Accessibility of codebases: Leader’s perspective
summary
Claim: making a codebase approachable cuts incidents, shortens onboarding, and raises velocity by shrinking unknowns and knowledge silos. Specifics: measure and track cyclomatic complexity and hotspot analysis over time, surface low bus‑factor components, and visualize change heatmaps. Practical fixes: enforce style and policy in CI with automated enforcement, standardize abstractions once and apply them consistently, run office hours and post‑incident reviews as embedded knowledge transfer, and treat documentation as living, prominently linked onboarding material.
AI-written summary · about
chapters (7)
- 0:00Accessible codebases intro
- 1:05Why accessible codebases matter
- 3:16Defining accessible codebases
- 5:01Building platform abstractions
- 6:27Knowledge sharing beyond docs
- 8:14Improving code health & learning
- 9:19Fostering open learning
related talks
33mBuilding Code Quality
18mBuilding a Culture of Code Quality
54mReadable Code: The Secret to Clean, Productive Software
34mDeep End Diving: Getting Up to Speed on New Codebases
49mTreat Your Code as a Crime Scene
39m7 Secrets of Maintainable Codebases
01h 01mDoes Your Codebase Spark Joy?
28mSome small steps for code, One giant leap for quality