What's In A Model?
summary
Argues a concrete alternative to MVC: refactor a simple customer UI through an onion core domain with ports/adapters so all inputs pass core rules; demonstrates building a customer form, adding a validated domain Customer, extracting a phone number value object (with parsing and toString logic), mapping layers, and replacing a messy shared project with a core domain project; shows tests that validation turns the UI red and that the refactor removes duplication and brittle mapping.
AI-written summary · about
chapters (8)
- 0:00Start
- 17:03In software engineering, a domain model is a conceptual model of the domain that incorporates both behaviour and data
- 29:59Classes should serve a single purpose
- 30:18Extension methods may indicate the lack of a domain model
- 30:43Write idiomatic code in domain models
- 31:18Think about your namespace hierarchy
- 32:15Explore your domain with a domain expert
- 33:58TECHNICAL DEBT ISN'T TECHNICAL
related talks
31mWhat Comes After MVC
38mThe M and C in MVC
37mBuilt to last: A domain-driven approach to beautiful systems
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
21mForm Validation Done Right
35mBuild Complex Domains in Rails
50mDomain Prototyping or Design Is How It Works
27mBridging Business and Frontend: Domain-Driven Design in Modern Web Architecture.