Which Language To Learn?

LordStormes writes "I've been a Java/C++/PHP developer for about 6 years now. However, I'm seeing the jobs for these languages dry up, and Java in particular is worrisome with all the Oracle nonsense going on. I think it's time to pick up a new language or risk my skills fading into uselessness. I'm looking to do mostly Web-based back-end stuff. I've contemplated Perl, Python, Ruby, Erlang, Go, and several other languages, but I'll put it to you — what language makes the most sense now to get the jobs? I've deliberately omitted .NET — I have no desire to do the Microsoft languages."

Comments

Really?

[r0ach]

I mean, I don't see php or C++ going anywhere anytime soon....

Re:Really?

[dreamchaser]

Yep, I still see lots of posting for people skilled in those languages. Also, if the submitter were serious about wanting to stay relevant and employable he wouldn't just automatically discount the .NET languages. There are more and more jobs available for skilled .NET coders. Tying one's career to ideology isn't always a smart thing to do.

Re:Really?

[Anonymous Coward]

Yes, but being honest about your preferences can be helpful. I don't want to do .Net development myself either, or dig ditches, or clean toilets. There may be jobs in all three fields, but that doesn't mean they're for me.

Re:Really?

[bhcompy]

Except that ditch digging isn't preferable because you make shit money and do shit labor. .Net is no different than any language he current programs in those terms. It's not like he's avoiding assembly because it's too difficult to learn or doesn't have the greatest job prospects. He's just cutting off his nose to spite his face.

Re:Really?

[wootest]

Okay, I'll bite: C# is a good language that makes more progress and is more eager to grow modern capabilities than Java is. None of the two will go away overnight, and C# isn't the very best thing ever, but I don't think people would have any problem giving it the credit it does deserve if Anders Hejlsberg worked somewhere else than Microsoft.

I personally mostly prefer to code in other languages than C#, like Ruby, but I'd much rather work in C# than in Java and that's not for a lack of trying. I use and love ASP.NET MVC, which is open source, patterned on Rails and all about the code, with no "insert control here" wizards in sight.

I know that there's a lot of people who drag a grid view onto a Web Forms canvas, hook up the data bindings, bill you the licenses of everything in the server stack and three weeks' work and then can't actually fix anything because they don't know how to code. Aside from conceding that Microsoft has largely traditionally gone out of their way to supply these people with software, I call Sturgeon's Law. Just please don't let that fool you into thinking that everyone who has touched or developed for a Microsoft product has the coding skills (and chair propelling propensity) of Steve Ballmer. If that's all they were capable of, I would be right behind you.

Re:Really?

[hal2814]

I've dug ditches for a living and built houses for a living and done grunt work for a kitchen installation company. Whoever is considering sitting around in an air conditioned office and cranking out .NET code "shit labor" has a severe reality deficit disorder.

Re:Really?

[EastCoastSurfer]

I take the general view that if you keep yourself *good* at whatever language you choose, you will have a job.

I agree with this, but in an even more general sense. If you are a good programmer then you'll always have a job. Language is largely irrelevant once you get into the larger groupings of languages. A good programmer is a good programmer regardless of the current tool they happen to be using at the time.

Re:Really?

[dreamchaser]

No, he is simply deciding that these particular principles are more important to him than a slightly better job prospect.

Oh I have no problem with that, I was just musing that it can bite you in the ass. In this economy if you're worried about your prospects it's probably best to keep one's options open. I can respect someone who stands on principle, but principle doesn't pay the mortgage. It's not like every time you code in C# God kills a kitten.

Or...does he! *eeeek!*

Re:Really?

[Anonymous Coward]

I've worked in various office enviroments for years as relatively unskilled labor, leaving for work in the dark, getting home in the dark, spending the entire day inside of a cold flourescent-bulb light enviroment that is always teedering on the edge of "full blown flu pandemic". Whoever is considering working outside preforming good honest work "shit labor" has a severe reality deficit disorder.

Newsflash: the grass is always greener on the other side.

Re:Really?

[NFN_NLN]

I've dug ditches for a living and built houses for a living and done grunt work for a kitchen installation company. Whoever is considering sitting around in an air conditioned office and cranking out .NET code "shit labor" has a severe reality deficit disorder.

Try debugging poorly written Perl code - there is such a thing as "shit labor" even in an air conditioned office.

If those are the only criteria used, then by your definition solitary confinement in prison would be a sweet gig.

Re:Really?

[Kagetsuki]

Wow, I'm not a big Microsoft guy but even I have to admit .NET is pretty damn clean and has some insanely good business app tie-up stuff. Look at what .NET offers you and really think about how much time it will take you to re-code that in PHP and JS - then consider how much more flexible the .NET interface will be. Unless your client is using something that really wasn't fitting to .NET in the first place you may be digging yourself a very large hole.

And if you know ASM then just learn some basic C and go into embedded development. Particularly ARM native highly optimized software is in extremely high demand and capable developers are far fewer than most other breeds.

Re:Really?

[SuperKendall]

I don't like .Net much. But I'm going to back you up and say you have a great point, and that obviously none of the other people have REALLY had to do full time manual labor for work. I have before college, and it was a huge motivator to finish a CS degree... All the people here are imagining frolicking outside on a 70 degree day carrying a single 2x4, and forgetting that pretty much everywhere has summer and winter too, and that a construction worker these days is going to be hard-pressed to find a job at all.

Re:Really?

[afidel]

Shit labor is anything that makes you unhappy and/or fails to pay the bills. So long as you are happy and have your health, a roof over your head, and a full belly then the rest of it is just noise.

Re:Really?

[ScrewMaster]

No, he is simply deciding that these particular principles are more important to him than a slightly better job prospect.

Oh I have no problem with that, I was just musing that it can bite you in the ass. In this economy if you're worried about your prospects it's probably best to keep one's options open. I can respect someone who stands on principle, but principle doesn't pay the mortgage. It's not like every time you code in C# God kills a kitten.

Or...does he! *eeeek!*

I agree. And there's nothing wrong with doing work that's not optimal in your opinion, but at least keeps the lights on, while simultaneously keeping an eye out for work that is more to your liking. It's not as if coding in .Net is amoral or illegal or something, not like selling your body to pay the rent (although some purists seem to believe that.) This is just his personal preference, a preference that he may very well find that he cannot afford. I'd rather not be doing Windows work myself, but you know what? I'd rather be employed than not, and besides, there are other aspects to a job besides the language you write in. In my case, I'm fortunate enough to have a great bunch of coworkers and a company that has good health benefits and retirement policies. Those count for a lot as well: a good coding gig is a complete package, not just your personal choice of programming language.

Having been in this business since before it was a business, I tend to look more at results. Is the end product of what I'm doing worth the effort? Am I proud of what I've accomplished? Does my work benefit others in addition to me and mine? Maybe that's because I started out coding for the likes of the Rockwell PPS4 and the MCS6502, and have been through a lot of different projects, in different industries, on different operating systems in a multitude of programming environments. I also spent the better part of fifteen years working as a contact programmer, and in that world you take what comes along. You never know when the next contract will be approved, or if, so if you're wise you don't get too stuffy about it. Still, it did help that after establishing a reputation as a reliable developer, I had some of my bigger corporate customers designate me as their preferred custom software vendor for industrial projects: they would pass all incoming RFPs to me for evaluation first, and I got to pick and choose. That was kind of a high point in my career actually, but I had to work very hard to get there. The point is, if I had told them "I only work in these languages", I wouldn't have gotten that far.

All languages have interesting aspects to their behavior, nifty features, unique drawbacks, and some are better tools for certain applications than others. I mean, I don't think of a screwdriver as being intrinsically superior to a pair of tweezers. For what each does, it does it well, and it doesn't hurt the user to know how to use both. The submitter sounds like something of a language bigot: I don't pay much attention to such people. "Oh, I wouldn't be caught dead working in that language. I couldn't possibly." If you love coding, you'll find something interesting in virtually any language, any project. A friend of mine once worked with a number of what he called "C bigots." These were guys that would spend three weeks hacking C just to put up a command button, and felt that that was only reasonable because, after all, the only real programming language was C. They wouldn't even consider anything else, and would laugh at the mere suggestion. Then C# came out ... suddenly they were huge fans of RAD and visual form design. My friend's comment? "Welcome to VB, you pompous assholes."

A language is just a tool, something to be learned, and you can accomplish significant things in pretty much any language. So maybe it's harder with language 'x" vs language 'Y': think of it as a challenge.

Re:Really?

[Anonymous Coward]

Digging ditches can be honest, rewarding work. Coding in any programming language can give one a sense of purpose. Answering phones and filing documents can be a good job. They can also be personal hell shit jobs... it all depends on the people you work with. If you enjoy the company of your coworkers and would at least go up and say "Hi" if you saw them out of work rather than try to hide, that's a good sign. If you can trust that you'll get proper credit if you help someone with their work, chances are you'll enjoy working there. If you are given enough tools, time and freedom to finish the job, but also paced out with a workload that keeps you interested, it doesn't really matter what the task at hand is. If your boss is incompetent, chances are none of the previous will be satisfied. Inadequate management leads to a higher emphasis on short term gains than long term growth, so a corporate culture of backstabbing and cutting corners develops whether you are performing brain surgery, digging ditches, programming in widgetfu, stocking shelves or designing nuclear reactor safety procedures.

That being said, learning another language just to put it on a resume is easy. Reportedly once you know a couple programming languages adding another is just a matter of a week or two to learn the fine points of the syntax and how to navigate the libraries. What you want as a prospective programmer is a portfolio of projects you have worked on. Don't just learn a language to have another bullet point on the resume... show that you can apply it to solve a real life problem. More importantly, try to take on a moderately difficult project with multiple specialized parts... team leadership experience will get you further than any three or four languages. The project doesn't even have to come to full fruition if you can show that your skills were improved and you learned lessons in the process. This doesn't necessarily mean that you have to shoot for a management position, but you may become qualified for a job where you are given the freedom to show just what you can do, rather than a boss breathing down your back interrupting you from the coding zone every 25 minutes, changing specs last minute and then yelling at you when you can't release on schedule.

That being said, it is up to you as an individual to determine what, if anything, requiring programming in .NET actually means about the kind of company you will be working for. And you might think you would be willing to take a $10,000-$20,000 pay cut to work at a place where your input is valued and you are given the tools that allow you to succeed, but really you end up making more money at those kind of places than you would if they were cutting corners left and right... because salaries and raises are one of the easiest things to cut off if they don't respect and value you anyways.

Re:Really?

[shadowofwind]

I can respect someone who stands on principle, but principle doesn't pay the mortgage.

You're not "standing on principle" unless you're willing to risk important things, such as the mortgage, to do that. Otherwise you're choosing expedience over principle, and any stated regard for principle is mostly posturing.

Not that there's anything wrong with that. And of course even a principled person has to make choices between important things, and may reasonably choose the mortgage, particularly if they have children.

But sometimes its better for kids to grow up in an apartment with honest parents than in a house with people who will trade their society's future economic health for temporary comfort.

Re:Really?

[bhcompy]

No one ever said teaching was rewarding from the start. The reward is the public retirement, the overall benefits package, the job security, etc. I know plenty of teachers that have spent their whole lives teaching in one school or one district and are set for life whenever they choose to retire(and a lot of times they do not because they enjoy their work). I know absolutely no one that has worked their entire career at one company as an non-owner/non-founding employee. That's the benefit of being the 42k math teacher working 12 hours a day for 9months a year. And your wage is more than I made working the same hours doing entry level tech support 10 years ago. 42k isn't a "bad" wage, even in Los Angeles, especially in a profession where wages grow by union contract

Re:Really?

[shawb]

The ones I've talked to always seem to be in good spirits... I think that's because after a week you get used to the smell and realize what society forced you to forget when you were in about second grade: poop is funny.

I might go with veterinary technician at your local pound. Their job is pretty much to take care of abandoned pets for somewhere between a few days and a couple weeks. Make sure their medical needs are attended to. Advocate for individual animals to try to facilitate adoption... and in the end humanely euthanize about half the animals that come in the shelter. All while receiving derision from activists and the public at large, being attacked by the animals you are caring for, and making about as much money as someone on the Geek Squad. Oh, and that vet tech will also be cleaning up feces, looking at it through a microscope, and even learning to identify certain diseases by the smell. And then once summer comes... you start with the maggots and cuterebra larvae. And numerous litters of newborn kittens with no fosters available to feed them. And the countless extremely friendly, people pleasing, perfectly socialized dogs that will never be adopted because the media has spread the idea that pitbulls are inherently vicious.

Re:Really?

[IICV]

You do realize that there are other things teachers do outside of classtime, right? Like, say, meeting with parents, staff meetings (you know those things? The same kind of bureaucratic meetings you have in an office? Teachers have those too - they don't just disappear as soon as school ends), meeting with students, and of course someone has to run detention though you can grade during that.

And then you're assuming that it takes a trivial amount of time to grade homework. It seriously doesn't. Most classrooms nowadays are pushing 30 students. Assuming he teaches five periods worth of class per day, that's 150 pieces of homework to grade. Assuming each piece of homework takes two minutes to grade (tip: it doesn't*), that's a full five hours of grading to do once a week, again assuming there's only homework once a week (in a lot of classes it's assigned more often than that)

And then there's all of the bureaucratic busywork to do. There's all sorts of continuing education, advancing education (a lot of teachers are working on a masters in something or other, since free tuition somewhere is often one of the few perks of the job), and God only knows what else the administration comes up with.

And then, when you're done with all that, you need to go over your lesson plan for tomorrow one last time, just to try and teach them a little bit better.

*it probably averages more like five minutes even for simple math assignments - sure, marking something right is easy, and marking something wrong is easy, but what about partial credit? What about bad handwriting? These are kids who've just barely learned how to write a few years ago scribbling shit down in the few minutes between classes because they forgot to do it last night - it doesn't lead to legible handwriting

Re:Really?

[elbobo]

I worked doing manual labour, and really heavy stuff at that, for maybe five years in my late teens, early twenties. It was, on balance, just as enjoyable, if not perhaps more enjoyable at times, than being a programmer. It just doesn't pay well enough.

Re:Really?

[ScrewMaster]

get real and face a few facts.

Something .NET proponents seem unable or unwilling to do. Most .NET apps would be better written as web apps and the remainder in C, C++, ObjC or something like Vala (I think Mono can do AOT compilation -- yet it's still a poor choice). Welcome to the real world where few except "pompous asshole" "language bigots" are placing long-term bets on the .NET platform.

I wasn't promoting .Net, and in fact I'm not a .Net proponent. I was just saying that limiting one's knowledge of one's own field isn't always a winning move. That's especially true when economics are a factor. I'm glad that you are able to work in the language(s) of your choice, and maybe don't have any real economic considerations to deal with. The rest of us don't live in that perfect world (I know I don't ... I have people whom I care about, and who depend upon me.) And, as others have pointed out, .Net is, like it or not, popular in the corporate world and if what you need is a job, you do what you have to do. Maybe, if you're a Unix/Linux/Solaris guy you get to work in an environment that suits your personal preferences/prejudices. Or, maybe you have bills to pay ... and you don't. That's life. It's not right or wrong, it's just the way things are.

There are a lot of people that have decided that their way of looking at the world is the only one, and don't accept that their might be another way. Maybe not a better way, necessarily, although "better" is a loaded term at best. That's true of any of the major camps: .Net, LAMP, you name it. If you took anything away from my post at all, it's that I believe that steadfastly refusing to look at what the other side has to offer is nothing but self-justified, willful ignorance. Even if after studying another approach you still find it wanting, well, one should know thine enemy.

COBOL

[Anonymous Coward]

Still in demand and it will not die.

Looking in the wrong places

[GaryOlson]

Industry constantly tells the Universities they need more C/C++ programmers for industrial systems. If all you are looking at is web based development, you are seriously limiting your options. I suggest a less restrictive filter on your search parameters.

To counter a shrinking job market?

[Cidolfas]

80% or so of all web-backend postings I see are PHP/Java/.NET or the like. The other 20% are all Python (usually Django, though I prefer Pylons myself) and Ruby. If you want to pick up another language just so you can be future-proof, go with Ruby. I haven't learned it yet (I do javascript myself, and use PHP or Python when I do backend), it seems to be a more common request than any of the others you listed.

What jobs?

[wilfie]

"What language makes the most sense now to get the jobs?" What jobs?

Just a thought

[RNLockwood]

Have you thought about one of the languages spoken on the Indian sub-continent?

Chinese

[asnelt]

I would go for Chinese.

Desperate for a Job

[hinchles]

I've deliberately omitted .NET — I have no desire to do the Microsoft languages.

Poster obviously has no desire to be employed either. Love it or Hate it C# is pretty much the only langauge in demand by big business these days in the UK unless he's perfectly happy doing small freelance jobs etc which PHP is fine. Other languages he's mentioned are all pretty much unused apart from in the domain of nerds but certainly not by the majority of the companies recruiting. Ironically enough I reskilled from C# and other .NET oddities to PHP a few years ago purely out of personal preference.

Re:Desperate for a Job

[HappyEngineer]

Don't get so emotionally fanboy about it.

You only need one job. Web developers are needed by practically every company. I don't know what percentage of all that is Java vs C# but as a Java programmer I know that Java jobs are trivially easy to come by.

In any case, objecting to C# is likely not an objection to C# itself. I personally think it looks like a great language. It's really objecting to all the stuff that's likely to come along with C# like Windows servers, IIS, VB scripts, IE only sites, Microsoft SQL Server, the attitude that cross platform development doesn't matter and a bunch of other crap that some of us don't want to have to deal with. If you don't have a problem with any of that stuff then that's your business. Don't blame anyone else for your eventual ulcers though.

Objective C

[drumcat]

Last I checked, being able to create apps with native hooks on the Mac platform is the hottest shit steaming right now.

Legalese

[El_Muerte_TDS]

Win or lose, either way you'll earn money.

Just C.

[Anonymous Coward]

No language is more universal. No language is more direct. It will never die. It transcends trends. It is the only decent language to me, having tried way too damn many in my life and always left wanting until I return to C.

It is the perfect language. People might gripe that it's somehow "obsolete" or missing "modern" features, but to me, that's part of its appeal -- you get to do with it exactly what you need to do, and that is the essence of programming to me. Leaving too much to the language makes me feel powerless and less in control.

I love C. If it was legal, I'd marry it.

Re:I avoided MS and work as .NET dev

[b4dc0d3r]

I intentionally tried to avoid MFC, and learned it anyway. I avoided .NET like the plague, and work moved me right back to the plague.

Since .NET 2.0 it's been a stable API, and if you're going to do web or web/desktop development, it's a good thing to have in your back pocket. And I'm saying this as someone who intentionally avoided it.

I picked up Prosise's MFC book so I'd know what MFC was doing behind my back, and I dropped wxWidgets once it became clear it was an MFC "port" - if you don't believe me read the wx history. I intended to stay classic MFC all the way, and learn something else - anything else (but Java, that's my ideology and just as unfounded). Qt and... whatever the dominant web language was in 2001.

I write .NET for a living. If nothing else, you can be read-only with .NET like I am with Java. I can search for an algorithm and find a public domain or otherwise compatible implementation, and if it's Java I can port it in a few minutes and have what I need - whether it's .NET or C/C++, which is where I prefer to work.

Learn .NET, even if you are working in a full open source shop. There are lots of open source programs available only in .NET, and a free compiler (not the GUI, just command-line).

I don't have mod points, so I'm just backing up dreamchaser (49529). I can write x86 assembly (att or intel), C (K&R, C89, C99), C++, VB5/66, VB.NET/C#, ASP 3, JavaScript, VBScript (cscript and IE), SQL (MS and Oracle) and lots of others less proficiently... so it's not like you can't learn multiple languages. In fact, the more you know the better. I write better .NET code because I think in assembly when performance matters. I write better ASM code because I think in OOP when code clarity matters. Yes, I probably need mental help, but the more you know the better you will be. The more ways you can think about something, the more solutions you can weigh when you have to actually implement something.

Here's the best part. Learn what .NET does *wrong* and avoid implementing that in your apps, or avoid using constructs like that in whatever language you get paid to use. Learning .NET has made me a better C++ programmer, far more than any other experience in my life. Both for the good parts and the parts that could be better.

You'll want to learn to use ILdasm if you go this route, no question. Obviously my vote is .NET.

Search sourceforge for stuff in .NET languages, C# is probably going to be more familiar, download the free compiler from MS, compile, make changes, and start reading.

I loathe Microsoft. I program in .net languages.

[gestalt_n_pepper]

Seriously. My life is made hell by one stupid microsoft idiocy after another day after day (I manage a server farm of Microsoft VMs). The fact that they treat their development community like crap (Classic VB, f'rinstance) and abandon products with... abandon doesn't help much.

Despite this, that's where the jobs are and all the crabbing of myself and the development community hasn't changed that. I hated MS in 2000. I hate it in 2010. I expect to hate it in 2020. And it's not going anywhere. Profits are up. Like the air, it exists. And I'll still be cranking out C#, ASP.net, or VB.net or whatever is called for.

Re:Don't pick just one

[indeterminator]

+1.

Don't learn the languages. Learn the the paradigms.

Once you know a paradigm, picking up a new language under that paradigm will be just "yet another language", and you can learn one in a week (or 7 in 7 weeks). Of course, it will take more time to actually become fluent in language specific idioms, standard libraries etc, but those are not rocket science either.

Re:There's your problem

[Anonymous Brave Guy]

.NET development is taking off whether you like it or not.

Sure it is, just like it was last year, and the year before. Get back to us when Microsoft actually rely on .Net and related technologies for their own flagship products like Office, so you know they won't declare those technologies obsolete when they want you to upgrade to the Next Big Thing like they did with Visual J++, Visual Basic 6, almost every database access technology they have ever published, almost every GUI API they have ever published, etc. The web technologies are looking like the next victims, given all the recent chatter about Silverlight and the resounding silence from Redmond where the defensive press releases are supposed to be.

There are many languages you could choose to learn today. History teaches us that almost all of the good ones that don't come from Microsoft will still be around tomorrow. In fact, Microsoft are pretty much the only player in the game that does actively kill off popular mainstream technologies that are still in widespread use.

Decide what you want.

[CFD339]

          If you want to be another common fish in a huge ocean, learn C# and sharepoint development. If you want to be hip and cool, but are willing to compete with low price coders from developing countries, go with LAMP development. If you want to be a big fish in a small pond and can self promote and communicate well enough to pull it off, pick something painful but useful to corporations ( Rational / Websphere / Oracle / Siebel / SAP development ).

I do most of my client based work using Lotus Domino as a back end server and data platform. The development IDE is freaking horrible compared to visual studio or pure eclipse. The documentation is poor at best. There are a lot of workarounds you have to know. In many respects, it's a terrible thing to have to learn. HOWEVER, I've been doing it for a long time and am very very good at it. I'm never short of work, and I can accomplish things with it for my clients in less time and at less cost than any other platform I've ever found. I also use visual studio to build desktop applications, c++ to write custom modules for my Asterisk servers, javascript for web front end stuff, bash shell scripts for linux back end stuff, etc etc etc.... Right tool for the job and all that.

              I know by writing that I'll draw a bunch of crap from cool kids that hate the platform I use to make a living, but I'm willing to bet most of them would trade annual incomes with me in a heartbeat if I gave them the chance. I've managed to have my own business for close to 18 years by focusing on what works rather than what's cool -- and by never letting myself be just another commodity programmer among a giant pool of people with similar (and frankly better) skills.

Re:Think carefully. Do you want to be close to MS?

[Jeremi]

Most of Microsoft's own software is NOT written in .NET. There is a reason for that.

Is it because most of Microsoft's own software was written before .NET was released?

Re:There's your problem

[the-matt-mobile]

Get back to us when Microsoft actually rely on .Net and related technologies for their own flagship products like Office

Nice little straw man you've built there. Sun never built Open Office or Solaris in Java, but you can''t be foolish to think that that was a vote of no-confidence in the future of Java. I'll judge .NET's success on two factors - employment opportunities and continued innovation and development from Microsoft. And let's face it - while a lot of copying and catch-up was done for the first few iterations of .NET, that was over and done with after the 2.0 release and ever since then MS has been blowing past everyone else out there. Visual Studio is arguably the best IDE out there, Linq was a total game changer, and ASP.NET MVC fixed the travesty that was the past decade of Webforms. The future looks really bright for .NET, and not so much for Java. But, things change quickly and I'm hoping that the Java community can pull itself together because MS does better when they are forced to compete.

There's no such thing as shrinking job market

[melted]

Where I work, I currently do one interview a week. I only said "hire" twice in the last year or so. Truth is, 95% of people I have interviewed so far couldn't write decent code on the whiteboard if their life depended on it, in _any_ language. Your fear is misdirected. No decent employer gives a shit about languages in a job interview. They care about whether you can write the fucking code, in the laguage of your choosing, and whether you have experience in the areas you're applying for. I.e. if you bill yourself as a backend dude, they'll want to see if you know e.g. distributed systems, and have the backend mindset. If you're a frontend guy, that's another set of skills entirely, but still very little (if anything) depends on the language. You can learn the syntax in two days. You can learn the libraries and language-specific idioms / patterns in 2-3 months (if you're proficient in at least a couple other languages). It's not that hard.

And if the employer makes the assumption right away that you _can't_ learn e.g. Ruby on Rails, to hell with them. You wouldn't like working there anyway.

I changed my attitude completely.

[gillbates]

The thing this recession taught me more than anything is that corporations have no morals, no ethics, and really, no just claim to fair treatment. They are not humans, and not deserving of anything more than that for which they pay. Not a dime.

Corporations - particularly large, publicly traded ones - routinely use "the recession" as an excuse to treat their employees like dirt. Get off your high horse - bowing down to your corporate masters so you can "have a job" only screws yourself and your fellow employees. Do us all a favor and stop working - or at least demand the respect that you, a human being, deserve.

The fact that the economy is in the toilet doesn't change the fact that you're a human being and deserving of the respect due a human being. If you think otherwise, well, you're just as much a part of the problem as the companies which exploit the poor economic situation.

Re:Don't pick just one

[melonman]

> Once you know a paradigm, picking up a new language under that paradigm will
> be just "yet another language", and you can learn one in a week (or 7 in 7
> weeks). Of course, it will take more time to actually become fluent in language
> specific idioms, standard libraries etc, but those are not rocket science either.

I know people who take the same approach to natural language. After all, Spanish and Italian are very very similar, aren't they? The reality with natural languages is that "all languages are the same" thinking enables you to abuse several cultures without actually understanding any of them.

And I think that to a large extent the same thing goes for programming languages. For example, if one of your "paradigms" is "object-oriented", does learning Smalltalk really prepare you for making best use of OO in Java or C++? Or vice versa? The inventor of Smalltalk and OO certainly doesn't think so.

I spent some time a while back trying to explain Scala to a Java programmer. His response was "It's just like Java." Well, Scala *is* just like Java, as long as you ignore the huge and central features that are not like Java. When I started to show him those features, generally in a "replace a page of code with one line" sense, his response was "I don't like it", and that was the end of the conversation. That, in practice, is what "learn 7 languages in 7 weeks" looks like.

My defining experience in this context was observing a government contractor whose preferred language was FORTRAN, who was told he had to code in Lisp. I would not previously have believed that it was possible to write Lisp as if it was FORTRAN, but that contractor proved me wrong. And, to be fair, I find that I have to make a conscious effort not to write C++ as if it is Lisp, eg "everything on the stack and screw the efficiency".

"7 languages in 7 weeks" only works if you stick to programming with the features that can be found or kludged in just about every language. Nowadays that's going to mean procedural code with loads of variables and a bit of OO for accessing libraries. It works, but it's a recipe for terrible, terrible code. But, hey, it will be equally terrible in 7 different languages!

Re:What about SQL?

[Cytotoxic]

I think it's typically assumed that if you know how to program, you ought to be able to interact with a standard relational database. There's almost no prospects out there for someone who does SQL and nothing else...

They actually have titles and everything. They are called DBA around my shop. The good ones are like old-school unix guys who wax poetic about their favorite shell script and kernel optimizations.

If you are a PHP or other front end developer who creates SQL to power it, you are very, very likely not a SQL master. A good programmer with experience can create SQL databases and queries that work well. His code will be amateurish and inefficient to a good DBA. They do the same thing OS programmers do, delving into the deep inner-workings of the database engine to find all the little tricks, optimizations and security gotchas.

Good DBAs tend to be more math oriented personalities than the larger developer population. Probably because they have to live in a world dominated by set theory and complex logic.

BTW, if your experience with DBAs is a bunch of Microsoft Certified Professionals who are proud that they can create a stored procedure to fill a ticket - then you haven't been working with a good DBA. Those guys are the equivalent of the "web developer" who can use the GUI development environment to put a couple of forms together. A good DBA will take that query that you spent two days optimizing to get from 15 minute run times to 2 minute run times and get your results in milliseconds. Often the optimizations they make won't even seem logical to the untrained - until you watch how much faster they run. They are able to do this because they've spent years focusing on one platform.

  Still don't buy it? Ok, a quick example. One of my analysts was faced with a set of tasks that was taking too long and causing application timeouts. These tasks involved importing and parsing millions of rows and then joining to many tables of tens or hundreds of millions of rows in a highly transactional environment. After banging his head against the limitations of the database engine for a week or so, he finally decided that he needed to expand the functionality of the engine. So he added a couple of customization DLL's to the engine (written in C#) to add two new commands with the features he needed. He was able to get an already well-optimized run time of two minutes down to about 35 milliseconds. Oh, and my team is already finding lots of other places to use the new features he added, knocking a few percent off of the CPU load on the server and improving response times.