Tag

Software-Design

13 Thoughts filed under this subject.

  1. A Design Is Good for a Change, Not in Isolation
  1. Entity, Value Object, Aggregate, Model, DTO: Name the Role
  1. A Constructor Should Leave a Usable Object
  2. A Null Object Should Mean Nothing Happened
  3. The Law of Demeter Is About Knowledge, Not Dots
  4. Tell, Don't Ask Means Keep the Decision with the State
  5. Strategy Chooses How; Command Records What to Do
  6. Composition Over Inheritance Is a Decision, Not a Rule
  7. Dependency Inversion Lets Policy Own the Boundary
  8. Interfaces Belong to Their Clients
  9. Substitution Is a Behavioral Contract
  10. Open–Closed Protects Stable Policy from Repeated Variation
  11. Single Responsibility Is About Change, Not Class Size