Employers Want More Open Source Workers, Says Linux Foundation Study (zdnet.com)
As in past years, "Open source is professionalizing, and employers are seeking staff with demonstrable skills," says the executive director of the Linux Foundation, describing the results of a new study with Dice.com. An anonymous reader quotes ZDNet:
According to the two groups' 2017 Open Source Jobs Survey and Report, "Not only do 89 percent of hiring managers report difficulty in finding qualified talent for open source roles, but 58 percent report needing to hire more open source professionals in the next six months than in the six months prior"... Seventy percent of employers, up from 66 percent in 2016, are hunting for workers with cloud experience. Web technologies placed second, with 67 percent of hiring managers hunting for workers with JavaScript and related skills. This is up five percent from last year's 62 percent. The demand for Linux talent remains strong. Sixty-five percent of hiring managers are looking for Linux experts. That's down slightly from 2016's 71 percent.
The three most common positions that they're looking to fill are developer, DevOps engineer, and systems administrator, according to the study, and "a growing number of companies (60 percent) are looking for full-time hires, compared with 53 percent last year.
"Nearly half (47 percent) of companies will pay for employees to become open-source certified."
The three most common positions that they're looking to fill are developer, DevOps engineer, and systems administrator, according to the study, and "a growing number of companies (60 percent) are looking for full-time hires, compared with 53 percent last year.
"Nearly half (47 percent) of companies will pay for employees to become open-source certified."
Indeed. The only thing that sticks in the minds of employers who don't understand the open source model is that talented people will spend countless hours working on something basically for free, so they want that cheap talent, willing to work long hours, for themselves.
They don't want to pay them full salary.
What does it mean? Someone willing to work with open source? Someone willing to write it? How does skillset differ from closed source professional or blue tie professional?
money-making is not compatible with open source.
... unless that software is of secondary importance to the business. For example, websites make more money from a free OS (Linux), a free webserver (Apache), a free DB (MySQL), because they don't have to pay for all that software.
So the linux foundation says something, but no link to them. They base on something dice.com did, but no link to them either.
Frankly, by now I'm surprised to see anything but bleeping bleepingcomputer or similarly inane non-sources, but zdnet isn't that much better, so it's probably down to the editors having a better-than-usual day. But still. It'd be fairly trivial to actually read what's in the summary and spend a few minutes hunting down the sources, and linking them too.
I'm starting to think the new new new editors are secretly HR dropouts.
Wrong.
You can't sell open source, but you can make plenty of money supporting it. Like redhat. Or make money using open source for providing services. Apache is popular for being good - being free too is not a disadvantage. You make more money when you don't have to pay royalties. Even better if you have some people who can program the occational fix - so you won't need a consultant for that.
"89 percent of hiring managers report difficulty in finding qualified talent for open source roles"
When your job ad demands 7-10 years of experience in a thing that isn't even 10 years old then yeah, you might have some difficulty "finding quality talent" because you're being ridiculous.
Job ad bullet points are used as filters and do a great job (ha!) of filtering out all of the ideal candidates in favor of the ones that will gladly lie about their skill sets yet can't write anything more trivial than strcpy() on a whiteboard. Maybe you stop looking for "workers with cloud experience" and start looking for "workers that have great system administration skills who we'll train to use the specific 'cloud' thingy we're using this month." After all, what these job posts that demand a "hit the ground running" candidate fail to realize is that they have to train the new employee in the operations and peculiarities unique to their business anyway.
Pay a decent wage and write realistic job applications and give everyone who applies in earnest a fair shake and you might not have so much "difficulty finding quality talent."
Wtf is an open source professional?
Until you read the job description, which usually includes Active Directory, MS SQLServer, and so on. Drives me to distraction.
good grief.
developer: write code. gotcha.
systems administrator: write scripts, config management, handle infra. gotcha.
DevOps engineer do neither. Write code in a shitty open floorplan office, get hounded for using noise cancelling headphones and working from home, endure nerf fights and microbrew on a tuesday because the CEO decided the devs were too gloomy for his investors to look at, and the burndown didnt matter anyway. Break incessantly from your coding job to go play sysadmin poorly. get overbooked to ops meetings, burn out and quit.
seriously, devops is a cancer. it only makes to @botchagalupe who uses it as a vehicle to pay the mortgage. It pisses off sysadmins by turning shit like NTP into a fragile 'microservice' of hypervisors and poorly documented ruby layers. it pisses off devs by making them take an oncall shift for an OS theyve only ever deployed to.
Good people go to bed earlier.
"Nearly half (47 percent) of companies will pay for employees to become open-source certified."
So nearly half of the companies are incompetent, then!
You don't get open-source certified anywhere. Unless they actually look at your portfolio of open-source contributions. There is no certification instance. Look at Linus Torvalds or Richard Stallman - neither is "open-source certified", although they define large parts of the open-source landscape.
Errrr, you certainly can sell open source software, with most licenses, but you need to make source also available for free or at most distribution costs.
young, attractive women want more rsilvergun. Now I wonder if I can get a job at the Linux Foundation doing studies...
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
A developer who doesn't use Visual Studio/Oracle DB/...?
A developer who will take his employer source code and drop it on GitHub?
A developer is a developer. Using Linux/Postgres/OpenLDAP/... doesn't make you an "Open Source" developer.
Will $CURRENT_YEAR be the year of the Linux Desktop?
Review Redhat's annual report. They trail not only their peer group, but the S&P 500. And they turn about 10% net profit. Better than grocery stores, laughable for a tech company.
Browsing at +1 - no ACs, I ignore their posts. So refreshing!
Everyone is hiring any developers. The problem is they do not give work from home.
All of my prior work experience has been in environments that use open source software exclusively, all software I have ever written is open source. What do recruiters tell me when I present my resume full of open source?
"Sorry you don't have open source skills."
Thanks for lying, Dice.
I have been programming on *NIX for over 30 years. Drivers, distributed network code, GUI, back end applications, user applications, number crunching. Never heard of open source qualified.
When you spend countless hours working on something for free, don't cowardly work anonymously. Always blog and git and tweet and twitch everything. Don't be that talented antisocial basement dwelling guy. Always be social, always advertise your brand, always pimp your skills, or you're not even cheap, you're worthless.
You can sell open source at market price, and the market price is zero. That was Stallman's plan all along when he vowed to remove software from the realm of competition.
You can't sell open source
Yes you can sell open source software under various licenses. However, you have your terms confused.
Free software is a subset of open source software often licensed under the GPL. There is nothing in the GPL that says you can't sell the software. When you transfer your binaries, however , the GPL license requires that you provide your customers with four freedoms:
The freedom to run the program as you wish, for any purpose (freedom 0).
The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
The freedom to redistribute copies so you can help your neighbor (freedom 2).
The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.
You can sell software using other licenses, such as BSD and Apache. Both meet the definition of Open Source, but do not convey the rights listed above. In fact, these licenses allow you to relicense the code as proprietary. For instance, a quote from the Apache license:
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
This is how Apple has legally built it's operating system on top of the Mach kernel and BSD Unix. They sell it, and they have relicensed it. A person contributing significant code to these projects is therefore unable to acquire their own source code from Apple. This loophole renders these licenses as non-free.
The correct response is "As they should. If a business wants employees who can do X, then the business must make them".
The realistic response is "Bullshit"! What's the business case for -that? An employee can code or can't, a business uses open-source or it doesn't, a business contributes to its open-source tools or it doesn't: None of that is improved by certification, let-alone paying for said certification.
The business case for certification is "Look; we're a better business because we follow procedure 1-2-3". Until such administrative pride filters into IT departments, there is no need for certification and definitely no reason to pay for certification.
Even that isn't the whole issue: This is certification of the employee, not the business; which is a problem. Namely, that employee and that certification can walk out the door. This is why businesses don't pay for employee training: They have to either enforce a repayment contract, or pamper the employee so he doesn't leave. Employees are meant to be disposable and replaceable cogs, not unique and valued resources.
Says the Linux foundation.
"Employers want more employees to become open source certified... says organizations that make their money off of open source certifications".
I don't need a fucking $5,000 certification on top of $5,000 worth of courses. I've been doing this shit for 20+ years. Go fuck yourselves.
Your an idiot
The report you linked shows gross profit margin is around 85%.
Gross numbers are meaningless without considering liabilities.
IBM managed to convince Cobol programmers that the world is divided into "mainframe" programmers and "PC". This is so inculcated into their brains that many of them still use those terms. I am not sure if a smart phone is an IBM or a PC, but IBM mainframe Cobol harkens back to the days when the entire os memory model allowed for no more than 640K of memory. But as long as you convince everyone who is willing to listen that not being one of "yours" is one of "others", you are golden. Just sprinkle some "open source" dust on it and it'll owrk. Oh, go ahead. Show me how to compile (open source) Docker with the network cable pulled out.
Any guest worker system is indistinguishable from indentured servitude.
And you just ignore that Stallman financed himself and FSF in the early years by selling GPL licensed software? His plan has never been about the price of software.
"When the wise point his finger to the moon, the idiot looks at the finger". Pixel had very low return of investment, for ten years. Few "glorified account" with silly titles would have seen any value, in what turned out to be a gold mine. Stevens job did... and stroke gold. Pragmatism is for the mentally challenged. Understanding for the wise and smart. A.G
Could not agree more. Furthermore, almost no one in HR understand engineering.
All of those things apply to proprietary software too. And in top of that you need a team of lawyers to negotiate contacts plus full time staff, expensive tools and often nasty workarounds just to manage license compliance alone.
tell this to red hat, too.
A great summary, but it's a bit disingenuous to describe that as a "loophole"; it's by design.
No I am not ignoring history. Market value was higher in the old days when duplication was expensive. Back when Stallman was selling tapes of free GNU software, I knew a guy who sold pirated commercial software for a duplication fee, and the business model was exactly the same. Guy obtained software for free, and then he copied onto physical media and sold the copies for profit. These days duplication cost is essentially zero with flat rate hosting and free internet connectivity everywhere. Stallman's plan was to eliminate competition and he did. Everyone can undercut everyone else so everyone sells free software at market price, and market price today is zero.
employers want...but are not willing to pay.
You are correct, at least in my experience.
I worked at a Fortune 100 company for over a decade and they openly said they were for open source, but they kept killing off all the open source projects and replacing them with .NET equivalents. They were particularly pissed at a system I built that the customers loved and they refused to be moved to the super expensive fancy .NET platform built just to replace it.
Quick question: do you bring home your gross pay or your net pay? If you have a gross income of $100,000 per year, but your living expenses are $110,000 per year - is that a good thing? Gross margin is irrelevant.
Browsing at +1 - no ACs, I ignore their posts. So refreshing!
Redhat has been around 24 years, and went public back in 1999 - 18 years ago. They aren't really that new, nor is what they are offering. It's been around for a generation. And I assume you mean Pixar, not Pixel? Pixar was a money loser until they partnered with Disney, and that's the reaosn Disney ultimately bought it. Until it was hired by Disney to do Toy Story, Pixar was slowly losing employees, shedding about 60% of its workforce - and all its hardware lines - over the course of 10 years or so.
Browsing at +1 - no ACs, I ignore their posts. So refreshing!
There are many more qualified programmers sitting on the sideline than they need. The problem is not that it is difficult to find workers. It is that it is difficult to find workers who will work for the low wages that they want to pay, especially if it requires moving to some of the ridiculously expensive locations they insist on placing their operations in.
They know this and often advertise jobs that they have no intent to pay to fill to create the illusion that there is a shortage. This helps in their case to bring in more offshore talent that will undercut wages.
They have the money as shown by their profits and the outrageous wages paid to those higher up the chain.
Somehow, the normal capitalist formula that says wages should rise to balance the supply has been broken. I believe it is largely due to them having enough success to not care and a reduction in the consumer's pickiness on product quality and features. I'm sure there are other factors.
So when your revenue model is 'give away the software and sell the support', how much incentive is there to build a great product that is easy to install and understand and has few bugs? It seems to me that anything that would cut down on the need for support would get a low priority. Maybe it is just me.
Hi kids,
20 years of Sysadmin experience. RHCE, CISSP, and AWS CSA-A.
Nobody will even talk to me unless I match the buzzword search.
And then they want to lowball the pay.
Want to bet? I am working in a bank. They are *ALL IN* on open source. Not because it is 'profitable' but because it is free software that usually costs huge sums of cash. I am watching major software skipped over because it costs money. Not because it is better or worse. You can set up a dev for cost of hardware now. The 'ms tax' was about 1500-4000 per dev. Now it is half that. Make no mistake everyone is using it. Because it is cheap. Not because it is better. In some cases it is the best there is. But they care not for that.
'Cuz tweeting is far more valuable than actually making software.
What is with the extraneous "an"?
That sounds exhausting. So rather than doing what I love I should talk about doing what I love? And make (presumably nude) videos about it?
Employers are missing the point.
If employers want more "open source workers", then they shouldn't mandate we use crappy commercial OSes.
I never want to be forced to run OSX or Windows or to use Outlook.
I don't have any "certificates", but I've been using F/LOSS for over 25 yrs. Seems that I am not qualified for any of these positions.
I imagine that gets easier to judge a good candidate from a bad one when you can actually read his code.
I think the fact that a hiring manager is looking for more open source people is a big indicator they have no clue what they even need. What is an Open source worker? Git hub has over 4 millions open source projects, old school Sourceforge has a little under 1/2 million projects. SO you want someone familiar with 5 million projects? Top that off with they want 10 years experience for something that is only 4 years old. Several job post out there now that want Docker engineers with 10 years of experience..
Market value for the software, or a copy of the software? There are two parts involved in software development: writing the software and copying it. Writing it costs money, copying it is essentially free. Open source makes it harder to charge money for copying software, but makes it easy to charge money for writing it. In contrast, proprietary off-the-shelf software involves writing software for free and then charging to make copies of it. Which do you think makes more economic sense?
I am TheRaven on Soylent News
let the work show for itself, i'm not trying to sell myself i'm trying to get work done.
Preach. That is what companies used to do, find good prospects and offer training. Now the illusion of "push button recruiting" and the expectation that you need to come onboard with training/certs has killed that off. The irony being that some of the training requires corporate membership of some sort, which means companies would have to work at employee retention. Which many refuse due to the push-button-recruiting illusion.
> Pay a decent wage and write realistic job applications and give everyone who applies in earnest a fair shake and you might not have so much "difficulty finding quality talent."
C'mon, that's just silly.
They want to make as much money as possible, and money-making is not compatible with open source.
That's strange Redhat seems to be doing just fine and is a billion+ dollar (US) company.
Basically, the software is free but the services and support are not.
They want Open Source contributors that will work for their for profit functions, for free.
IT's not about workers, again it's about paying them,,, at all really.
If I recall correctly.. Are we specifically referring to the version of GIMP that Pixar hacked up to make Cinerella? And that's why pixar came up in the conversation as an open source company?