upvote
> the critical part of the backend where a new 300ms delay will cost the company millions then yeah.

If it is so critical, why don't we have tests and benchmarks for it?

Oh right, because "Greg the super-coder" never wrote any of this down and it lives in his head so he can be the arbiter of change.

It was toxic before agentic coding, it's still toxic now.

Document your systems. Add tests and benchmarks for what is important.

We've always known this, we have a dozen or more textbooks written about it. But we always gave it a pass because "Greg the super-coder" was producing more value than he was hurting.

That's no longer the case. Your best coder is now Opus or Astra

reply
> If it is so critical, why don't we have tests and benchmarks for it?

Thats a fair point, but Ive seen LLMs modify the surrounding environment to “pass the test”

A human still has to be responsible at some point.

reply
Good thing you reviewed the PR so you could catch the gap in Greg’s documentation and force him to write it before approving his PR!
reply
> Your best coder is now Opus or Astra

No, that's our _fastest_ coder, which is a different thing than _best_

reply
> he critical part of the backend where a new 300ms delay will cost the company millions then yeah.

If a performance regression like this isn't caught by an automated testing suite, you have made a horrible mistake.

reply
Reviewing the PR gives you a chance to identify this gap in the performance regression suite.
reply
The agent could also do that part while its still in draft. If the rigorous tests already exist of course.
reply
> new 300ms delay will cost the company millions

these might be 1% typically

reply