Thoughts

Notes on design, code, and the details that make software feel considered.

  1. A Command Bus Must Pay for Its Indirection
  2. A Composition Root Makes Choices Visible
  3. A Hexagon Is Not a Directory Layout
  4. A Mock Fortress Tests a Call Script
  5. A Pull Request Is a Review Narrative, Not a Template
  6. A Queued Command Changes the Contract
  7. A Surviving Mutant Is a Question, Not a Score
  8. A Valid Command Can Still Be Refused
  9. An Interface Does Not Make a Fake Substitutable
  10. Choose the Test Boundary from the Defect
  11. Coverage Tells You What Ran, Not What Your Tests Would Catch
  12. From Commit to Changelog: An Intent-Aware Release Pipeline
  13. Intent Commits: Commit Types Are Not Release Decisions
  14. Unreleased Is Not a Junk Drawer
  15. EventStorming Finds Disagreement Before It Finds Services
  16. Shared Kernel or Published Language: Choose Where Coordination Lives
  17. A Process Manager Remembers What the Queue Cannot
  18. CQRS Starts When Reads Need a Different Model
  19. A Repository Is a Domain Collection, Not an ORM Wrapper
  20. Entity, Value Object, Aggregate, Model, DTO: Name the Role
  21. Strategy Chooses How; Command Records What to Do
  22. A Null Object Should Mean Nothing Happened
  23. Tell, Don't Ask Means Keep the Decision with the State
  24. The Law of Demeter Is About Knowledge, Not Dots
  25. Composition Over Inheritance Is a Decision, Not a Rule
  26. Dependency Inversion Lets Policy Own the Boundary
  27. Interfaces Belong to Their Clients
  28. Substitution Is a Behavioral Contract
  29. Open–Closed Protects Stable Policy from Repeated Variation
  30. Single Responsibility Is About Change, Not Class Size