4 ms·
I love Github, but I certainly must agree with point number 1. I work as a CTO at a start-up here in SF full-time (which means, 8am-2am). We have to a lot of de
by lowglow 15y ago
I love Github, but I certainly must agree with point number 1. I work as a CTO at a start-up here in SF full-time (which means, 8am-2am). We have to a lot of developers and designers around the world which means when I'm not coding, chances are I'm managing. This leaves me very little time to contribute to my own personal projects, much less open source projects.
I'd say that using Github as a resume is a great idea for Jr. Developers and students looking to get some "cred" in the real world. But that really just refers back to knowing your industry and being professional about your work.
- dblock 15y agoEveryone missed the part where I found myself contributing to several open-source projects, naturally. Here's an example: we use this gem called "analytical". Its configuration didn't support test vs. dev vs. production. I could have hacked on top of it - it would have added some gross code to my project. Instead I changed the original - turned out to be less code overall and didn't pollute anything in my work project. My pull request (https://github.com/jkrall/analytical/pull/17 https://github.com/jkrall/analytical/pull/17) still hasn't been accepted, but we use the fork. I just think that the reason you're not contributing to OS is not time, it's that you choose to design within the box.
- rreeves 15y agoInteresting considering he works from 8am-2am. How on earth do you come to the conclusion he's not contributing to OS because he chooses to design within the box?