7 ms·
No this is not ageism. After a certain point, if you are an individual contributor, your value is not worth more than someone with less experience. A developer
by scarface74 7y ago
No this is not ageism. After a certain point, if you are an individual contributor, your value is not worth more than someone with less experience.
A developer with 10 years of varied experience can usually do just as well as someone with 20 years of experience. I also believe that the idea of the 10x developer while not a myth, is so rare it’s not worth trying to find for most companies.
I speak as someone in my mid 40s who has been at this professionally for 20+ years [1].
I’m debating whether I want to take the next step of consulting or just stay in development. I see my salary hitting a ceiling in the next two or three years and I think I am okay with that.
[1] well for all intents and purposes maybe 12 years. I stagnated for a few years and became an “expert beginner”.
- slavapestov 7y agoI think the number of years in your post is off a bit. In San Francisco, you become a senior engineer within 2 years, and after 5 years you're either expected to go into management, or retire to southeast Asia with your IPO money.
- deleted 7y ago[deleted]
- ergothus 7y agoYour summary is a bit outdated, I believe. While there is definitely a ceiling as the above poster added, the last decade has had a LOT of effort in improving options for non-management IC development. The big companies are realizing there is value in keeping strong technical people in technical roles. You still have to improve your so-called "soft" skills, improving communication up and down the chain, and it does involve a reduction in actual coding time, but you end up more of a code manager than a person manager. None of which says there isn't a struggle, but the world is very different than when I had a manager told me I could never expect a decent job if I stayed in coding.
- Nursie 7y ago> A developer with 10 years of varied experience can usually do just as well as someone with 20 years of experience As a developer with 20 years experience ... I'm a lot better at what I do than I was ten years ago. Better at seeing how it relates to the business I'm working with, more productive in ways that are not just LoC. I'd be OK if I can sustain my current income... but I'd still like to take the step to being more of a consultant. I'm dancing on the edges of it now, between contractor and consultant.
- scarface74 7y agoAnd that’s another line of reasoning I don’t believe. I have a coworker who is probably 10 years younger than I am but has been working for the company for 7 years to my one, how could I better understand the business of the company than he does? I worked for one company when I was 35 dealing with the complicated rules of the railroad industry. My manager was 28, but he was the founder of the company before it got acquired, built it from scratch and had 90% penetration in the particular market segment, how could I be more experience at how my code relates to the business - one he studied since he graduated from college?
- rpedela 7y agoYou can always find examples that counter the generalization but don't necessarily make the generalization false. In general, a 40 year old is going to be better than a 25 year old in understanding how software is applicable to business simply because they have more experience. They have been in more business meetings and seen how their software applies. Does that mean a 25 year old can't be better than a 40 year old at that? Of course not.
- scarface74 7y agoIt's not just one random counterexample. Knowing how code relates to a business has a lot more to do with how long you have been in that particular business or vertical than your general experience. That 25 year old who was at the company since they started 3 years ago is going to know a lot more than that 40 year old who just came in yesterday. Besides that, I did say 10+ years. The whole point is diminishing returns from experience.
- notacoward 7y ago> your value is not worth more than someone with less experience. I don't think such a general statement (even its direct inverse) can be true or even particularly useful. At a certain point you're playing the odds. We're dealing with X, what's the chance that someone has seen X before or can see a connection to something else? In those situations, 20 years of varied experience can be a lot more valuable than 10 years of varied experience, especially if the 20 includes areas or approaches that have been forgotten/ignored for most of the last 10. (You'd be surprised how often the ebb and flow of tech fashion produces such results.) Note that I said can. Whether that actually happens depends on the exact technology, what experts you already have, team size/cohesion, etc. "Is not" without qualification expresses a more absolute and certain opinion than is warranted.
- xfitm3 7y agoLet's not forget the essence of why we get paid: you are paid because someone likes you. They like your work output, your social skills, or your status. I'm not as hungry as a intern but I present well, and at the end of the day, thats why I get paid.
- mistermann 7y ago"In order to be successful, one must project an image of success at all times." – Buddy Kane, American Beauty I doubt many people know this explicitly, but I think the necessary behavior is intuitive to lots of people. I suspect people "on (or near) the spectrum", which is far more common in tech circles, get their ass handed to them career wise many times because of this, because they are in some sense looking at a different version of reality than other people.
- jerf 7y ago"I also believe that the idea of the 10x developer while not a myth, is so rare it’s not worth trying to find for most companies" The problem with the 10x myth is that it assumes a single dimension of productivity, and that no-one is ever negative so there's some sort of sensible, positive "minimum" to talk about. Senior developer leads a team of three other medium-experience developer, and completes the project in six months. Junior developer leads a team of 5 other even more junior developers, after six months they've got nearly nothing, so we pull in another 4 semi-skilled developers and 2 contractors who are drowned under the mess and don't know what to do, and six months later, the project is cancelled entirely. How many times better is the senior developer? There's nothing even remotely skewed about those numbers, either. Both are totally realistic. And yes, senior engineer can fail, and junior engineer could succeed. (Although the range of projects where a junior can succeed and a senior can fail assuming adequate initial knowledgebase for both is fairly narrow; generally if you find one, you've probably got a strawmanned "senior" engineer who isn't actually senior but just a collection of stereotypes in your head.) If you're still offended: A generally senior software engineer who knows nothing about the domain and his team of three develop furiously for a year and eventually deliver the first iteration of what was asked for, with another year to go on the project to finish it. A generally software junior engineer who is deeply familiar with the problem domain listens to the customer's problem and after a day's thought realizes what they really need is a very different, but also much simpler, solution, which they deliver in two weeks by themselves. How many more times valuable is the latter? (I've actually advised someone like that in the construction industry. They were switching into a programming career in their 40s. I said, look, there's no realistic chance you're going to outprogram me in a really academic, isolated sense of the term. But you've got contacts, the ability to pass the shit test with other people in your industry which I and/or generic software engineer have no chance of, and a deep understanding of the problem domain. Don't worry about trying to outprogram a 20-years-experienced software engineer, take advantage of the facts that you know what your customers really need, and... you're there! and I (standing in for generic software engineers) am not! Life's about playing what you're dealt, but people are generally dealt more cards than they realize, I think. Not necessarily better cards, but they have more cards than they think.) I tend to agree there isn't a such thing as an engineer who is 10x more productive than another, in the sense that they will do the same thing as that other engineer, just 10 times faster. The key comes from doing things differently, most of the time. There's other differences as well, such as being aware of the pitfalls. I recently got myself put in charge of a billing system, and as a senior engineer, I at least have the good sense to be suitably terrified, for instance. "Move fast and break things" has its place, but "careful, paranoid engineering" does too. Almost by definition, your really junior employees don't really know how to do the latter. (They'll often be able to cargo cult it, which can be a start, but they won't really understand it.)
- bsder 7y agoDon't confuse the current shitshow that is VC flippable social software garbage with actual competence. I worked with people at IBM and DEC at the point probably just at the peak of their heyday when the average experience was about 15 years. Oh ... my ... God. I have never had that kind of interaction again. Being able to just call up and talk to the folks who designed FPU algorithms, x86 emulators that smoked (I think the FX!32 guys knew more about x86 than AMD), BDD analyzers that actually matched circuitry to descriptions (NP-hard problems--solved every day), debugged CPU failures by having 3 old guys light up cigars, put their feet up and think real hard ... I can go on and on. Yes, those big, sclerotic companies had lots of deadwood. But, there was a 25% that was amazing. About once every couple of years now I bump into someone genuinely as good. It's really rare now.
- kylel 7y agoDo you know of any companies that nowadays with that type of culture?