Earlier quoted context omitted.
The mistake there is to point it at code to figure out performance optimizations. The place to find them would be performance profiles, query plans, telemetry. The guidance for perf still applies, measure before and after change. The issue is that the code often does not contain the information to do a perf optimization. Eg. you can't tell your cache size, the volumes of data in your DB or the latency of your network…
You can very easily spot performance issues through code. Allocations are often visible, slower hash maps are often visible, loops are visible, etc.
Google fixed more Chrome bugs in June than over the past two years, thanks to AI
281–290 of 667 posts
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#282Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#283I'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…
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.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#284Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#285Earlier quoted context omitted.
What is bikeshedding supposed to mean here?
It comes from C. Northcote Parkinson's work, where he calls it "The Law of Triviality". The idea is that people clog up decision-making by introducing a swarm of issues that have little relative impact or importance for the project at hand, leading to a massive misallocation of attention. His example is a $10 million construction project for a Nuclear Reactor where as much time is spent debating the materials to be u…
I’m assuming he’s using it to mean “cruft” or “low value features” but maybe there’s some meaning I’m missing.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#286Earlier quoted context omitted.
Do you really think they mean they’ve been using mythos
In my mind there are three tiers: The SOTA: Fable, GPT 5.6 Sol, Opus 5 The "enterprise admin did not turn on the new models": Opus 4.8, GPT 5.5 The "I love hallucinated garbage": Sonnet, Qwen 3.6, GPT 5.4 mini, GPT 5.3 Codex, etc. Results vary widely
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#287Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#288Earlier 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.
Very few problems really have "all the tooling to verify its hypotheses" though. even if you want to construct such an harness. Also let me ask you why we need better and better and models if what we have already can produce good output with 'all the tooling to verify its hypotheses'
This is such a blanket dismissal that I can’t agree or disagree.
Maybe very few of YOUR problems are this way. At least mention some problem domains.
Recent experiences: compiler-related (helpful), UI-related (agree it isn’t testable but the design iteration is quick, easy, and correct), debugging technical configuration problems (useless; I basically have to solve each problem myself before the LLM recognizes it).
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#289I'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…
Which model are you using? There is monumental difference between models. Even between "frontier models". When people tell these stories, it would be great to also add which model you were using. As an example Opus 5.0 is in completely different class compared to Cursor Grok 4.5 even if the benchmarks don't show such massive difference. Not even talking about regular stuff like Sonnet or Composer or stuff like that.
Re: Google fixed more Chrome bugs in June than over the past two years, thanks to AI
#290I'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…
Which model/mode?