11 Articles
Palatable sized content to supercharge your life
Part 1 of 8: Understanding what makes software valuable and how to protect that value through good design
Part 2 of 8: Every dependency has two properties that determine whether it helps or harms your code
Part 2 of 8: A model for thinking about dependencies — explicit vs implicit, fixed vs flexible, and why one combination is impossible
Part 3 of 8: SOLID is not arbitrary — each principle addresses a specific aspect of placing dependencies well
Part 3 of 8: How SOLID principles follow directly from the goal of locality and good dependency placement
Part 4 of 8: Immutability, purity, total functions, and railway-oriented error handling — patterns that make code easier to reason about
Part 5 of 8: Modeling the business domain with Records, Principals, and Aggregate Roots — pure, testable, and free of infrastructure
Part 6 of 8: Wrapping a pure domain in controller and repository layers, with mappers at every boundary
Part 7 of 8: The composition root as the big bang — constructing every service once into a frozen, immutable tree
Part 8 of 8: How the architecture makes testing straightforward — and why testability is the proof the design works
Try adjusting your search or filter