Boost Your Time to Market by Dancing the Limbo
summary
Argues that using a single branch workflow plus small, atomic commits cuts cycle time from months to minutes, demonstrates a Jest plugin (called limbo/TCR) and WebStorm integration that either auto-commits passing tests or reverts failing work, and shows a practical habit change born from a 4-hour refactor reverted at 3am: enforce timebox TDD (typical timers 1–5 minutes or 30 minutes) so every push is releasable and refactors proceed incrementally without merge spaghetti.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 6:02Branches are the problem
- 7:09Single branch advantages
- 8:35Limbo concept explained
- 12:54Demo time box TDD
- 23:52Demo TCR approach
- 30:39Try limbo yourself
- 31:01Prerequisites and tips
- 32:44About our company
- 33:06Q&A and closing
related talks
45mContinuous Integration: That’s Not What They Meant
35mIncrease Agility and Quality Using Trunk-Based Development in Continuou...
10mBeyond “try harder”: Effective strategies to tackle bugs
35mSmarten Up Your Pipeline and Reduce Test Execution Time｜
56mContinuous Integration: That’s Not What They Meant
42mSpeeding Up Innovation
41mContinuous Integration Tips & Tricks
57mBlazing Fast Feedback Loops in the Java Universe