Trunk Based Development – Optimizing for Team Performance
summary
Company experience over two years plus the Google State of DevOps study (7 years, 32,000 pros) links trunk‑based development to elite performance: frequent mainline commits, CI pipelines and pre‑commit checks. Concrete techniques are pair programming, test-driven development and continuous integration. Reported impacts: pair work adds ~15% time but cuts defects by ~15%, IBM sees ~40% fewer defects with TDD and Microsoft 60–90% fewer; an e‑commerce price feature is split into front end, calculation class and DB query and shipped incrementally to main, enabling parallel work, fewer context switches and faster, more confident deployments.
AI-written summary · about
chapters (8)
- 0:00The industry standard
- 1:53Issues with isolation
- 4:41Trunk-based development
- 9:10Performance and pairing
- 12:48Benefits of TDD
- 15:05Implementing the change
- 20:36Overcoming resistance
- 24:23Personal and team impact
related talks
51mFrom the Trenches - Remote Scaled Trunk-Based Development
47mTrunk-Based Development in the Enterprise
45mContinuous Integration: That’s Not What They Meant
56mContinuous Integration: That’s Not What They Meant
11mTDD - Trust Driven Development
35mFeature Toggles, Trunk-Based Development and Continuous Delivery
23mMoving Fast with XP
01h 01m"Doing Devops" as a politically powerless developer