Live data from Hacker News

Great developers are raised, not hired

sizovs.net

171–180 of 341 posts

Re: Great developers are raised, not hired

#171

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…

> Make mentoring/growth a central strategy at every level so people will see a path to grow.

I have been following hackernews for 15 years. 20 years since I saw an stallman interview in local pc magazine, blown away by the intensity of the man. I am an artist. I love to read plt stuff and haskell lisp code, I cried over sussman lectures.. It expands my mind, finding ways to express my thoughts so that common people in my world can understand me better, for their sake. I dont write programs, a lot of the code feels unmusical, not ergonomic, my musical background made me aware of how unmusical a keyboard feels like. Learning functional programming has made me aware how most people use imperative chain rule sequences to generate their thought patterns. I would love to work with inspired people just building new ways to express thoughts. But I quietly read and try to translate visions and feelings into code. Writting linear sentences is becoming a drag. It feels as if the time is ripe to raise our conversations to a more constructive functional level. It is happening. It is a slow progress. I can't see myself working in IT because of business deadline material oriented approach. So I continue to quietly read plt stuff. I do not want to understand anything because the other is usually limited to a smaller temporal frame. I read code and apply different real life variables to it and see how the interactions develop within my interaction space. How would you mentor me? /rant

Re: Great developers are raised, not hired

#172
post #155

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…

> And everyone has known for 20 years that you have to job-hop to grow your salary in this industry

And this is why companies continuously lobby to keep the current H1-B system in place.

Re: Great developers are raised, not hired

#173
The distinction here is between a hunter-gatherer mentality and an agricultural one.

Are you picking and choosing or are you farming?

Currently we grow engineering skill in (often) high cost institutions with limited capacity such as traditional universities. Moocs and bootcamps are alternatives which try to address the scalability, cost, and time commitment barriers of traditional education.

The question is should there continue to be a strong dichotomy between organizations who consume the output of these growth channels and the growth organizations, or should software development companies create programs of structured education and growth that have a low barrier to entry?

As others have mentioned startups who can hunt/find/pick people with relevant, high quality skills have the advantage of not paying the time and organizational cost of training.

Personally I think that large organizations should be taking more hands-on approaches that take all, or nearly all comers, and then provide training for the kinds of skills they need.

If you look at military funding for medical educations (for example) you'll see that the organization can be very generous in terms of time and training cost as long as a candidate ends up with the skillset they need. You might not go in wanting to be a urologist, but you can end up highly skilled and very well paid if you're willing to meet the needs of the organization.

Re: Great developers are raised, not hired

#174

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…

I don't see why this rules out giving A.) developers who have now become B.) developers a raise to match their increased value

Because it is still more expensive than just hiring b).

If you decreased a) wages during their initial training to cover the costs and be able to break even with b)-like wages at the end of the training, you wouldn't be able to hire anyone as a) at all.

Re: Great developers are raised, not hired

#175
post #163
post #155

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…

My last company would insist that they couldn’t give promotions or significant raises. Until you came in with an outside offer, then they’d roll out the red carpet and bend over backwards to keep you. It breeds distrust, discontent, and disloyalty. The best people don’t like this and leave. They company is left with people who can’t land outside offers. And the company ends up needing to pay market rate anyway to rep…

This works for the company because most people don't bother interviewing and coming up with a counter offer. In my previous company the best of the best would leave because company had this blanket policy that they would never do a counter offer. But in overall it was good for the company because they were able to retain most of engineers with raises as little as 1% and no stock refreshers.

Re: Great developers are raised, not hired

#176
post #169

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…

You think you’re entitled to a trained developer for the price of an inexperienced developer. That’s not going to happen. No wonder they leave.

The end result is hiring trained developers for the price of trained developers, and sending the inexperienced developers to be trained somewhere else. Where? That's their problem.

See? Looking just for one's interests works both ways.

Re: Great developers are raised, not hired

#177
post #127

So many developers here downright scared to mentor others. The problem with the current job market on full display.

We have to live in the world as it is, rather than what we'd like it to be. The well reported in this discussion patterns of your boss trying to replace you with your mentee, getting dinged for not getting "real work" done, and mentees not staying in the company for very long should give anyone pause.

That seems like a good way to keep the world the way it is, and not how we'd like it to be.

Thankfully, not everyone thinks as you do.

Re: Great developers are raised, not hired

#178

Earlier quoted context omitted.

Off topic - but your username and the vast majority of your commenting history is primarily on salaries. Curious - is there some backstory to it? Feel you got severely underpaid? To each and his own, but bay area engineers pissing about making ONLY 300K has always come off as being a bunch of spoilt brats - especially considering the vast majority just gem/npm/pip install this and that and glue all the code together.…

The hard part of engineering isn't the ability to glue packages and microservices together. Those tasks are literally done by entry level, bottom of the totem pole engineers. You're saying that all bankers do is run models and spit out valuations, and all a chef does is put stuff in a pan. I'm not speaking toward your argument of a bubble bursting, but engineering isn't going anywhere. And where else would an entry l…

Consider the scaling factor for salaries; My salary is on the high end in my area, but would be on the low end of a living wage in the Bay Area.

My salary is in the neighborhood of 120k; I'm a senior-level engineer with almost a decade of experience, involved in some of the high-level planning tasks you describe.

Re: Great developers are raised, not hired

#179

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…

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.

The question is why would someone leave your company once you train them? If someone is more valuable on the open market than you are paying them, pay them market rates. HR compensation policies need to be in line with the market, not the old “we have a policy of not giving more than 5% raises”.

I’ve been working in development for a $long_time but I restarted my career about 10 year ago and my rise is about the same as you would see from someone just graduating from college 12 years ago. Out of the four job changes I had, two were partially because the next company was willing to offer me $25K more (not talking crazy west coast salaries here).

One other went out of business and the other because they decided “they didn’t want to be a software company” and they just wanted report writers a year and a half after I was hired as the dev lead.

1. Pay more than everyone around you. (Obviously, not generally viable.)

You don’t have to pay the most, but don’t pay so much under the market that everytime the employee sees a random job posting or a recruiter call they know they can make signifactly more just by picking up the phone/responding to an email.

2. Make mentoring/growth a central strategy at every level so people will see a path to grow. I'd be curious to hear other possibilities.

That helps. But why would I spend a year a two “growing” at your company, when I could both “grow” and make a lot more money some place else?

I’m at a happy place where I work now, and I am decently compensated compared to the market, but even now if someone was willing to pay me $25K more, all other things being equal (work life balance, no travel, short commute), I would jump ship. But the only realistic way I could make significantly more is by going into management (not interested) or being a consultant (not interested right now).

Re: Great developers are raised, not hired

#180

Earlier quoted context omitted.

Currently switching jobs for a personal record 57% increase in total compensation. And I was NOT poorly compensated before. I was already in the 99th percentile for individual income. The harder I push on comp the more I get each time. I am not going to lie and say that it didn't take years to build to this point in terms of skill, work record, professional network, and interview ability. It took three FAANG companie…

Off topic - but your username and the vast majority of your commenting history is primarily on salaries. Curious - is there some backstory to it? Feel you got severely underpaid? To each and his own, but bay area engineers pissing about making ONLY 300K has always come off as being a bunch of spoilt brats - especially considering the vast majority just gem/npm/pip install this and that and glue all the code together.…

> but bay area engineers pissing about making ONLY 300K has always come off as being a bunch of spoilt brats - especially considering the vast majority just gem/npm/pip install this and that and glue all the code together. Of course the market deserves to pay accordingly but I think it's just a big bubble that's going to crash soon - since there is a huge mismatch between demand and supply of CRUD glue programmers (which most programmers are).

Seriously? Why the hate?

300k is Tier 1 (FAANG) and 2 companies. They don't just do CRUD. Those that do CRUD probably work on the SETI/Infra/Tooling division for the BigCos and even some of these "Tool-Devs" created amazing OSS tools. Do you suggest they should be treated as 2nd class citizens and get paid half of the "product" people and creating an old-time rift?

I've seen a few Bootcampers that get a job in Tier 1 and 2 companies but they have "solid" background/previous experience (hardcore Math, Stats, Data Scientist switching to SWE, greybeard embedded software engineers), just not up to date skill set.

This whole "salaries" will crash down demise has been around forever and it hasn't happened yet just like any other "demise" prediction.

I'd suggest people not to hate the situation: our sector/field is getting paid serious money, why the envy/jealousy/negativity?

Do you like the situation where hi-tech industry as a cutthroat, no-union, rampant ageism, low-paying wage?

Think of the bigger picture here...

Post reply on HN