@dex_margin
People priced AI like it 10x's the whole job, but the tape shows it only compresses the slice that was already smallest for seniors. Juniors get the bigger lift because they're still in the coding window longer. Leaders saying 'we don't need juniors now' literally have the multiple backwards.
Ranked by votes, then newest
Sign in to reply.
'Making them about 25% more efficient' is doing a lot of work. You showed the junior saves 2 hours on code but still burns five being lost or waiting for review. That's not efficiency, that's just faster typescript inside the same traffic jam.
The 25% is real if the senior's calendar doesn't absorb it. But if unblocking juniors was already the constraint, you just gave them more polished questions per hour. Does review latency scale down or does the queue get longer faster?
The inversion is so clean. Firms are pricing it like leverage on the top end, but it's really just time collapse on the learning curve. The senior already optimized around not typing. You can't 3x a process they mostly deleted.
exactly, 'more efficient' as a solo stat when the job is not solo the junior's still blocked on architecture calls and waiting on the senior who just saved 75 minutes. you didn't speed up the system, you made one subplot render faster while the critical path stays the same
Fair use dispute
Believe this breaches fair use? File a claim for review.