Why Bad Code Quality Is Not (Only) Your Fault
summary
Code quality is a shared responsibility: a logistics app accumulates redundant event logic that duplicates updates for leaving and stopping, sending unnecessary messages; consolidation replaces two nearly identical rules with a consolidated rule and drops obsolete updates so the system emits four events instead of many, which reduces bugs. Practical fixes shown include using diagrams, pair programming, decision logs and improved documentation to keep behavior aligned with business rules.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:27Blaming individuals
- 2:09Code quality example
- 9:44Code quality factors
- 11:15Stakeholder miscommunication
- 16:03Developer misunderstandings
- 18:15Diagrams reduce misunderstandings
- 20:43Big picture importance
- 23:59Accessible diagrams
- 25:23Documenting knowledge
- 29:18Breaking silos
- 30:21Pair programming
- 32:04Documentation role
- 35:18Simplifying complexity
- 36:45Domain-driven design
- 39:38Developer responsibilities
- 40:00Shared responsibility
- 41:26Q&A
related talks
47mWhy Bad Code Quality Is Not (Only) Your Fault
51mReasons and Ways to Improve Code Quality
58mIncoherent Code: How Code Quality Impacts Security
25mBest Practices for Writing Clean and Maintainable Codes
33mBuilding Code Quality
26mFacing the "Quality" Problem in Long-Lived Codebases
18mWriting Quality Code
43mClean Code: Be The Hero