Why you’re getting understandability wrong
summary
Claim: most companies ignore understandability even though 68% of organizations report flying blind or flying slow. Defines understandability as having source, config, runtime, dependencies and inputs well documented and judged by being complete concise clear and organized. Recommends five fixes: minimize complexity, capture and share knowledge, maintain faithful dev environments, add logging/tracing metrics, and use next‑gen debuggers like Rookout live debugger for non‑breaking breakpoints in Kubernetes/serverless/production.
AI-written summary · about
chapters (8)
- 0:00Software understandability
- 2:24Understandability vs complexity
- 7:55Minimizing complexity
- 10:00System knowledge sharing
- 11:21Development environments for clarity
- 13:07Observability tools
- 13:47Debugging tools
- 15:12Conclusion and key takeaways
related talks
10mAccessibility of codebases: Leader’s perspective
54mReadable Code: The Secret to Clean, Productive Software
31mObservability for Developers: How to Get There
57mComprehending hard-to-understand software
43mQuit Simplifying!
46mTechnically Speaking: Improve your code with documentation
30mLow-Context DevOps: Helping DevOps find answers faster
23mBeyond the Buzz Building Developer Platforms That Drive Business Success