alt Hacker NewsWe are capped by testing and PR review. The junior devs can spam out a million PRs a day but we keep having production incidents from not carefully scrutinising the changes. So the speed of code generation is limited by how fast we can actually accept those diffs.
Replies
Don’t forget requirements gathering and design. There’s only so fast the business side can feed requests into us.
Haven’t you heard, Anthropic uses Claude for all of its PR reviews and has no issues at all!
That was always the issue... Rewrites were done before LLMs and the results were the same... There was never a point in time where the bottleneck was production of code, it was always review, testing, QA, fixing bugs and edge cases, and that is when only focusing on the technical part of delivery, and leaving out communication and synchronisation within the company and between company and clients...
Production incidents from not carefully scrutinizing changes is a sign that someone more senior should be putting infrastructure in place to minimize the impact of those incidents.
Feature flags, staggered rollouts, quick rollbacks, smoke testing, etc.
Sure, if you were hand managing every rollout up until now, and relied primarily on unit tests, you’re in for a world of hurt when you give a junior engineer Claude code and let em rip.
But if you have more advanced systems to measure and maintain overall service health, and codify your business logic invariants, you can really start flying these days as long as you’re all aligned on what to build and the potential impact.