4 ms·
Open source won't pay your mortgage or buy you that yacht. It won't get you a job. It isn't going to help your resume potentially. And if you're doing it for a
by vorpalhex 7y ago
Open source won't pay your mortgage or buy you that yacht. It won't get you a job. It isn't going to help your resume potentially.
And if you're doing it for any of those reasons, then stop doing it because you're missing the point.
Do it because you care about what you're building. Do it because you want to share your solution with the world. Do it because you want to contribute.
- ummonk 7y agoWhy would anyone want to contribute solutions that others can profit off of for free? It seems really weird to me that there might be people who actually want to do this kind of charity.
- SolarNet 7y agoWell in the case of GPL it's to build a public commons. Part of GPL is to ensure that that public commons is maintained (it can be profited from, but not exploited). This article is likely referring to mostly permissive open source, which yea allows people to profit. We build a commons upon which better software can be built. People write open source to improve those commons, not for charity.
- csande17 7y agoIf you already wrote the solution for your own personal use, it can only benefit you to open-source it so other people can contribute improvements. (But sure, it might benefit you even more to sell it or distribute it as adware or something, depending on how useful it is.)
- harperlee 7y agoIn my case, even from a self interested point of view this makes sense: this only applies to improvements and bug fixes on some Clojure libraries, but: If I contribute back to a library I use, I can raise the probability that other people use it and contribute to it, thus ensuring that my dependencies keep fresh; and by sharing work I’d do nonetheless, I do not lose anything. On the other hand if I keep my changes to myself, then I do not gain anything, but I contribute to the withering of the environment Im building dependencies with.
- ummonk 7y agoContributing bugfixes, sure, but that's different than providing a project you've written yourself for free to others and continuing to invest significant work in maintaining it.
- jlg23 7y ago> Why would anyone want to contribute solutions that others can profit off of for free? For me: * I profited off free software that could have been sold as well but was not (25 years BSDs and Linux). * I rather see my code in use because it means it solves a real problem and it does so in a good way. If I wanted to invest time into turning this software into money, I could. If I don't, why shouldn't somebody else be able to invest his/her time to turn that into money for him/her?
- gridlockd 7y ago> Why would anyone want to contribute solutions that others can profit off of for free? Why does that matter at all? What's wrong with others profiting from something that you can't profit from yourself? Most FOSS software that is commonly used couldn't be sold for a profit by itself. It wouldn't be used if it wasn't free. Yet, it marginally lowers the cost of software development. The compounding effect of that is massive. Despite what the GP says, developing FOSS can open up opportunities that you wouldn't otherwise have had. It's just not guaranteed.
- johnisgood 7y agoWell, perhaps it makes them feel good. Why is it weird? Some people volunteer at hospitals. I do not find it weird. In fact, I wish there were more people like them. :) Maybe the world would be a better place, who knows.
- decebalus1 7y ago> And if you're doing it for any of those reasons, then stop doing it because you're missing the point. Baah.. As long as you're doing a good job and writing good software, I don't give a flying fuck why you're doing it. And please don't stop OSSing because of random idealistic gatekeeping bullshit.
- vorpalhex 7y agoNone of what I listed was idealistic. Don't work for free and expect to get paid or a job.
- johnisgood 7y agoWho cares why they are doing it? There could be more than one reasons. One of those reasons could be showing it to their potential employer. It may increase their chances of getting hired. Of course it may also decrease.
- tathougies 7y ago> It isn't going to help your resume potentially. Of course it will. I mean, this is like saying 'making beautiful pieces of furniture won't improve your career as a woodworker'. It's always a benefit to have projects in your portfolio in any kind of skilled trade, whether done for free or pay.
- DasIch 7y agoThat's assuming you're making the equivalent of "beautiful pieces of furniture". There are quite a few people with open source contributions on their resume or their github account with repos that is not helping them, quite the opposite in fact.
- johnisgood 7y agoSo? If their code is of low quality, they can be filtered out based on that by the not-so-potential employer. Employers do not have to hire you, and not everyone knows how to write "good" code. If you cannot write code "properly", it will show one way or another. If you can, that is good, that will show, too!
- hinkley 7y agoI know a couple of recent graduates I've encouraged to volunteer. It would have been far better for them to get internships or work writing software on campus but that boat has sailed. Hopefully they can get references out of it, some contacts, and that first 100 hours of professional coding experience. If not a job, at least the tools to get one. OSS is a little rough for newbies because it can be pretty open ended, and having vague requirements can get us all in trouble, but it worse for people who don't have any coping mechanisms for ambiguity. Being able to close bug reports is an extremely necessary skill. Necessary, but insufficient. There are other options like https://en.wikipedia.org/wiki/Code_for_America https://en.wikipedia.org/wiki/Code_for_America that should feel more like project work. Have you done much volunteer work, and for long? I've been working off and on with such groups since I was 16, and in some ways the stories don't change for the successful ones (Anna Karenina again, perhaps?). Volunteer-based organizations tend to end up with a small number of historians, regulars who show up and help glue the whole thing together. You get a few people who contribute intensely for a couple of years and then burn out because they aren't pacing themselves. Then you get an army of wide-eyed energetic people who will move onto something else quickly. This is a very, very fat 'long tail' and as an organizer you have to get useful and durable work out of these people whenever you can. The names and faces keep changing on you. To do that you have to direct them, steer them into a project that is already thought up or exists but for whom not enough people are participating. Preferably something with some good optics so they feel seen (and so your organization is seen). Because if they show up and you let them work on whatever, you get pulled in a million directions. There's no cohesiveness, no coherent story, and without those you lose your narrative, you can't recruit more people, you can't hold onto those 'intense' people who do a ton of the big work, and you disappear. I don't know if volunteerism requires all three of these types, but it certainly gets them, and they all fill an important niche. Most of the people who are going to read your message fall into the short-timers section, and we need those although we sure would like to turn you into one of the other two groups.