Article · 12 min read

The safety of speed: How we ship code 180 times per day

Danny Fallon and Ryan Sherlock, Intercom · Intercom Blog Free Advanced

The mechanics behind a high shipping cadence: small batches, feature flags, fast pipelines, and the safeguards that let a growing team deploy constantly without breaking things. This is the how that makes the heartbeat essay real. Useful once your team is asking what infrastructure and habits a fast cadence actually requires.

  • Small batches minimize the risk of any single deploy.
  • Feature flags let you ship code continuously and release it separately.
  • Speed and safety compound together when the pipeline is built for it.
Open on intercom.com ↗

The question it answers

  1. How do product teams keep a consistent shipping rhythm as they grow?

Read with it

  1. Video · ~13 min How to Plan an MVP Michael Seibel (YC)
  2. Basecamp's battle-tested, opinionated system for shipping meaningful work in fixed cycles without endless backlogs, a primary... Basecamp / 37signals Book · free online book Shape Up: Stop Running in Circles and Ship Work that Matters Ryan Singer
  3. The essay that explains why one badly-placed meeting can destroy a founder's entire day of building, and what to do about it.... paulgraham.com Article · short Maker's Schedule, Manager's Schedule Paul Graham
  4. This is the operating manual behind the answer's core rule: don't run a remote team on vibes. GitLab runs 1,600+ people across... The GitLab Handbook Article · 25 min read Asynchronous communication for remote work GitLab
  5. Zerodha, India's largest broker, built almost everything in house with a famously small team, and its CTO explains why owning... Software at Scale Podcast · 1 hr Building Zerodha with Kailash Nadh Utsav Shah
  6. Linear is a small, largely distributed team that ships a famously polished product, and this breaks down how they organize... Lenny's Newsletter Article · ~20 min read How Linear builds product Lenny Rachitsky
eChai Partner Brands The partnership →