Betterer Incremental improvement
summary
A compact walkthrough of a tool called better that turns migration goals into measurable fitness tests, serializes snapshots to a better results file, and refuses commits when a constraint check like smaller (fewer .js files) fails. Examples show writing a file test that produces per-file issues, using an update flag to force progress when necessary, and how merging, CI and automated counts let teams lock in incremental wins instead of long-lived branches or risky rewrites.
AI-written summary · about
chapters (6)
related talks
21mBetterer: Incremental Improvement
48mBetterer: Incremental Improvement
46mThe Surprising Effectiveness of Small Steps
32mMaking Sotware Better, Despite Having Users
40mTightening the Feedback Loop
35mQuickly and Safely Refactoring Legacy Code
34mBoost Your Time to Market by Dancing the Limbo
28mSome small steps for code, One giant leap for quality