Continuous Integration: That’s Not What They Meant
summary
Jez Humble's CI test (commit to main daily, every commit triggers build+tests, fix failures within 10 minutes) becomes the yardstick and trunk-based development is presented as the practical way to meet it. Teams switch from slow feature-branch + PR workflows to continuous trunk-based development, adopt many more much smaller steps (MMSS), pair/mob programming, TDD, automated incremental testing (run only affected tests), frequent refactoring, and minimized dependencies to reduce merge hell, speed feedback, and enable safer, faster deployments.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:14Jez Humble's continuous integration test
- 3:24CI vs CD
- 4:26TBD = CI
- 5:30TBD: Better, faster, happier
- 7:16Storytime
- 15:03Dan Able quote
- 15:35Kief Morris quote
- 16:55Dragan Stepanović quote
- 18:49Dave Farley quote
- 22:06Review code base at regular intervals
- 26:50Get help
- 28:58Ensemble programming
- 31:35Minimize dependencies
- 35:30Trisha Gee quote
- 36:35CTBD (Continuous trunk-based dev.)
- 37:15Conclusions
- 38:31Summary
- 39:13Feature flags
- 43:17Outro
related talks
56mContinuous Integration: That’s Not What They Meant
46mContinuous integration - that's not what they meant
31mContinuous Integration 101 for Devs
34mContinuous Integration: A Bittersweet Love Story
01h 15mThe Practices That Make Continuous Integration
32mBuilding Confidence Together: Continuous Integration & Testing
11mCreate unfair competitive advantage w/CI/CD Pipelines
25mProgramming to the extreme