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.
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.
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.
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.
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?
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.
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".
*assume: (communication/coordination overheads) + their pay < your pay
Blue collar refers to jobs that involve physical labor. The term arose when people on the factory floor would wear blue coveralls, and people that worked in the offices off the floor would wear white button down shirts.
Why exactly every job needs to have a clear path to CEO or be considered a dead end or blue collar job is a mystery to me.
and that's only one problem. you may reach (or ever want to) the top, but if there is a low ceiling that is going to put so many pressures on your career.
and people have to look ahead and see the trend. newer stuff is coming out faster and faster. The 'hard' stuff is paying more and more and requires less and less people to do it, while the easy stuff is consistently either being outsourced or made so easy 'anyone' can do it.
and unemployed beyond 40 dead in the industry? are you kidding me? we have less IT/programming jobs today than we had in the late 1990s. Where do you think those people went, they just up and died? they had to pick a new industry
>>> newer stuff is coming out faster and faster.
I see no indication of this. Actually, most of the things that were with us 10 years ago are still around, and introduction of paradigm-shifting concepts massively slowed down due to massive size of the market which would not allow quick change and incurs massive legacy costs. You could maybe introduce new HTML version in a year in the 90s, but now you're stuck with HTML 4 for decades because literally millions of applications depend on it and they are not going to change, and HTML 5 is rolling out in baby steps, despite all the cool stuff it proposes. Looks what happens to XP - they have a massive install base and now Microsoft can not get rid of it, however hard it tries. Market size is enormous now, and so the pace of adoption of any paradigm-shifting concepts is much slower than before.
>>> we have less IT/programming jobs today than we had in the late 1990s.
Could you back this up with some data? I haven't found the data that support this conclusion. The programming jobs are shifting around and moving, but I don't see IT being smaller now that it is in the 90s, even accounting for the dotcom bust. Where is that "less programming jobs" coming from?
[1] http://www.indeed.com/q-Cobol-jobs.html
[2] http://cis.hfcc.edu/faq/cobol
Edit: removed wrong data.
making a web page today in 'html' is NOTHING like it was 5 years ago, let alone 10. you're simplifying it way too much.
if you were a web designer, and just stuck with what you taught yourself back in 2005, you would be out of a job. you constantly have to learn new libraries, new languages because no software operates on an island. yes, every field must adapt and add changes, but none so much as like with tech.
all of this is COMPLETELY irreverent anyways. IF you want to be a programmer, and not look ahead to your future to find out what you will need to grow into, BY ALL MEANS. And if you think people will still find your skills valuable even though you don't plan on updating them constantly, good luck.
the point is, if you read the article and dont want to gamble with your future, a programmer is a dead end job in the sense that if you are not moving into some sort of managerial position, there is no where to go.
>>> IF you want to be a programmer, and not look ahead to your future to find out what you will need to grow into, BY ALL MEANS.
This is a false dichotomy. I want to be a programmer AND look into my future, and I do, thankyouverymuch. I do not want to be a CEO, it's not a job for me, I'd suck at it. But I don't suck at programming, and that's what I want to do. And I think there are lots of opportunities around to earn your bread and butter on it.
>>> that if you are not moving into some sort of managerial position, there is no where to go.
That's plain wrong - there's everywhere to go, and you confirm it yourself by noticing new things appearing all the time. That's where you go - doing new things! You don't have to have a 'C' in your title to live a fulfilling professional (or personal) life. Of course, if your goal is to have that 'C', go ahead - but there could be many more goals than that.
This site seems to disagree with you: http://www.bls.gov/opub/btn/volume-2/careers-in-growing-fiel... . I work with numerous people over 40 actually.
Also, I beg to differ that learning a new programming language is a big deal. We've yet to see a single complete disruption in the way we program... It's still editors, compilers and debuggers in the end.
Peter Drucker called these folks "knowledge technologists": http://www.economist.com/node/770819 ... And believed probably will be the majority of workers in a developed countries over the next century.
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.
Electricians, mechanics, heavy machinery operators in Alberta can make $150,000 in the oil sands before overtime, plus fly-in/fly-out costs; in the major urban centers, upwards of $100,000. If you're young, add in overtime and you're looking at $150-200k+. Foremen and supervisors can make up to double.
A programmer in the Bay Area will top out around $200k as a senior member of technical staff.
Edit: I thought the original "blue collar" remark was sarcastic. Am I wrong?
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. :-) )
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.
I wrote "all jobs" in one place and in another "a lot of software people [...] again".
Since you were also there, what I meant should be obvious...?
In my Swedish job market, there was also something similar around a decade earlier. But it was not only for software people.
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.
This is just plain false.
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.