GeistHaus
log in · sign up

Contributing to Open Source projects

brad.livejournal.com

Prior to joining Google I always joked that Google was the black hole that swallowed up open source programmers. I'd see awesome, productive hackers join Google and then hear little to nothing from them afterwards. When I joined I decided I'd solve this mystery and post about it but it's been over…

2 pages link to this URL
Dev Tools at Work

I was reading this old post from Brad Fitzpatrick, talking about why he thought open source contributors suddenly disappear after joining Google: They’re busy. Google seems to suck everybody’s free time, and then some. It’s not that Google is forcing them to work all the time, but they are anyway because there are so many cool things that can be done. I often joke that I have seven 20% projects. The Google development environment is so nice. The source control, build system, code review tools, debuggers, profilers, submit queues, continuous builds, test bots, documentation, and all associated machinery and processes are incredibly well done. It’s very easy to hack on anything, anywhere and submit patches to anybody, and notably: to find who or what list to submit patches to. Generally submitting a patch is the best way to even start a discussion about a feature, showing that you’re serious, even if your patch is wrong. https://brad.livejournal.com/2409049.html

0 inbound links article en blog
Paralyzed

If you follow the Jekyll community, you might have noticed that I haven’t been as active in the last year or two. Part of this is due to life events usurping my free time, and part of this is something else entirely: paralysis. I want to discuss today the paralysis.

0 inbound links article en