Building a Culture of Quality
summary
Claims a practical path: assemble qualitative feedback (one‑on‑ones, retrospectives, anonymous surveys) and quantitative metrics (velocity, cycle time, defect rates, static analysis from tools like flog, Flay, Reek, Code Climate), stop introducing new slop and apply the Boy Scout rule to clean one thing per touch, run team‑factoring sessions (group refactors), use GitHub pull requests and CI/build‑failure alerts into HipChat for early warning, treat legacy code as anything older than two weeks and iterate with fixed experiments.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:40Building a Culture of Code Quality
- 2:02Presenting Problems
- 4:29Pressure Can Lead to Sloppy Coding Practices
- 6:43Why Does Poor Quality Code Get Introduced
- 7:44Complex Code
- 8:11Legacy Code
- 12:17Quantitative Data
- 13:09Software Metrics
- 14:11What Do You Do When You Find Yourself in a Hole
- 15:01The Boy Scout Rule
- 16:18Conflicting Style Preferences
- 19:43Team Factoring
- 22:13Build Failures
- 23:35White Boarding
- 24:08Code Reviews
- 25:19Github Pull Requests
- 25:39Synchronous Code Review
