alt Hacker NewsIt's not so contradictory if you peel back a couple layers
1. For junior engineers a 50% increase might be less than a 10% increase for senior engineers. So the % comments are consistent with the pareto argument. Diminishing returns _can produce_ a pareto tradeoff.
2. Saying gains are "concentrated" to junior engineers can also be a function of the work assigned to junior engineers. A senior engineer might get 1000% boost over jr doing the same jr work. The problem is the reverse - the hard things are concentrated around the oldest engineers, and now "hard" can also mean "not easily claude'd"
Yes, I’m a senior engineer at a 3-engineer startup, and there isn’t “junior-level” or “senior-level” work here. It’s all just work. Claude allows me to tear through the kind of gruntwork I’ve been doing ad nauseam for the last 15 years.
If my tasks were things like squeezing 3% more efficiency out of an algorithm, that might be different. Although, even then, my PM (!) used Claude to boost the efficiency of one of our more complex Postgres queries by up to 5x, in ways I honestly would not thought of doing. It was quite humbling. A former engineer here used pgMustard on the same query a couple years ago and claimed it was as fast as it could get.
I can’t speak for the kind of work done in the higher echelons of big tech, but for us, there isn’t much that Claude can’t help with.