3 ms·
Hmm, so if there are a lot of junior developers - inevitable as more people are getting STEM degrees - I should not help them grow, so that they are not able to
by sershe 4y ago
Hmm, so if there are a lot of junior developers - inevitable as more people are getting STEM degrees - I should not help them grow, so that they are not able to do my job? Sounds pretty bleak. Continuing this to its logical conclusion, should I try to sabotage them too? :)
By the time cheaper juniors are able to do what I do they might demand the same salary I demand, or whatever salary I might be able to demand at the time.
Frankly even from a cynical perspective, this doesn't check out. Juniors usually don't try to own the same thing - I'm already there and at any given point could do it better, shared component ownership is rare, plus they'd rather own something new so they can get promoted. Plus juniors move around more. Moreover, while new juniors are relatively easy to replace or outsource, someone with tons of expertise in the area and experience of owning it and working thru others is harder. So, being a large area lead seems more secure than being a junior.
- Viliam1234 4y ago> Continuing this to its logical conclusion, should I try to sabotage them too? Similarly, if you are not donating blood, the logical conclusion is to become a vampire. :) If you want to help junior developers, there are many other ways to do that. For example, you could teach a programming course, make a paid video at Udemy, or write a book. If your goal is to help junior developers, skip the intermediary, be more efficient, own the copyright, and set your own working hours.
- sershe 4y agoMy point was that not helping your coworkers succeed because you are afraid they'd take your job (unless that appears to be an explicit goal) is a very bleak mindset, and probably self-limiting too, as far as one's own career goes. My goal is to eat candy and poop diamonds, I don't have altruistic motives towards junior developers :)