Slashdot Mirror
Is Programming a Lucrative Profession?
itwbennett writes "A pamphlet distributed by blogger Cameron Laird's local high school proclaimed that 'Computer Science BS graduates can expect an annual salary from $54,000-$74,000. Starting salaries for MS and PhD graduates can be to up to $100,000' and 'employment of computer scientists is expected to grow by 24 percent from 2010 to 2018.' The pamphlet lists The US Federal Bureau of Labor Statistics as a reference, so how wrong can it be? 'This is so wrong, I don't know where to start,' says Laird. 'There are a lot of ways to look at the figures, but only the most skewed ones come up with starting salaries approaching $60,000 annually, and I see plenty of programmers in the US working for less,' says Laird. At issue, though, isn't so much inaccurate salary information as what is happening to programming as a career: 'Professionalization of programmers nowadays strikes chords more like those familiar to auto mechanics or nurses than the knowledge workers we once thought we were,' writes Laird, 'we're expected to pay for our own tools, we're increasingly bound by legal entanglements, H1B accumulates degrading tales, and hyperspecialization dominates hiring decisions.'"
In my state you must have 10+ years in 5+ languages (even if the language is only 5 years old) and start at $8.00 an hour. Oh, and clerical/janitorial experience a plus!
I know some developers that are highly specialized in low-level DSP programming, and they make plenty. Also, if you are also responsible for architectural decisions and architectural design, you make more. I don't know many people who are just programmers, but I would have to assume they make less. My advice for programmers is take on more responsibilities and/or try to become a specialist. Unfortunately, there is a large supply of programmers, probably because the barrier to learning is quite low compared to say, FPGA design and development.
That they are essentially mechanics? They're just not auto mechanics, they're more or less computer or software mechanics?
That shouldn't be a surprise to any. Especially as we see more about self-fixing computers, the furthering of object oriented programming which is leading to simpler and simpler APIs so you don't even have to be a programmer to make things happen. Or technologies like Sharepoint where you don't even have to have a GED to prop up multiple sites / data sources, etc.
Blessed be he who reads this post, Cursed be he who tells my boss.
My starting salary in DC contracting with the Feds was $70K. Flash forward to a year of living in Cincinnati and my salary dropped to $40K. Now I'm back in DC contracting for Feds again. Starting salary? $105K.
60K in a place like Cincinnati, not bad. 60K in DC, can't live on it. Be sure to take regional salaries into consideration.
Don't be a developer. They will work you 24/7. You will be cuffed to your desk most of the day. Your hair will turn gray and fall out around the edges so you'll have a friar cut. They'll water board you for overtime. They make you buy your own computer, desk, and chair. You aren't allowed outside except for one hour a day of supervised time in the yard. Coworkers will shank you with shivs made from sharpened USB drives. You'll have to gang up to get respect. First thing you'll have to do when you come to work is shank someone, to let them know you mean business! Wages are a lie. You'll be paid in honey buns and cans of tobacco so you can roll your own. If you work hard enough you can get a free day with your spouse, but this depends on company performance.
Overall being a developer is the most horrible job in the world. If I were young and choosing a career I would do something else. Like be a reality star or join the circus.
If you listen to people who don't do tech work talk about techies, you'll quickly realize that a lot of them do in fact put techies on roughly the same level as mechanics or bricklayers. You can think of yourself as a "knowledge worker" all you want, but the fact remains that you are going to be treated like a bricklayer. My most educated guess on why this is true is that techies produce useful products. In most businesses, the act of producing something (rather than selling something or organizing other people to produce something) severely limits your chances for advancement past the equivalent of senior foreman.
There are 3 ways to avoid this fate that I know of:
1. Do some serious and visible work for your company about issues that aren't tech-related. For instance, if you provide intelligent input about pricing, the salespeople will respect you a lot more.
2. Work at a company who's business is technology, which is still run by a techie. Make sure to leave once the suits take over.
3. Start your own company, and watch out that you don't completely become a suit.
I am officially gone from
I can believe 54,000 grand.
I cannot. 54 grand I just might.
Because they might show up your grammar and spelling skills?
Never ever let anyone tell you what you can or should earn. Your salary is your choice. Do what you love, take control, and don't whine. This approach has worked well for me for the past 30 years. I've survived more than a few industry changes over that time.
The only thing worse than a statistic is an anecdote. The author has his personal experience- fine. But my personal experience directly contradicts his. And the only statistics on the subject (from NACE and BLS) give a fairly Normal distribution of salaries between 57,000 and 151,000 (http://www.bls.gov/oco/ocos304.htm) Median annual wages of computer and information scientists were $97,970 in May 2008. The middle 50 percent earned between $75,340 and $124,370. The lowest 10 percent earned less than $57,480, and the highest 10 percent earned more than $151,250. Median annual wages of computer and information scientists employed in computer systems design and related services in May 2008 were $99,900.
I'm in software. I freely admit my spelling and grammar skills SUCK. :)
(re)Learning spelling would be a good idea. I'd hate to be the one to debug human resources code with a variable named /*Whether or not higher subject*/
bool higher=False;
which actually determined if someone was hired, but another coder thought it was a boolean for hierarchical levels, and was making it flip-flop between true/false.
Coders, as the future jacks of all trades, need to know a little of everything, and a lot of the fundamentals.
Hello there!
Please refer to your opening on job posting site. I, Rajesh Sharma, would like to apply for the job.[...]My hourly rates are $ 9 USD.
We all like to pretend this isn't here and it isn't happening, but I would say conservatively half the job market has disappeared in 10 years due to this currency/standard of living imbalance.
There's another reality: it's really, really hard to manage projects in India. I have tried this for a number of projects, and have learned the following things:
Each and every project, I have had the above things. There are lots of ways around the above, but the main thing is that it's very hard.
8 of 13 people found this answer helpful. Did you?
I wouldn't be surprised since USD9/hour is a fair bit in my country.
;)...
Analyst Programmer monthly salariesin Malaysia
According to Google: 1 Malaysian ringgit (RM) = 0.292184 U.S. dollars
So at the higher end, RM4500/month * 12 = USD15777 a year, or about USD7/hour. The low end is naturally even lower...
For some strange reason[1] a company I used to work for outsourced some work to India. When the Indian workers came over and we compared salaries, they were paid more than the average Malaysian programmer in our company, and while we weren't very good, most of the Indian team made us look good in comparison, one or two of them had some clue (they were paid quite a lot in comparison), but the rest were like the sort of programmers who would be responsible for the notorious Excel bug (where 77.1*850=100000).
FWIW, RM5-6 buys you a decent lunch, you can rent a room for about RM250-500/month and taxes at the RM4500/month level aren't that high.
A lot of people in "the West" are unaware of the huge differences in cost of living. Wages are really low elsewhere. So when you see people say "it must be child labour", it's often bullshit, or someone misinterpreting a picture/video ( just because a bunch of oriental/asian workers are petite doesn't mean they are children - my cousin is 40+, she lives in New York and she has to buy some of her clothes in the children's section).
[1] Apparently the company had money stuck in some country (not India), so they decided to use it by outsourcing work to a company that then outsources it to India... Can't remember how many layers there were. Something like that anyway. I was wise enough not to say in one of the first meetings - "why don't we just buy a whole load of merchandise, ship it to where you want the money to be and sell it, you'd lose less that way", go figure why
Stop hiring Rajesh FFS!
Not that I disagree entirely that it may be more difficult to manage someone in India, and I've certainly heard horror stories, but come on. These could all be applied to just about any remote contractor who isn't worth their salt. I have worked with/currently work with plenty of Indians who really knew/know their stuff.
I gotta side with cerberuss on this one. Yes, c'mon all of those can be applied to any remote consultant that is not worth his salt. However, from my experience working with remote teams (India, Brazil, within the US), there is something specific about the consulting industry in India that can really bit you in the ass harder than in other cases.
Now, just like you, I've worked with plenty of Indians who really knew their stuff. In fact, most of the remote projects I've worked that involved teams in India have had a high success ratio. But the few that have failed have done so far more miserably and catastrophically than with other teams on other countries.
This has given me a glimpse to a darker side of Indian offshore consulting, which I've actually talked a lot with several of my Indian colleagues who also agree on this: you can end up with a consulting firm that sells the idea of development guided by a a top-notch architect, and you swallow the tripe. And then the top-notch architect designs a system which looks solid, then he moves to another project. Then the consulting firm gets a whole bunch of sophomore kids from college find ways to replicate GOTO statements in Java to do the implementation. My first encounter with such practices from such a consulting team was when I was working together with an Indian colleague of mine (a really good software developer) in trying to make sense out of the mess. When we looked at the code and the original design, all we could do was say "WTF?".
That's an experience I've had to repeat several times. It's a reality, and it has nothing to do with dissing people from X or Y country. It's an unfortunate reality that cannot be denied or politically correctly sugar coat it.