3 ms·

> From a purely practical perspective, being a developer who exclusively works on closed-source code in 2014 is a bad career decision. You mean 99% of develope

• Touche 12y ago
  Most companies don't have you work on open-source as your primary job, but plenty allow you to do so as it affects your primary job. And plenty allow you to work on open-source in your down time. If you have a job that's exclusively closed-source and with no down time there's a good chance that's a bad job. You have to think about your own career. Unless it's a prestigious position that will make you attractive to other employers, you have to consider that being isolated from the larger software community puts you at a disadvantage in the market.
  • skizm 12y ago
    > If you have a job that's exclusively closed-source and with no down time there's a good chance that's a bad job. I guess that's where I disagree. I don't know how you can tie "ability to work on open source at work" to how good a job is. What does one have to do with the other? Also, "down time" is just another way of saying "free time". If I have free time, I won't be in the office. Which brings me back to, I don't want to work at a company that only wants people who work on open source in their free time. I really think the amount of open-source you work on has nothing to do with how good of a programmer you are or your work ethic. Which is why, for me, asking for a github profile is a red-flag when applying to jobs.