2 ms·
I mean literally that if you're a green-eyeshade bean-counting manager and you're making a headcount decision and you have the option of retaining a very senior
by tptacek 1y ago
I mean literally that if you're a green-eyeshade bean-counting manager and you're making a headcount decision and you have the option of retaining a very senior engineer or hiring an early-career engineer, and there's a story you can tell yourself where they both get the same fundamental revenue-generating or cost-avoiding work done (for instance: because the senior engineer has a later-career focus in team building and acceleration, which has become less relevant in this stipulated world where we're laying off tons of engineers --- that's the premise of the question, not what I believe is happening) then there's a lot of reason to believe it's the senior engineer who is going to get the fuzzy end of the lollipop.
I think a lot of senior people talking about the impacts of this technology on "junior developers" understand this, and are trying to talk their own book.