Breaking Dependencies: The Path to High-Quality Software
summary
Claim: software quality means easy to change, extend, test, and that hidden dependencies are the core problem. Evidence: counted ~47 conference talks with ~8% of talks on design; examples show real tools and patterns that work or fail — std::pmr monotonic_buffer_resource demonstrates configurable global allocation, make_unique vs Factory method clarifies customization, and a service locator / persistence interface pattern replaces a raw Singleton. One book takes 1.5 years to write; examples compile and run.
AI-written summary · about
chapters (12)
- 0:00Breaking dependencies intro
- 1:45Dependencies core problem
- 5:20Degrading project story
- 10:15Design over features
- 16:14Patterns for dependencies
- 21:19Factory method revisited
- 30:54Patterns beyond OOP
- 41:54Patterns more complex than they seem
- 51:04Singleton pattern problems
- 1:06:22Fixing Singleton with inversion
- 1:19:48Singleton with service locator
- 1:23:16Summary: design essential
related talks
44mDependencies; Devil or Darling?
58mGetting a grip on your code dependencies
01h 03mBreaking Dependencies: The SOLID Principles
40mBuilding resilient frontend architecture
41mUsing Boundary-Driven Development to beat code complexity
01h 26mChaos Development: Removing Software as the Inhibitor of Agile
29mDecoupling in Practice - How Good Software Engineering Can Save...
51mDependencies: Can your agile teams handle them? and if not.. how