5 ms·
GitHub epitomizes a "culture of shipping" to me. They're slamming feature after feature out the door (multiple features in the same day sometimes - like today)
by troygoode 14y ago
GitHub epitomizes a "culture of shipping" to me. They're slamming feature after feature out the door (multiple features in the same day sometimes - like today). I like BitBucket too but, man, I would not want to be competing against the GitHub team right now. They're just prolific.
- leeoniya 14y agoi wish they would slam out a feature of a all-project-activity-feed and make it the primary home view of repos.
- d0m 14y agoI wish not!! When I get on a repository, I want to see the code. Although I don't mind if there is smaller area containing the feed.
- up_and_up 14y agoI agree. But I would also say they do have a rather largeish dev team: https://github.com/about/team https://github.com/about/team. Like 50-80 devs maybe? Thats like 12-20 teams of four people each. Plus they have some really productive people on their team, several people are/were core contribs to Rails. I guess one would expect with that many high quality people that a decent amount of work would be getting done.
- kneath 14y agoOur team makeup is almost entirely "devs" (I call them Engineers — people who design, build, and ship software). A lot closer to 120 than 80. However your estimates a pretty far off in terms of people who work on dotcom — that number is much closer to 15. One of the more interesting sociological problems of software to me is this idea that more people equals faster movement. The only studies in this field prove the opposite, yet common opinion is simply that: more people equals more output. We've actually spent a great deal of effort not growing our team lately, much of which has directly contributed to an increase in pace. I would credit our pace far more to the organizational structures we've created within our company (ex: http://tomayko.com/writings/adopt-an-open-source-process-constraints http://tomayko.com/writings/adopt-an-open-source-process-con...) than the size of our team.
- arikfr 14y agoWhat the other engineers work on? (Besides the enterprise version)
- bkbleikamp 14y agoA few of the other projects that people are working on: GitHub for Mac, GitHub for Windows, libgit2, internal tools, ops, Gist, Git
- mbesto 14y agoI'll just leave this right here: http://www.amazon.com/Peopleware-Productive-Projects-Second-Edition/dp/0932633439/ref=sr_1_1?ie=UTF8&qid=1359107252&sr=8-1&keywords=peopleware http://www.amazon.com/Peopleware-Productive-Projects-Second-...
- swah 14y agoJust picked this one from the library. Around here, few people know it (Brazil).
- miles_matthias 14y agoGranted they have a highly technical product, but it's also really cool to think that they have loads of devs, and not a single manager. jealous
- miles_matthias 14y agoSo I love how github works. Love it. But I think they're able to work like that because they are a highly technical, product oriented company. (see http://zachholman.com/posts/how-github-works-hours/ http://zachholman.com/posts/how-github-works-hours/) I've always wondered, how can companies that do client work adopt those principles? Is it even possible?
- ipmb 14y agoOur work is still primarily client based at Lincoln Loop and we share many of the same principles that GitHub does. Keeping track of billable hours is how we get paid, but our people get to choose when, where, and how many hours they will bill. We've written a little about it here: http://lincolnloop.com/blog/categories/business/ http://lincolnloop.com/blog/categories/business/
- miles_matthias 14y agoWow that's really cool. Thanks for sharing that. I'll be reading all of it :)
- meh01 14y agoThere are features that are worth shipping, and there are "look at me" features. This the latter.