3 ms·
This is laughably false. The highly-paid, experienced seniors produce so much more value than juniors that it's not even in the same ballpark. It's also usually
by stavros 2y ago
This is laughably false. The highly-paid, experienced seniors produce so much more value than juniors that it's not even in the same ballpark. It's also usually the kind of value that juniors don't even notice, because it's not measured in lines of code.
A good junior will write a hundred lines of code in a day. A good senior will delete a hundred because they realize the user dictated a solution instead of detailing their problem, asked them, and figured out that they can solve that problem by changing a config variable somewhere.
- mewpmewp2 2y agoYes, but they don't get paid as many times as junior engs compared to how many more times value they bring.
- klabb3 2y agoViolent agree on variance in value produced. Violent disagree on that junior, senior or other titles or roles have such strong correlations. For very simple reasons: we can’t measure value, and we absolutely can’t measure value within a performance review cycle. The most devastating value destruction (aside from the rare intern deleting the prod db) that I’ve seen consistently is with senior/rockstars who introduce new tech, takes credit, moves on. There’s a reason for the term resume driven development. Think about what a negative force multiplier can do for an org.
- stavros 2y agoI don't know, I think where I work we have a pretty good idea for the value each person brings. I don't know how much they're paid, but I do know how good each person is (including whether they tend to complicate things, to use exciting technologies, etc). Maybe it varies per company.
- deleted 2y ago[deleted]
- mulmen 2y ago> I don't know how much they're paid But that’s the entire point you’re missing. The pay is not proportional to contribution or technical skill. It’s proportional to market forces and negotiation skill.
- stavros 2y agoI know what level each of our people is, and levels are compensated fairly evenly. The fact that I don't know exact numbers doesn't mean I don't have a proxy.
- deleted 2y ago[deleted]
- jalapenos 2y agoHow does violent agree/disagree work? Like after you conclude you agree/disagree to this internet text, do you then proceed to scream out on your balcony that which you agree with / smash up your apartment in rage, respectively?
- chrismorgan 2y ago> Think about what a negative force multiplier can do for an org. Negative force multipliers are easily remedied: just make sure you have an even number of them.
- atherton33 2y agoThis totally happened on my first team. We had a guy who would argue about everything that knew the CTO so we had to tolerate him. Then we hired a second one and they just argued with each other all the time and the rest of the team could finally make progress. It was awesome.
- bravetraveler 2y agoI have a feeling I was hired to be this second guy and I really just want to hang up my gloves, man
- atherton33 2y agoThank you for your service
- deleted 2y ago[deleted]
- jalapenos 2y agoIt's true, not "laughably false". I've seen with my own eyes the most effective developer in a company being paid in the bottom quartile, as well as a vice versa case. In the former case, we basically had to demand management raise his salary to the low end of his market value, over the cause of six months, until they finally gave in. It was just so disgusting to us we couldn't let it go. The reason comes down to a skill bias - it's a different skill set to navigate other people into getting yourself a good salary, versus navigating the ins and outs of coding. The skills don't overlap, so time spent on one detracts from another. In the end he finally got the message we kept ramming in to his head, applied to work at a brand-name tech company, and instantly more than doubled his salary. He could've done so years earlier. This stuff is the norm. I've been a manager having eyes on salaries while also having eyes on people's performance (although unfortunately not much of a lever on the former), and rest assured it is often a very jarring experience. Like "that person should be let go immediately / that person should job hop immediately".
- stavros 2y ago> instantly more than doubled his salary. He could've done so years earlier. So it's not true, then? The GP claims this is universally true. All I need to do is post a counterexample, and I did. Yes, there are shitty companies that try to keep salaries as low as possible, not realizing that that will lose them their best people. Don't work for those!
- deleted 2y ago[deleted]
- vaylian 2y ago> This is laughably false. The highly-paid, experienced seniors produce so much more value than juniors that it's not even in the same ballpark. It's also usually the kind of value that juniors don't even notice, because it's not measured in lines of code. This particular case sounds like someone got incorrectly hired as a junior. Maybe they didn't have enough "real world" corporate experience and that is why they weren't offered a senior position?
- mulmen 2y agoI was fresh out of college. But it’s not like that was an isolated incident or that other juniors don’t also have good ideas.