Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Open Source Programming Stats IT

What Keeps Developers Happy? Contributing to Open Source (techrepublic.com) 64

This week long-time open source advocate Matt Asay warned employers that the best way to keep their developers happy was to let them contribute to open source projects: SlashData recently surveyed over 16,000 developers to see what makes them tick... what they care about. The data is collected in SlashData's State of the Developer Nation, though let me give you the tl;dr: 59% of developers contribute to open source software today. Why do they contribute? The top two reasons are: To improve coding skills and because they believe in open source.

Want to keep those developers happy and employed with you? Let them contribute...

[Y]our employees want to contribute both code and knowledge — they want to be part of something. Talking to Bert Hubert, founder of PowerDNS, a supplier of open source DNS software, services, and support, he stressed that an open source project must be "a fun place where people feel that they are learning things, that they're contributing things, that they're being valued." Perhaps not surprisingly, these are the same elements developers expect from their employers. By making open source a valued part of workplace expectations, employers tick both boxes.

Is it an absolute requirement that you encourage your developers to contribute to open source projects? No. But many of your best developers will chafe at keeping their talents locked up behind the firewall, and other developers simply won't apply if you have a reputation for being an open source scrooge.

The article was written by Matt Asay, a former COO of Canonical now working at AWS. (Right before becoming Canonical's COO, Matt answered questions from Slashdot readers).

The survey he cites also found that out of 17,000 developers they talked to, just 3% said they were paid to contribute to open source.

The other 97% contributed for free.
This discussion has been archived. No new comments can be posted.

What Keeps Developers Happy? Contributing to Open Source

Comments Filter:
  • by Anonymous Coward
    Oh wait, wrong forum.
    • This isn't the "What to do With Your $1,200 Stimulus Check" forum.
      • Yes, but successful developers didn't qualify for stimulus checks, just poor ones.

        • Wow, you consider under $150k to be a failure, eh?

        • Mostly, but there are some exceptions. Developers for non-profits and governments often get wages that are well below market. Somebody working for a non-venture funded startup might be sacrificing current wages in exchange for an ownership stake that could be very valuable if the company succeeds. Developers in small markets well away from the big high wage cities (San Francisco, New York, Boston, Seattle, etc) are likely to be eligible for some amount of money, especially if they have a non-working spouse.
  • Make a difference. Like everyone else in the world.

    Often, that is kids.
    For developers those kids may be in code form.

    • There's also a few tons of garbage, some of which will endure for a thousand years.
    • like most things man produces, today's code is in tomorrow's /dev/null
    • Be honest... For developers, the only kids they will have will be digital.
    • Maslow's Hierarchy of Needs

      1. Physiological needs: The job should pay enough to buy you food and shelter, as well working conditions should be clean and healthy.
      2. Safety needs: Work should be steady and pay is enough to buy more then you just need to survive. This is where you have enough for a Mortgage and raise a family.
      3. Love and belongingness needs: Here is where your work is appreciated and you feel like you are part of a team.
      4. Esteem needs: Where you work is recognized and you get praise and rewor

  • by Viol8 ( 599362 ) on Sunday May 03, 2020 @03:00PM (#60018430) Homepage

    Sure, making some nobel contribution to OSS to feel part of something bigger than yourself blah blah psychology 101 etc works for the kids, but for those of us with mortgages and families to support money is a better bet.

    • by west ( 39918 ) on Sunday May 03, 2020 @03:28PM (#60018502)

      I suspect the employers whose work force cares heavily about Open Source and employers whose work force have mortgages and a family is a pretty small intersection set. And I suspect that it is the former set of employees that answers surveys like this one.

      This is good advise for companies whose coders are under 30. For companies where most of the coders are 40+, not so much.

      • I suspect the employers whose work force cares heavily about Open Source and employers whose work force have mortgages and a family is a pretty small intersection set.

        I have a mortgage and a family, and I get paid to work on open source. I would not take a comparable job working on closed source, for many reasons. If you wanted me to work on closed source, you'd have to make me a much better offer to compensate.

        This is good advise for companies whose coders are under 30. For companies where most of the coders are 40+, not so much.

        Oh, and I'm 50+. Come to think of it, in a very few years I won't have any kids at home, and could have my mortgage paid off if I wanted. So will that put me into your category of people who could care heavily about open source?

      • by twms2h ( 473383 )

        I suspect the employers whose work force cares heavily about Open Source and employers whose work force have mortgages and a family is a pretty small intersection set. And I suspect that it is the former set of employees that answers surveys like this one.

        This is good advise for companies whose coders are under 30. For companies where most of the coders are 40+, not so much.

        What makes you think so? I know many contributors for open source projects who are 40+. I am one of them myself. And no, I don't get paid for it. Admittedly I don't have any kids and neither a mortgage to pay, but that has nothing to do with my open source activity. (The first is an accident, the second was a personal choice.)

    • Sure, making some nobel contribution to OSS

      If you did make a Nobel-level contribution, wouldn't the prize be worth a couple of pay rises?

      • There is no Nobel prize for software engineering, information science, or computer science, so you're not going to get a Nobel for anything that is purely about being a software developer. Nor is there a prize for mathematics, the field that is most likely to directly intersect with computer science. You might get a Nobel if your work intersects with an area that does have a prize: physics, chemistry, medicine, economics (not a Nobel in title but awarded by the same people), or conceivably the Peace Prize i

    • Working for OSS also means you can have more visibility and show others what you have done. Which means it's better for your resume, and you can more easily get hired somewhere else ... which means money.

      So definitely more like a long term investment than a pay increase, but good for your career if you intend to switch companies at some point.

  • You get to pick which open source projects you work on and as a result you probably have some motivating factors for picking that project. I would imagine people would be similarly happy with their usual jobs if given that much freedom, but someone has to write god-damned login page.
    • Absolutely this.

      It isn't that contributing to open source makes people happy. While that does apply to some people, it's not universal.

      It is that doing what they enjoy rather than doing what makes a profit and paycheck makes people happy. Some people enjoy certain projects, and open source allows collaboration so you can make large things as a group without the structure of the corporate environment. Other programmers do other things that they enjoy, such as playing games, flying kites, building a boat,

  • All developers are welcome to help creating an OS/2 Warp open source clone !!!!
  • And here I thought it was raise was how you showed employees that they are valued. -_-

    • And here I thought it was raise was how you showed employees that they are valued. -_-

      This special story brought to you by your employer.

    • by Junta ( 36770 )

      Fun story, in the last 'Agile' training we were forced to attend, the trainer was going on and on about how paying coders *less* was the way to make them more productive, totally misinterpreting various studies where highly paid participants tended to do worse at the tasks than lower paid ones.

      The training was consistent in this respect between managers and employees, both being told that the work is where to find fulfillment, not pay raises and bonuses. Thankfully they seem to recognize that we will work f

  • I thought it was free peanuts that made developers happy?
  • That's because we developers are bossed around every day by deadlines, unbearable managers, unnecessary meetings and non-existent specs which suck away all the joy from coding. Yet, we all love what we do for a living. That's where open source comes in. It's our safe harbour. The space where we can sit down after a stressful day and enjoy our craft in peace and quiet, on our own terms and where we are appreciated for our efforts. For some of us it's the only thing that keeps us sane in the crazy business wo
    • by jonwil ( 467024 )

      Until you run into an open source project where the maintainers make it hard enough to actually contribute (e.g. being really really picky about coding style) that the motivation to get stuck in and write code goes away.

      • Then you move on and find a project which matches your style. Although from my years of experience as a programmer and team mentor I find that those who complain about others being picky and overly critical when it comes to following strict style guidelines are usually too cocky to take a step back and learn from what the more experience are trying to teach - that following a common coding style allows for better readability and easier maintenance because the code reads in a uniform fashion and everyone is
        • by Junta ( 36770 )

          Of course, then sometimes there is insanity.

          For example I got to be in the middle of two people who cared way too much about whether to enabled W503 or W504 in pycodestyle (since they say exactly opposite things to each other). A purely subjective opinion that most people don't mind being one versus another, but two folks cared vehemently about it and bothered everyone about it.

    • by Junta ( 36770 )

      I will say that my professional coding efforts are pretty rewarding.

      The key has been to say no when it is appropriate. I don't quite understand how it happens, but useless work tends to be generated, and successfully cutting things out generally earns gratitude. Not perfect by any means, it works easy enough when it's clear it kind of 'evolved' generally out of miscommunication with no one wanting it, and sometimes you have to go along with pointless work when there is a stakeholder that did cause it, but i

  • The key to happiness in the labour market is money.

    If I'm selling my labour, getting the most money possible is the thing that makes me happy.

    If the person buying my labour wants to give away the thing he pays me to produce, that's fine. But I want to get paid.

    • Some people contribute to open source as hobby. I don't need any more money, seriously. I get money during workdays being devops for open source OS.

    • The key to happiness in the labour market is money.

      I used to think that, too. When I found a job that paid a LOT more than I was making, I took it. I then realized that I didn't like it, and went back to my old job. I'm happier at my old job, even though I make less.

    • by Anonymous Coward

      If this were true, then why are you wasting your time and talents in software development? Okay, so maybe "fetishist for hire" is out of the question, but seriously you could probably make more money spending all the time you spend on staying abreast of new technology on perfecting the art of negotiation, working on your social game and pushing to get into upper management. Especially once you become a manager of managers, by then, no one cares if you coded in some antiquated if obscure and difficult lang

      • by wilsong ( 322379 )

        >> "why are you wasting your time and talents in software development"

        That's a statement of fact that's entirely invented by you. I moved on some time ago.

    • by twms2h ( 473383 )

      The key to happiness in the labour market is money.

      If I'm selling my labour, getting the most money possible is the thing that makes me happy.

      I agree: Earning enough is the prime motivation. But once I got there (25 years ago), contributing to Open Source projects turned out to be quite a factor for staying happy, especially when the work I did for money wasn't that great.

    • Only to a point. Happiness has been extensively studied, and it was found that more money only makes happier up to a certain point, which lies somewhere in the neighborhood of US$75,000 per year. (Obviously that number will vary depending on the cost of living where you live; $75,000 in Omaha is comfortable but $75,000 in New York is not. And most of the data is from a few years ago, so the numbers will be slightly higher now due to inflation.) Additional income beyond that has little or no benefit.

      Up to th

  • by Brett Buck ( 811747 ) on Sunday May 03, 2020 @03:23PM (#60018482)

    So you asked a bunch of open-source zealots what they liked, and it was "contributing to open source"? What a stunning and remarkable result!

          What about the rest of the world (which generally had no interest or otherwise stake in open-source? What motivates them?

  • Anyone know how this data was collected? Just saying “a survey” doesn’t cut it. How were the respondents selected? Did they self-select?

    I went to look at the SlashData survey, but it requires registration - now why would I want to register just to view one article on a site I’ll likely never visit again?

    Anyway, it’s difficult to know what merit this report’s conclusions have - if any - until / unless we know what the methodology was.

    • That "59% of developers contribute to open source software today" sounds ... completely implausible. I'm not buying that they actually surveyed a representative sample of all developers. (If they can show that they really did, then I'll eat my words, but I don't think I'll have to.)

      • by pjt33 ( 739471 )

        What counts? According to Github I "contribute" to open source whenever I fork a project, even if I don't make any changes to my fork; or when I open an issue. I have actually made some genuine contributions to open source projects, albeit very minor contributions and mainly to minor projects, but it's probably still an exaggeration to characterise me as an open source contributor.

  • All the children of the world, coming together to sing a song of peace.
    And money.

    (Honestly, a useful product that I enjoyed developing. That and crushing my enemies and hearing the lamentation of their women.)

  • Was it just me or did others think the answer to the question: Want to keep those developers happy and employed with you? Let them contribute... should have been written "Pay them to contribute!" instead?

    As far as I know, almost no company has a policy that prevents their developers from contributing to OSS in their spare time. I doubt such a policy would stand up to a lawsuit in any case. The authors of the article want companies to pay their developers for the time they spend working on open source proje
    • by unity ( 1740 )
      I had a couple employers back in the .com wild west that tried to get me to sign contracts saying they owned anything I produced 24hours a day even if completely unrelated to my work. that would preclude contributing to OSS.

      I refused both times and they backed down when I told them I would walk rather than sign.
  • I can tell you what trends are now expected in web design in 2021. Even now, experienced experts are preparing for these fundamental changes. That's why I can't fall behind. And I can only try to suggest in which direction it is necessary to move now. I recommend, for example, to study this article https://merehead.com/blog/8-in... [merehead.com], here just the same professionals talk about trends in web design in the next year. Those who want to be ahead of all this is important to know!
  • by jmccue ( 834797 ) on Sunday May 03, 2020 @04:15PM (#60018596) Homepage
    Get rid of Agile and all such methodologies. Let the developers work directly with the users. In the 'old days' (tm), we did that and we were so much more productive than dancing around using jira, rtc, carnban all other such tools.
    • (regarding Jira) While I don't work on any agile projects where I work, I still have to use it for time tracking/information logging. Perhaps it is a limitation of their cloud-hosted offering, but I find it to be obnoxiously slow; similarly, making a simple edit to something in Confluence takes far longer than it seems like it should. Barely usable in Firefox with 10+ second page loads in most cases; somewhat tolerable in Chrome (5+ second page loads, but you still need to wait for the entire page to load b
    • by disoma ( 6829554 )
      I think any developer will make happy that his product is in demand and relevant. Also, the specialists of the developer's company will be pleased if they will be heard and listened to their advice. Use DevOps Consulting Services https://mangosoft.tech/experti... [mangosoft.tech]. Enable IT developers to evaluate your current IT capabilities, develop a business case, audit the maturity of your app lifecycle, and google your DevOps roadmap to achieve your business goals. And this work will bring a positive result
  • Comment removed based on user account deletion
  • by deodiaus2 ( 980169 ) on Sunday May 03, 2020 @06:20PM (#60018966)
    They will say money and power.
    Open Sources is fine, but I would be pissed if I were to know that a lot of the software is being used by corporations who use it to avoid paying for licenses on such software. In the end, some company like RedHat sells themselves to IBM who end up using it for their back end processing. Great, but I think that those developers who contributed to it got short changed, even if they knew it was going to happen.
    Similarly in drug research. Scientists work getting paid by the public from Federal Grants. If they develop something valuable, corporations take over the clinical trials to bring it to market, but never really paid all the upfront costs, especially for research that was not successful.
    I wrote some OS software, but I have had people ask me to support it by adding features. I could, but my time is valuable and I would rather be doing other things, rather than "just" developing software. I am also interested in Astronomy, Mathematics, Physics, [Kant] Philosophy, Computational Neuroscience and developing my karate.
    • Scientists work getting paid by the public from Federal Grants. If they develop something valuable, corporations take over the clinical trials to bring it to market, but never really paid all the upfront costs, especially for research that was not successful.

      The grants provide research for things the private corporations would never take such a risk on. Once it's proven (or close to it), it's more efficient for the private capitalistic sector to take over. The researchers got to work on something they're passionate about, which probably wouldn't happen in private industry (due to risk). Sometimes they'll get hired by the private companies to continue their work. Nothing is wrong about this picture. It's a good intersection of socialism and capitalism, using eac

      • Well, we have now a society with the worst of capitalism and worst of socialism. Privatize the gains and socialize the gains. Worse, people are now thinking that that is a good idea! It is now called friction free capitalism!
        The same is happening with the buying the corporate debts that companies incurred to buy back their own stock. Boeing took out debt $100B to pump up their stock price 4X, using low interest loans.
        Or the bail out of the American investors in the Mexican oil pipelines in 2000!
        Sort
  • What developers want are the same things every worker wants: higher pay, career development, and autonomy.

    This "study" seems aimed at shitty companies that are unwilling or unable to provide those obvious, proven incentives.

  • Selection bias.
  • During 30 years of programming, I have worked for companies across several industries. I have not yet worked for a company that allows, supports, or even acknowledges OSS contributions or participation. Out of the 100s of developers with whom I am personally acquainted, I know a very small number (10) of developers who work for companies supportive of OSS work. Where are these 59-percenters?
  • Whoever said money can't solve your problems must not have had enough money to solve 'em.
    https://archive.vn/qW7jE [archive.vn]

This is the theory that Jack built. This is the flaw that lay in the theory that Jack built. This is the palpable verbal haze that hid the flaw that lay in...

Working...