The Anatomy of Business Conditions
summary
Argues that many brittle systems come from feature-driven aggregates and scattered if statements, and shows concrete refactor steps using DDD, event sourcing and policies to centralize business rules in the application layer and inject tunable strategies into aggregates. Demonstrates renaming and generalizing events (percentage discount → generic discount) to remove dozens of conditional handlers, replaces ad hoc event handlers with discount policies and process managers, and claims this yields smaller domain models, fewer regressions and much easier removability of features.
AI-written summary · about
chapters (10)
- 0:00The problem with if statements
- 3:27Analyzing feature-driven code
- 7:07Lessons from client projects
- 14:42Anatomy of business conditions
- 18:58Structuring application layers
- 25:14Tuning domain logic with policies
- 30:24Process logic and workflows
- 36:14Refactoring for cleaner design
- 42:08Redefining code quality
- 45:51Conclusion and key takeaways
related talks
52mBreaking Bad Code: From simple problems to complicated solutions and back
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
01h 07mThe courage to business logic - Business Driven Architecture
50mMoving away from CRUD: DDD + CQRS
38m7 Years of DDD: Tackling Complexity
43mArchitecture antipatterns and how to beat them 1/2
36m"Business Logic in Ruby"
59mDomain-Driven Design - Where Rubber Meets the Road