Scott Chacon on working at GitHub
thegeektalk.com
thegeektalk.com
---
This reminded me a lot of Steve Yegge's "Good Agile, Bad Agile" ( http://steve-yegge.blogspot.com/2006/09/good-agile-bad-agile...):
"- Google has a philosophy of not ever telling developers what to work on, and they take it pretty seriously.
- developers are strongly encouraged to spend 20% of their time... working on whatever they want, as long as it's not their main project.
- there aren't very many meetings. I'd say an average developer attends perhaps 3 meetings a week, including their 1:1 with their lead.
- there aren't Gantt charts or date-task-owner spreadsheets or any other visible project-management artifacts in evidence, not that I've ever seen."
I don't see how "work on whatever you want" can get the maintenance jobs done when everyone would rather be writing new code than maintaining old stuff.
Unfortunately, this will likely never be some of the things that bug their customers the most -- such as the wiki that's been wrong since before they launched.
A lot of really nice features can be found on github, and a lot of interesting technology has come out of github since I've started using it (which is a few days short of two years now).
The wikis remain pretty much trapped in time, though. I can easily imagine what an awesome github wiki would look like, but I also understand that migrating to it would be a huge pain.
In the meantime, I just can't use it. github pages is awesome and it's almost, but not quite a substitute. I wonder how much of the problem would go away with gh-pages as a mob branch...
What bugs you most likely bugs us ten times more. There isn't a feature on the site we don't use extensively.
I'm running Ubuntu on a 2nd gen Air. The big problem is getting it to boot. The -noapic kernel option helps. Also I have a little ritual where when turning it on I hit the power switch at the beginning grey screen then proceed to turn it on again.
Damien Katz on couchdb