Building a Culture of Code Quality
summary
Argues for measurable, concrete steps: gather data (retrospectives, anonymous surveys, lead time/cycle time/velocity and code metrics), install early‑warning systems (CI alerts, chat notifications, static analysis with Code Climate and Breakman), adopt stop introducing new problems and the Boy Scout rule, practice team refactorings and lightweight pull‑request reviews (non‑blocking, asynchronous), and tune processes based on what the metrics show so crappy code gets fixed immediately instead of lasting forever.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:19Presenting Problems
- 1:42Developers Write the Worst Code When They Are under Pressure
- 2:14Why Does Code Quality Have this Vicious Cycle
- 4:59Gathering Data
- 5:37Software Metrics
- 6:25The Boy Scout Rule
- 7:48Team Factoring
- 9:29Early Warning Systems
- 9:56Detect Likely Bugs and Quality Issues
- 11:49Github Pull Requests
- 15:03Comprehension
- 16:59Quality Leads Developers To Be More Satisfied
related talks
33mBuilding Code Quality
43mBuild in Quality
11mTake back control of code quality
28mSome small steps for code, One giant leap for quality
25mBest Practices for Writing Clean and Maintainable Codes
59mTechniques for writing high-quality code
35mThe Code Quality Advantage How Empirical Data Shatters the Speed vs Quality Myth
29mCreating a Code Review Culture