Code First, Ask Questions Later
summary
Claim: run a company like an open source project with no managers no vacation days and identical pay for full‑time staff. Tools: GitHub pull requests as living code reviews, Campfire for searchable async conversation, hubot wired to Jenkins, knife and puppet to auto‑provision and to trigger deploys. Outcome: feature‑branch CI auto‑configures, Master stays deployable, zero‑downtime releases happen and fixes land in ~20 minutes; engineers deploy 20 30 40 times a day and hubot controls builds and office gadgets.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:56Redefining code as building
- 2:39Taking ownership at GitHub
- 4:01Running GitHub as open source
- 5:48Iterating quickly with code first
- 6:51Autonomy mastery and purpose
- 7:54Why async communication matters
- 9:19Power of pull requests
- 11:44Hubot and automated workflows
- 14:17Deploying 30 times a day
- 16:42Culture of shipping
- 17:45Why questions after building
- 18:25William Herschel and building
- 21:14Q&A
