Hacker News Reader

Comment by turbinerneiter | Hacker News Reader

Simple problem:

Developers want more money for more experience.

At a certain point, more experience does not make them more effective developers.

If they want to justify higher salaries, but can not be more effective on their own, they need to multiply their experience by making other developers more effective.

The organizational problem is that most companies see management as the only way to do that, but not everyone can and likes to be a manager.

We as developers have to make sure we promote mentoring, tool and framework building, system architecture and such topics as viable paths upward. Otherwise, managers will only have managing as an idea of how someone can create more value.

View on HN

Excellent point.

Training and mentoring are extremely important.

Last night, I had dinner with a friend of mine, who is a former Marine. He told me that the "best of the best" become DIs (Drill Instructors). He had tremendous respect for his DIs, and described them as "almost superhuman."

DIs are always noncoms, but tend to be highly experienced. They are also good trainers. Being a good trainer is a fairly specialized skillset, and many techs aren't able to adapt to that, either.

In my case, money has never been the point. I'm a high school dropout, with a GED, and never really got paid as much as even many entry-level kids are, these days. Nonetheless, I lived frugally and sensibly, and have been able to survive being tossed out into the trash. Many of my peers do not have that capability.

In the early years of my career I was the hot-shot developer that outproduced everyone. It was fun, but ultimately unrewarding. Some people don't mind but most people dislike others who are conspicuously better/faster than them. In a "team sport" like development, this was a bad strategy.

Now the analogy I like to use is a rising tide raises all ships. Instead of being the individual hot-shot I do everything I can to make everyone else a hot-shot. If they are talking in a meeting and I think a nudge needs to be made, I just 1:1 message them with a tip and then let them say it instead of speaking up. I do more training of juniors and even seniors, teaching devs how to think through complex problems. Now my teams are more productive, most of the people like me and want to be working with me, and my income has skyrocketed as a result. Of course, I did have to escape from traditional office hierarchies and go into consulting to really increase the $.

I agree with one caveat: the degree to which more experience means more productive depends to a large extent on two factors:

1) The experience. 2) The job.

Having 10 years hacking on one system probably won't make you anymore productive than 3. At that point you're a factory worker, and you can't only put so much expertise into flipping a few switches and following traces.

However, having 20 years of diverse technical experience will make you more productive than 15 if the job requires the breadth you've developed.

I'm 12 years in and have moved into Startups for just that reason. You get to learn more numerous things, and you get to use all of them. I've been at my current job 6 months and I've worked with 4 languages, more libraries than I can count, 2 third parties, blah blah blah. If I went back in time even 3 years of experience, I would definitely be less effective. If I went back 5, I'd be struggling.

I work for a small company, and one of the things I enjoy is we're always spinning up new ideas to see if they work. We tend to spend half time on new stuff and half time on maintenance.

This has given me a lot of exposure to different things over the years. It's mostly web stuff, but one of the more interesting ones was interfacing with hardware for a warehouse app that we built to make the shipping process less error prone and more efficient.

Often said as, you can have 10 years of experience or 10 one year experiences.

This ignore the immense amount of overlap various systems have, and the benefits of cross-pollination you get from the parts that don't. Even if you work on a completely different system every year, by that tenth year, you'll be up and running faster, and probably have something to teach the people who've been working on that system longer than you.

I took an alternative approach, I was living in london, so I moved to Portugal. a remote London Dev contracting, and the wage is more than enough over here

Reply on news.ycombinator.com