Building a Culture of Quality
summary
Claims that code quality is measurable and actionable through metrics lead to concrete practices: a SaaS called Code Climate rates classes A–F and shows a 3.2 score for its own repo; early‑warning systems use build failures, static analysis and tools like break man, fog and fle to flag security or complexity regressions; process changes include non‑blocking pull requests, the Boy Scout Rule (leave code cleaner), and team factoring group refactor sessions. These tools and rules detect problems early and stop adding new “slop.”
AI-written summary · about
chapters (15)
- 0:00Building a Culture of Code Quality
- 2:57Presenting Problem
- 4:48Vicious Cycle
- 6:18Opposing Forces
- 10:38Fixing Any Problem
- 10:53Qualitative Data
- 11:54Quantitative Data
- 17:33Early Warning Systems
- 20:03Lunch and Learn
- 21:08Teamfactoring
- 23:45Language Error
- 24:21Painless Code Reviews
- 26:20Review Criteria
- 27:58Individual Resistance
- 29:30Virtuous Cycle
related talks
28mGet a grip on your quality by using Quality Views
50mPanel: Beyond The Vibe: Code Quality First
24mRoad to Zero Lint Failures: Tackling Code Quality Challenges at Scale
38mA Game of Testing
58mClean Code, SOLID, CQRS... And what about our tests?
43mTesting Software Architectures
47mFighting Software Entropy
45mConquering complexity: refactoring JavaScript projects