3 ms·
> I’ve just started transitioning my career closer to management, so I develop/manage roughly 50/50. At this point, if I had to manage a tight budget, I’d rathe
by Marsymars 1mo ago
> I’ve just started transitioning my career closer to management, so I develop/manage roughly 50/50. At this point, if I had to manage a tight budget, I’d rather have an entry level salary as tokens for a senior engineer.
A high-potential junior you can at least justify as an investment in the future.
The other people who are going to get squeezed are the later-career developers who are below-average in ability. (I'm not using "below average" here pejoratively - just noting that by definition, half of developers are below-average.) Outside of big tech, there are piles of organizations with devs who don't make big-tech salary and who are only marginally productive for what they're getting paid.
If you're an organization that only has the budget to pay non-junior devs $80k... you can see the implications of having the option to spend your dev budget on seniors + tokens instead.
- whatshisface 1mo agoI'm not seeing the reason why typical engineers can't vibecode. Non-coders can vibecode. I have read hundreds of posts claiming that senior engineers can vibecode but not a single one saying that juniors cannot.
- Marsymars 1mo agoI'm not saying they can't, but rather that with the time seniors then spend cleaning up their tricky bugs, architectural problems, etc. the seniors could have just done the work themselves.
- whatshisface 1mo agoIn a cost sensitive business, nobody cleans up the architectural problems today - no change for vibe coders except upward.