Why Bad Code Quality Is Not (Only) Your Fault
summary
A business-logic cleanup uncovers duplicated start/stop rules in a delivery-tracking system so that identical location updates are often sent twice; consolidating nearly identical classes and removing obsolete rules cuts event volume and bug surface while making the rule set easier to read and change. Recommended practices include sketches and diagrams, explicit decision notes in code or an onboarding entry page, plus automated checks and reviews to prevent regressions. redundant business rules pair programming static analysis decision logs
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 7:33Complex business logic impact
- 10:48Miscommunication and misunderstandings
- 17:38Diagrams and documentation
- 26:18Knowledge silos and sharing
- 34:09Domain complexity and simplification
- 35:59Developer responsibility and conclusion
- 37:45Q&A session
related talks
42mWhy Bad Code Quality Is Not (Only) Your Fault
25mBest Practices for Writing Clean and Maintainable Codes
33mBuilding Code Quality
58mIncoherent Code: How Code Quality Impacts Security
51mReasons and Ways to Improve Code Quality
43mClean code, is it really worth it? A story about monsters and...
43mClean Code: Be The Hero
18mWriting Quality Code