Getting a grip on your code dependencies
summary
Argues that coupling, not vague patterns, breaks changes and gives concrete fixes: use tools like Project Dependency Viewer, JetBrains Rider and AI to find weird dependencies and even uncover a bad asymmetric encryption copy; run SQL Server in Docker/testcontainers for fast characterization tests; favor the Dependency Inversion Principle and vertical functional slices with local DI containers; make everything internal so unused code is deletable; intentionally duplicate inside boundaries to reduce cross-cutting coupling.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:27Abstractions and dogma
- 6:08Internal code boundaries
- 12:27Dependency inversion
- 18:26Vertical slice architecture
- 24:07Package dependencies
- 29:49Code visibility
- 34:48Tell-Don't-Ask principle
- 39:08Dependency injection
- 41:13Legacy code approach
- 49:18Code seams refactoring
- 53:29Monolith to microservices
- 54:11Q&A
related talks
44mDependencies; Devil or Darling?
41mUsing Boundary-Driven Development to beat code complexity
59mTechniques for writing high-quality code
58mDespagghetifying code with NDepend
40mBuilding resilient frontend architecture
53mTools and practices to help you deal with legacy code
42mSponsored Session: Dependencies: Do's and Don'ts
32mKeeping your code strong