6 ms·
I respond really negatively to the notion of 'dead end.' Programming isn't a dead end job any more than welding is a dead end job or painting. But it is a trade
by ChuckMcM 13y ago
I respond really negatively to the notion of 'dead end.' Programming isn't a dead end job any more than welding is a dead end job or painting. But it is a trade.
What is more, managing is a different job than programming. Not a lot of programmers really internalize that until they try out being a manager. Architecture, and technical leadership in general, is still another job. It takes the ability to internalize massive amounts of detail, organize it into some coherent frame work and then communicate that framework as needed to various levels in the language they understand. So for programmers they need to know how the parts fit together, for managers they need to know how the parts integrate with the business process, for sales they need to know how the parts make them better than the competition (or equivalent to).
From an economic standpoint, being able to generate 1000 lines of syntax error free code per day, is perhaps the best possible programmer you could be, but its never worth more than 10 programmers generating 100 lines of syntax error free code a day.[1] So yes, there is an economic limit on your pay.
The good news is that generally that economic limit is much higher than the cost of living, and you can run at that limit for a decade or more, so you can be reasonably expected to save enough to retire and not have to work any more.
Dead end jobs are jobs that will never pay you enough money to save for retirement. Programming isn't one of those jobs.
[1] Yes the 9 women, one month joke applies for short sprints but in general not for longer coding projects.
- nostrademons 13y agoBeing able to combine programming with communication, sales, and analysis skills can be incredibly valuable, though. That 1000 line/day programmer, if he looks around and observes the functioning of the org, could probably easily find several areas where those 10 programmers are writing 100 lines/day that could easily be automated away. If he can then write a solution that does this and sell it to upper management, he's clearly been more productive than all of them combined. This is where you find the programmers who get paid several million a year.
- ChuckMcM 13y agoAgreed, but if she can observe the "functioning of the org" then she probably will try management at some point. There is an old quote my Grandfather had which went something like "soldiers control battlefields, generals control objectives, and kings control countries." The gist of it was that if you could see the path to success you rose to the level where you could use that vision to make that level of change happen.
- lrryy 13y ago"she"?
- nostrademons 13y agoSeveral tech bloggers/writers (Ben Horowitz of a16z is probably the most prominent) have taken to using female pronouns when referring to unspecified tech leaders (CEOs, founders, high-level engineers). This is a way to combat sexism and unconscious bias in the tech community - by sorta jarring you out of your expectations of what gender a prominent tech person is, you're made to consciously think "Why wouldn't a woman be in this position? Why is my default assumption that a high-performing engineer is male?" Much like your post. Anyway, I support this trend and I've been known to do it myself sometimes. It's a little disorienting when the hypothetical subject of a thread flips genders halfway through, but the person is only hypothetical anyway, so why not?
- andrewljohnson 13y agoIf there is an economic cap on the value of a developer, it doesn't derive from how much code they produce. Value differentials for programmers derive from knowing the right code, not typing up any code that suffices, and I think pay reflects that. 1 KLOC of the right code can easily be better than 10 KLOC of the wrong code, even if the 1 KLOC is buggy and the 10 KLOC has no bugs. I think programmers are valuable in a power law way, and this can be based on intelligence, domain knowledge, experience, math skills, and other things. You can command a much larger salary if you either have technical/math abilities that almost no one else has (like a Google search engineer), or you can have an economically valuable product sense (like a proven, high-paid early start-up engineer), or you can know a domain in an economically useful way (many technical founders). Programming is an army-of-one kind of job, even if you work in a larger team. Insightful programmers are better than dogged ones by orders of magnitude. I look for programmers who are creative, self-driven, and knowledgeable. EDIT: I ended up editing this for the first 18 minutes it was live. Premise is the same, but I wanted to work on how I said everything.
- jamesaguilar 13y agoIn my book, edits like this are fine. You turn a draft into a post-revision work and it makes the site better, especially for folks who aren't reading it conversation style. I agree with this sentiment. It's more effective to find the correct company and correct project within that company to make sure the lines you write are valuable. That's where the money comes from. I know some dudes who are smart and great coders who are making (relatively) little, because they are working on fun things with limited economic value. On the other hand, there are guys who are merely good programmers who are making a lot more, because they sought out projects with very high value and impact and moved those forward. Although it's hard to say how either group can complain too much considering the relative luxury of even entry-level programming jobs in this market. Part of the reason that startups can be so lucrative is not that a lot of code is being produced, but that code doing something never before done is being produced. The code is not the product, the behavior it's implementing is. It's a subtle distinction, but an important one.
- ChuckMcM 13y agoI tend to agree with your basic premise, and I realize that in the general case it is impossible to do analysis. But my fundamental point was that a programmer's salary is limited by that programmers replacement cost. We talk about ageism here now and again, and it is out there, but it is more common in my experience that people who had their salaries ratchet up because their management didn't know what else to do, end up being paid more than their replacement cost. If they try to find a job at a different company, the hiring managers might evaluate their salary requirements as unreasonable. That particular story is way too common in the Bay Area.
- eternalban 13y agoYou are right. Programming is a blue collar trade.
- rschmitty 13y agoThat is a bit of a reach to call it blue collar. I have blue collar friends from high school who envy what programmers do and make and I do what I can to try and persuade/teach them to learn to code and make a better life for themselves.
- asdfologist 13y agowhoosh Edit: I thought the original "blue collar" remark was sarcastic. Am I wrong?
- deleted 13y ago[deleted]
- BugBrother 13y agoMost everyone has forgotten the 2000 dot com crash, when all the computer jobs disappeared. This "learn to code" is just how it was then. I would bet money that in less than five years, a lot of software people will be unemployed -- again. (If I win, good. If not, good. :-) )
- smsm42 13y agoI'm curious - how much money would you be willing to bet on that? At which odds? I've been through the dotcom crash and minor disturbances after, and the jobs never "disappeared". Yes, there were layoffs, pay cuts and hiring freezes. But not all jobs disappeared, and most of the people who lost their jobs found new ones after a while. I'm not diminishing the pain and suffering of those who got caught in bad situations there, but it's not like the whole IT disappeared and people went back to abacuses and wired telegraph.
- 13y ago
- zaroth 13y agoFrom an economic standpoint, being able to generate 1000 lines of syntax error free code per day, is perhaps the best possible programmer you could be, but its never worth more than 10 programmers generating 100 lines of syntax error free code a day.[1] So yes, there is an economic limit on your pay. If all you ever do is code functionality that other people dream up, in a system design that someone else specifies, then I agree completely. For a lot of engineers, that's how they operate. Maybe that's how they want to operate, maybe that's the best way for them to operate. For other coders, and this depends as much on the company and corporate structure as it does on the individual, they are the ones dreaming up new products, new approaches to old problems, layout solid foundation that 100s or 1000s of engineers can build upon, or specifying an approach and methodology which ships the product 6 months sooner with twice the functionality or half the bugs. They are the engineers that make your entire organization not only more efficient, but literally capable of things that they weren't capable of before. That's when you start getting into the same type of ROI from that programmer as that SVP is supposed to be providing. The problem is most organizations simply aren't organized to promote and reward these engineers, and that's the "dead end". The last time I worked for a company I didn't own, literally the only way I could find to make any real money was to do my programming inside the sales organization, so I could be paid on commission for writing code for "major accounts" which would only later be taken up by the core engineering team and become a full-fledged product line. Being a quota carrying engineer, with variable compensation and benefits like 'Presidents Club' was living in a different world from the engineering org. What I found was that, when working for someone else, in order to justify significantly higher pay, I had to be more directly driving increasing sales. Doing the exact same work inside of the engineering org, even with the same sales impact, would have paid significantly less.
- lukeschlather 13y agoFor the big tech companies, this is exactly how they are organized. Software companies that don't have job titles like "principal software engineer" and "distinguished software engineer" which rank at director/VP level are going to have a hard time as software becomes more and more critical.
- 13y ago
- fragmede 13y ago> So yes, there is an economic limit on your pay. As a mere programmer, sure, but senior developers get well into the six-figure range, and with some luck, those stock options are worth quite a bit. Sure, not everyone gets to work at Google at an early stage, but their IPO minted a good number of 'mere' programmer millionaires.
- dkarapetyan 13y agoFrom an economic standpoint, being able to generate 1000 lines of syntax error free code per day, is perhaps the best possible programmer you could be, but its never worth more than 10 programmers generating 100 lines of syntax error free code a day. This is just plain false.
- littledot5566 13y agoYeah, Jeff Dean would probably disagree with this post too.
- smsm42 13y agoI think you view (or at least present here) the programming job as pure production measured in KLOCs or something similar, and this is wrong. It is a part of the job, but not the main part. 1 KLOC written by a good programmer may be worth literally orders of magnitude more than 10 KLOC written by 10 poor programmers. The reason is not syntax errors - those are mostly irrelevant as the tools get rid of them pretty quickly. The relevant part is what tools can't do - conceptual build of the code, design, robustness and ability to accommodate change. These terms are very hard to define, especially with rigor that would be convincing to anybody outside of the industry, so there's a lot of hand-waving and "you know what I'm talking about" when we talk about it, but in the essence poor code is poor and great code is great not because the former has tons of obvious errors and the latter does not. It is because you'd spend orders of magnitude more money, time and other efforts supporting and improving poor code than great code. That's where better programmers are providing the edge, not in the KLOC output. If you need KLOC, you don't need great, you don't even need good, you just need "can tie his own shoes" one. But if you need a system that you wouldn't have to throw out and rewrite in 3 years because it became unmaintainable and every fix immediately creates an explosion of new problems - then you need great. That's where 9 women/1 months comes into play. The problem here is of course as I noted this is very hard to manage and evaluate except way post-factum (and even then there are little of robust tools and methods to do it with any rigor) so it's hard to know for sure. But in many cases, "you know it when you see it".
- godzilla82 13y agoWhy are you assuming that the 10 programmers are less skilled than you are. Take this scenario: You(good programmer) write 1 kloc. 10 other (equally good) programmers write 1/10 kloc but each of them is willing to work for less than 1/10 your pay!* Isn't this a possibility in free market? So may be you dont have any intrinsic value. Your value is a function of how many similarly skilled programmers are out there. Since this applies to all trades, I guess the solution is to move to trades where the supply of "good" labour is less than your current trade. May be that is why the author's friends who moved to management get paid more. *assume: (communication/coordination overheads) + their pay < your pay