Real Developers Ship (a.k.a Tenets for Software Delivery)
summary
A small Envato team ships Microlancer from a blank terminal to production in two weeks by cobbling Heroku, Zendesk and third‑party services together, then evolving the codebase continuously. Key claims: move CI to continuous deployment with feature flags so new code is toggled and tested in production, never revert but always roll forward, import scrubbed DB backups into dev, run the full test suite fast (about 90 seconds), do small refactors immediately, and automate only when a manual workflow proves itself.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:30Sebastian von Conrad
- 2:10Marker Lancer
- 2:50New Product Idea
- 3:10Tired Timeline
- 3:55Real Developers Ship
- 5:25Fake it until you make it
- 6:30Building a foundation
- 7:35Cut the crap
- 9:55Continuous integration
- 14:30Feature fake gems
- 18:00Roll forward
- 18:50The bleeding edge
- 19:35Trust your test suite
- 21:55Pay your effector up front
- 26:05Yagna
- 26:20The 37signals
- 26:55Build half the product
- 28:15Do things that dont scale
- 29:45Time is value
- 30:40Questions
related talks
47mContinuous Delivery Warstories
25mProgramming to the extreme
30m10 Ways to Improve How You Ship Software
50mContinuously delivering software to big brands
46mContinuous Deployment Workflows
34mEnabling a Continuous Deployment Mindset
42mA Modern Development Culture for a Modern Development Process.
38mJust Ship It!