Build in Quality
summary
Argues that small “broken windows” hacks become runaway technical debt and that enforcing quality in-process stops it: CI (BillKite) runs rubocop, eslint, unit and acceptance tests and fails builds on new issues, CodeClimate flags regressions and SimpleCov enforces a ~75% coverage floor. Notes a 56% NYC crime drop analogy and that developers spend ~70% reading code (and 30% copying), so catching smells early prevents proliferation. Teams schedule monthly developer days and gate merges on green builds, and those measures demonstrably reduce regressions and slow technical decay.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:57Breaking Windows
- 3:11Tech Death
- 4:42Legacy Code
- 6:54Enforcement
- 7:26Good Code
- 8:58Code Structure
- 10:08Antipatterns
- 14:49Coding Standards
- 17:30Interface
- 21:08Easy to Test
- 23:41RepoCop
- 24:49RepoCop Configuration
- 26:26ES lint Configuration
- 28:54Tests
- 30:28Code Climate
- 31:54Static analysis tools
- 33:27Visual Studio
- 34:48GitHub
- 35:43Pull Requests
- 36:24Code Reviews
- 37:58Large Changes
- 39:12Small Changes
- 40:41Refactoring
related talks
33mBuilding Code Quality
18mBuilding a Culture of Code Quality
28mSome small steps for code, One giant leap for quality
44mClean as You Code Your Projects
35mWhy Software Engineers Should Make Quality a Priority
59mTechniques for writing high-quality code
40mFixing Broken Windows
14mThinking of Quality as developer productivity tool