Slashdot Mirror
Which Programming Language Pays the Best? Probably Python
Nerval's Lobster writes: What programming language will earn you the biggest salary over the long run? According to Quartz, which relied partially on data compiled by employment-analytics firm Burning Glass and a Brookings Institution economist, Ruby on Rails, Objective-C, and Python are all programming skills that will earn you more than $100,000 per year. But salary doesn't necessarily correlate with popularity. Earlier this year, for example, tech-industry analyst firm RedMonk produced its latest ranking of the most-used languages, and Java/JavaScript topped the list, followed by PHP, Python, C#, and C++/Ruby. Meanwhile, Python was the one programming language to appear on Dice's recent list of the fastest-growing tech skills, which is assembled from mentions in Dice job postings. Python is a staple language in college-level computer-science courses, and has repeatedly topped the lists of popular programming languages as compiled by TIOBE Software and others. Should someone learn a language just because it could come with a six-figure salary, or are there better reasons to learn a particular language and not others?
No, I probably won't make $100k/year coding in Perl but I don't care.
It's not about the money. It's about the love.
Not as tedious as C++; not as clunky as Java; not as lame as VB.
Scoff all you want! I feel blessed while coding in Perl.
Thanks Larry & friends!
Political correctness is really just herd psychology pushed by insecure people who desperately seek social conformity.
But it's not the language, it's the domain knowledge I bring to the table. I was hired to write embedded software for scientific instruments. As a former research scientist and current software engineer I can understand the problem, the solutions, and write code to do what the device needs to do. C/C++ just happens to be the tool I use to build the device. Python, Java, and so on just wouldn't cut it.
Hands down it can do everything perl can do - while providing clear, readable code that is consistent from one developer to the next.
My experience is different. Dramatically different, actually. I've seen very few examples of readable python, and very little consistency between developers.
I suppose you're referring to the controversial the white space rules? The killer-feature that can be replicated for any sensible language with a keystroke in virtually every editor? Or, if you prefer: The reason that anonymous functions in Python are crippled?
I'd even go as far as to say it's white space rules make Python code significantly more difficult to read, as you can't clearly see where blocks begin and end, particularly when the indentation level changes by more than one, which happens quite frequently.
I debugged my last hanging curly brace/missing semicolon long ago.
I'll bet it was easier than hunting down the invisible bugs from mixed tabs/spaces or introduced by your editor mangling indentation while moving bits of code around. You know, problems you're actually likely to encounter when using Python, unlike your examples.
Required reading for internet skeptics
I love Python because it maps very neatly onto how I model problems in my head. I'm not averse to using other languages, but Python is my comfort zone because Guido and I apparently think about algorithms in the same ways. As it turns out, I make a decent living with it.
So, do I have a good job because I know Python, or is it because the thought patterns of the people who are drawn to Python are the same ones that companies want to pay for, regardless of language? If the former and you want a good job, then by all means learn Python. But if knowing Python is just a side effect of the properties that employers are actually looking for, then it's probably not going to help you all that much.
Dewey, what part of this looks like authorities should be involved?
I hate this comment.
I probably hate it because I make about $90k (plus one of the best benefits/retirement packages in the United States...you can suck your 401k, I gots me a pension!)
But really, I hear this all the time. "Oh, you only make $90k? You must suck. Any mid-level programmer can make more than that."
First, it really isn't just about the take-home. The benefits are really important.
Second, there are sooo many other factors, it is incredible. I live about 70 miles from Silicon Valley. My salary *is* something to scoff at by the denizens of the Valley, but for quality of life? I have most of them beat.
I live in a beautiful house that I can easily afford. I average 40 hours per week- with the variance being about 3 hours each way. A 'crazy' time means that I come in at 7:30, and maybe stay as late as 5:30 if I have some process running.
I get to lift my head out of the screen and go do REAL things during my work. I am consulted on many different business processes- my opinion is valued well beyond the technical side of my job.
Someone else mentioned 7 brogrammers huddled together in some Santa Clara shit-shack, all making $150,000. That's a miserable existence that I want no part of- no matter how great they are at programming, or how many Google logoed items they own.
It isn't all about the dollars- don't let some HR firm tell you it is! Don't base your career/life trajectory on your paystubs.
**As an aside, I have visited the Google campus a few time for different projects- meeting with 'fairly high level' employees. We typically compare quality of life notes...I haven't talked to any Google employees over the age of 35 who thought they had made a good life decision to be there. Except for the former CEO's of companies Google has purchased...those guys are happy as shit.
No reason to lie.
Sigh.... *Raises hand*
Hey, in my defense, when most people say mid-west they really mean Chicago. And the cost of living there is not the same as here in miniscule Quad Cities. I know it's only three hours away, but it's still a difference.
Here, I only know of CTOs and one developer making over 6 figures. Most of the makerspace is making under 80K, with a couple exceptions.
The biggest factor is that, for an embedded guy like me, there are only about 3 companies that would employ me. And only one big fish. (It's John Deere). There are plenty of small side players for general business-level developers, and web-devs can live anywhere, right?
But yeah, with about a decade experience, I'm kinda feeling underpaid. The good news is that the whole family is headed for Colorado, where I hear there's more opportunity.
With a combined income of ~150k, we live a comfortable life in a 3 bed 3 bath and have saved up a net worth of about 300k.
That's two engineers with no kids most of that time. We certainly feel like one of the wealthier people in the area.
Even cost of living adjusted you're being screwed. A senior in Seattle (more expensive, but not silicon valley prices) will make 120K plus stock. A senior in the valley can make 160+ not counting equity and bonuses. A senior coming off a big success like working at a sold startup can make twice what your combined salary is (that's not counting what he makes on the sale itself). And cost of living isn't as huge a deal as many people make it for two reasons:
1)The only thing that's hugely different is housing. Even if you pay 2-3x rent, you won't pay 2-3x for car insurance, the car itself, food, etc. That tends to be more 10-15% max (and usually much less, some things are even cheaper). You're most likely figuring the COLA wrong. The right way to do it is to break your costs into categories and figure out the adjustment for each category, not straight multiply by the rent adjustment.
2)If you save the same percentage in either place, you should still prefer the place that pays more because you can downsize someplace cheaper at retirement.
If you have personal reasons for wanting to live out there, that's totally different and understandable. But understand that you are getting fucked financially by it, it isn't just a cost of living difference.
I still have more fans than freaks. WTF is wrong with you people?