231–240 of 341 posts
A “self-confident rockstar“ is just a developer who has been through this process of self-development and no longer requires the mentoring and extra effort to get them there. I appreciate that some companies value experienced developers and aren’t trying to nickel and dime by finding “broken toys” so to speak that they can force into their own moulds on the cheap
What do you mean by "broken toys"?
Earlier quoted context omitted.
Agreed, however am in Los Angeles. Would recommend remote but this type of thing might be better in person. Perhaps each city can create their own. Even in LA there'd probably need to be a group in each part of town, like west, downtown, and/or Pasadena.
I am interested in joining a group in the LA area. How can we make this happen?
Let me think about it a bit.
We're in a labor market in which CS students are focused on drilling for the FAANG-style whiteboard tests. And many will tell you their strategy is to go to Google for 2 years of experience and resume-building, and then leaving rather than grind away and play the promotion game there. And everyone has known for 20 years that you have to job-hop to grow your salary in this industry. And most employees would be naive t…
I officially mentored someone at my previous company and helped him move from a support tech role into a software dev position. It was incredibly rewarding. But to play devil's advocate for a moment, isn't there something of a natural disincentive to level up one's employees in such a tight labor market? To follow the author's analogy, by mentoring someone, we're effectively "adding a fish" to the pond, and if someon…
When you are the one adding the fish to the pond. You know exactly what type of fish it is as it grows. Whereas the fish that you catch may be a catfish rather than a sockeye. The free rider problem is a real thing, but so is the market for lemons.
I officially mentored someone at my previous company and helped him move from a support tech role into a software dev position. It was incredibly rewarding. But to play devil's advocate for a moment, isn't there something of a natural disincentive to level up one's employees in such a tight labor market? To follow the author's analogy, by mentoring someone, we're effectively "adding a fish" to the pond, and if someon…
Most good employees don't quit for at better job unless there's a dysfunctional workplace. Partly they don't know if there's better jobs, and partly it's just a lot of effort, but mostly because other companies don't know they're good employees. The labor market is a market for lemons. If you own a $2000 car that drives OK you don't sell it because other people won't believe it's any good.
This article assumes that the person you are mentoring is open to being mentored. I’ve worked with some engineers who were definitely junior despite having years of experience and very opposed to even a slight suggestion on how to improve their thinking process or implementation process.
So basically you have to somehow spot right person to spend time with, and it is hard. At least guys that don't want to be mentored are not time sinks.
I officially mentored someone at my previous company and helped him move from a support tech role into a software dev position. It was incredibly rewarding. But to play devil's advocate for a moment, isn't there something of a natural disincentive to level up one's employees in such a tight labor market? To follow the author's analogy, by mentoring someone, we're effectively "adding a fish" to the pond, and if someon…
> But to play devil's advocate for a moment, isn't there something of a natural disincentive to level up one's employees in such a tight labor market? To follow the author's analogy, by mentoring someone, we're effectively "adding a fish" to the pond, and if someone else "catches" the fish, that effort is largely wasted. Most good employees don't quit for at better job unless there's a dysfunctional workplace. Partly…
Earlier quoted context omitted.
This is simple - pay people by the value they bring to the company upon every annual compensation review. Yes, it costs money to train people. Consequently they get paid less during that period. But once they can fly on their own, treat them as if you hired them like that.
> Consequently they get paid less during that period. But once they can fly on their own, treat them as if you hired them like that. That's too early. You made an investment, that investment has to break even. With your suggestion, it would never break even.
Earlier quoted context omitted.
Usually, the teaching/mentoring is not free either. So you can a) hire someone who needs training and then train them, or you can b) hire someone who is productive since day 1. The people in a) cannot expect the same salary as b). Otherwise, there would be no point in incurring the costs of training them. Unfortunately, once you train them, someone can snatch them as people in b). You incur the loss, someone else ben…
This is simple - pay people by the value they bring to the company upon every annual compensation review. Yes, it costs money to train people. Consequently they get paid less during that period. But once they can fly on their own, treat them as if you hired them like that.
how do you determine the value they bring to the company? Presumably it must be a % of the revenue or valuation growth but I cannot come up how you derive the value.
> Your mentees will support you and promote you for the rest of your life. The problem I've seen is that this is rarely true. We've had a big set of grads we've trained that quit for a 20% pay rise, or a project that they happen to like better. Many regretted it but it didnt stop the next guys from doing the same. I'm really burnt out over teaching green newbies again and again.
In fairness, all other things being equal, wouldn't you move for a 20% pay rise? Especially at the more junior level, where that kind of increase could probably afford them a significant boost in living standards.