>With a 10x boost, if you give an engineer Claude Code, then once they’re fluent, their work stream will produce nine additional engineers’ worth of value.
I keep hearing about this 10x productivity, but where is it materializing? Most developers at my company use Claude Code, but we don't seem to be shipping new features at ten times the rate. In fact, tickets still take roughly the same amount of time to complete.
I'm seeing that some tickets are "finished" (i.e. ready for PR) more quickly, but they end up needing so many changes and to be re-reviewed so many times it takes longer than it ever did because someone is saying yes to the LLM instead of designing software. When it's clear your review comments are just going back into the maw of the LLM, I've given up trying to guide and now just outright suggest actually workable designs (taking more of my time too), and that merely cuts down the number of times it will come back for review again.
Nothing is more infuriating at work than when you say something to someone in a message or PR comment, and they just paste the LLM response back to you.
Wow, you still get responses? I usually get 3 or 4 more commits (I've seen some of these touch nothing but comments but have a typical LLM-brained commit message as if it actually changed the functionality the comments were about, and some which literally won't compile) and the comment marked as Resolved.
I keep hearing about this 10x productivity, but where is it materializing? Most developers at my company use Claude Code, but we don't seem to be shipping new features at ten times the rate. In fact, tickets still take roughly the same amount of time to complete.