Comment by pixel_popping

I agree with all of it, and I think author did a really good job at actually saying what's true, it's almost like developers don't want to hear it.

I feel that OP has reach that point because he went out of the basic tooling like Claude Code (at least in its default state) and embrace multi-model, automatic reviewing, fuse, loops and so-on, when it's done right, well, failure rate to solve issues is <1%, this is exactly why you arrive to that kind of depressing thoughts afterward and it's spot-on.

Many people will disagree because they are still at the vibe coding stage, not "as much as I can prompt will be automatically done stage". Claude Code imo is deliberately not implementing the best ways for users to work, they have recently implemented Workflows but that's almost a year late, many companies are doing this since always and that's just part of basic tooling nowadays.

People talk about models and benchmarks score while genuinely I'm baffled because they seem to ignore that that same benchmark can reach 99% by levering tooling intelligently, we don't really need better models (at least for coding), we just need adoption of proper methods. The day developers will discover that they are already able to solve 300 issues in a single day with ZERO supervision in complex Rust codebases, I'm sure they'll change their mind.

Our bottleneck in our team is currently just having the mental bandwidth to type as much as possible, it's kinda sad, it is becoming all absurd.

If you are still watching the output of the model for coding tasks, I bet you haven't challenged your own methodologies, yet.