Earlier quoted context omitted.
It's not an invention it's a question. If the number is <20% that's great news for the Chrome team.
The elephant in the room is how many people in this discussion are actually alien lifeforms. The elephant in the room is how many turtles obtained law degrees. The elephant in the room is whether this is worth discussing because we're all in a simulation. No, it isn't the elephant in the room. You made up some horseshit that betrays how little you know about the field, which will get upvoted because HN has a hearty c…
Google fixed more Chrome bugs in June than over the past two years, thanks to AI
231–240 of 667 posts
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#232A lot of people here seem to be living in a different universe than me or simply don't know how to work with AI. I think detractors believe you should just let AI do the job blindly instead of leveraging it as a tool to accelerate you. They get mad at Excel for the poor investment returns. At this point, this is such a strawman, it isn't worth counter arguing. I think I'll abandon this discussion and keep using AI qu…
I agree with you. > I think detractors believe you should just let AI do the job blindly instead of leveraging it as a tool to accelerate you. However this is how it’s marketed. C-suite is telling people eventually you won’t need to read code, frontier labs saying programmers won’t exist etc. The reality is like you said, a tool to accelerate you.
If you test each feature and have it iterate on your feedback, you can build a decent product in this way.
Does it write too much code? Perhaps. Could I bring those 100k lines through code review in a team where some members nitpick? No.
That does not change the fact that it works, and that you do not need to read the code even today.
Unless progress slows down dramatically and soon, it seems rather likely that most of us will not be reading code in the near future. Their marketing is not wrong.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#233Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#234A lot of people here seem to be living in a different universe than me or simply don't know how to work with AI. I think detractors believe you should just let AI do the job blindly instead of leveraging it as a tool to accelerate you. They get mad at Excel for the poor investment returns. At this point, this is such a strawman, it isn't worth counter arguing. I think I'll abandon this discussion and keep using AI qu…
I see a lot of the disagreement here has the same form as many of the political arguments from 10 years ago.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#235I've recently been using AI a lot for performance optimisation during a particularly busy period at work. I would say it was almost completely useless at the high-level direction - it would point out suspicious parts of SQL queries for example but on back to back testing these almost never resulted in any performance change. In fact, if it wasn't for the fact that it made making the actual changes I identified much e…
And at worst you still saved a bunch of time on writing the tooling to test the issue
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#236Earlier quoted context omitted.
You have to learn to use your tools, not try whatever intuitively made sense to you at first (expecting the tool to do all the work) and then whining on Hacker News when it doesn’t work out for you.
We're reliving the early day Google era. It's an objectively simple tool to use, but some people just refuse to put any effort to learn. I'm thinking the issue is probably that LLMs/harnesses are too easy to use? It crossed the thin line between magic and tooling and blur the mental model. If Claude Code were as hard to use as, say, ComfyUI, perhaps there would be less programmers having absurd expectation of it.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#237Earlier quoted context omitted.
You're using it wrong. No really you are. Give Fabe 5 access to a test database with some data, or even restricted access to your live DB and tell it to optimize then. I've had stunning success optimizing for performance this way. In a single day, I made the core part of our app 2-3x faster.
Thats fine but then Fable 5 should have requested this information instead of blundering along. So why didn't it? An expert human asked to do the same task would have surely asked for the additional data.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#238Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#239I've recently been using AI a lot for performance optimisation during a particularly busy period at work. I would say it was almost completely useless at the high-level direction - it would point out suspicious parts of SQL queries for example but on back to back testing these almost never resulted in any performance change. In fact, if it wasn't for the fact that it made making the actual changes I identified much e…
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#240Earlier quoted context omitted.
The thing that makes it work really well is to make sure it has all the tooling to verify its hypotheses. If you allow it to run the full lifecycle in loops you will be surprised how well it works.
But them it's more like AI assisted performance fuzzing? Just throw stuff against some measuring harness and see what sticks?
Current AI isn't super effective at making the breakthroughs, but it sure is effective at democratizing the ones you can point it at.