Critiquing Claims of an Open Source Jobs Boom

snydeq writes "InfoWorld's Bill Snyder examines what appears to be an open source job market boom, as evidenced by a recent O'Reilly Report. According to the study, 5 to 15 percent of all IT openings call for open source software skills, and with overall IT job cuts expected for 2009, 'the recession may be pushing budget-strapped IT execs to examine low-cost alternatives to commercial software,' Snyder writes. But are enterprises truly shifting to open source, or are they simply seeking to augment the work of staff already steeped in proprietary software? The study's methodology leaves too much room for interpretation, Savio Rodrigues retorts. 'That's why the 5% to 15% really doesn't sit well with me,' Rodrigues writes. 'I suspect that larger companies are looking for developers with a mix of experience with proprietary and open source products, tools and frameworks,' as opposed to those who would work with open source for 90 percent of the work day."

Duh?

[sexconker]

Companies want people who have open source experience - both use and contribution.

They want to use these people to implement open source projects that fit their needs, for free (beer).

They do not want these people because they love free (open) software.

As a 17 year IT consultant...

[infinite9]

I've seen a lot of shops. And a lot of them like open source for one reason... it's cheap. Not because they're cheap bastards, but because free software often can circumvent the corporate BS associated with spending money.

Once a place has used some open source software, they tend to keep using it. And they tend to want to hire people who know how to use what they have. I wouldn't call it an open source hiring boom. I'd just call it acceptance.

Re:I am with Bjarne on this one.

[jrcamp]

That's like saying since drag racing cars are the fastest cars everybody should be driving one.

Re:I am with Bjarne on this one.

[LighterShadeOfBlack]

You're making the insanely simplistic assumption that one language is appropriate in all parts of a given application/project. Yes, obviously anything that's truly resource/speed dependent will generally require a language like C or C++ to allow you to get intimate with the lower-level aspects of the given system. Which is why just about any newer language makes it simple to create native language modules and packages allowing you to take all the advantages of a tightly coded core with the convenience of writing the majority of code in a high-level language.

I don't think there's anything truly new about that concept and I certainly don't think it's responsible for any kind of 'backlash'.

Re:The cheapest code...

[Lord Ender]

No! The cheapest code is the code that doesn't require support, maintenance, or bug fixes! Development costs are trivial compared to upkeep costs.

Re:I am with Bjarne on this one.

[Reverend528]

C++ may be better than python/ruby/java for certain applications, but it will probably always remain in C's shadow.

Me too...

[iamhigh]

Looking at sysadmin jobs, I also see things that want Cisco, RedHat/Some *nix, MS AD, some sort of DB, this ERP app, that specific app, Citrix, scripting, programming, web development, website hosting, blah, blah, blah... Those that have a salary range, are in 55-60K

I think HR just throws all in the listing... get as many applicants as possible, sort it out later.

Re: IT degree = waste of time

[sfcat]

I make about 3x that working as a Java developer for an investment firm. And I can make even more as a contract dev. But that is in SF where the cost of living is very high. 60K in a rural area is probably a better salary adjusted for cost of living than I make. But 60K in the bay area is very tight and means you will either live in a dangerous area, live very cheaply, or live far away (long commute). Your choice. But if you think a programmer's salary isn't very high then either you aren't very good at programming or you have a very different idea of "making a good living" from most people. Try living on a construction worker's salary (or a junior QA person's salary) in the bay area and you might change your opinion.

Re:Startup = Open Source Only!

[Rycross]

So the assumption is that someone who has worked with proprietary technologies is incapable of working with OSS technologies? Because I'd say thats pretty much completely contrary to my experience.

I work with propriety technology ATM. Didn't stop me from opting for CruiseControl.Net and NAnt over the proprietary build systems that were vying for our business. There are plenty of technologies we're using that I'd switch to OSS alternatives in a heartbeat (goddamn ClearCase...). Yeah, some of my coworkers have drunk vendor kool-aid, but plenty others are open to the OSS side of things too.

I would say that putting that kind of arbitrary restriction on your hiring process may be cutting you off from some valid talent. That is unless you're looking for someone religious about it, then I guess it would be perfectly valid. Just some food for thought though.

Hedging their bets

[PPH]

A 5 to 15 percent figure for open source skills doesn't necessarily mean 5 to 15 percent of the projects will be open source. More likely, IT managers are getting smart, keeping their options open and making sure that they have a back door out of the lock in trap. A broader range of experience is also a sign of someone with a better background in CS rather than a one language/one tool technician.

This sounds like a smart tactic. In fact, I'm surprised that the figure isn't higher. And I'm particularly happy that the proprietary platform fanbois are getting their panties in a bunch over only 15 percent.

Comment removed

[account_deleted]

Comment removed based on user account deletion