@blotosmetek I say that after two weeks of working with Claude Code on a large and complex code base, which allowed me to blaze through around 40 issues from my bugtracker. Some were small fixes, some were complex new features. My job is that of an architect at this point, guiding the programmer, which is exactly what I would be doing with a junior.
This isn't "statistically significant data", I guess, but it's not a single fluke. And I've worked with enough juniors to know this is better.
@blotosmetek The thinking is valid, code written is good. Most of it is what I would have written. It does need architectural guidance: use that way to access the data instead of this way, implement this using different abstractions, etc.
When it reviews code, it sometimes finds valid issues that I overlooked.
There really was a major change recently: I've been trying this regularly, and it was never good enough. It is now.