Software doesn't tolerate ambiguity
summary
Claim: software doesn't tolerate ambiguity and Domain-Driven Design techniques are the way to make messy human communication executable. Shows how turning tangled requirements into ubiquitous language and concrete bounded contexts yields models that compile into tests and code, describes the meta-experience of collaborating on the talk as a case study, and demonstrates when the conversion fails versus when the resulting code actually runs as intended.
AI-written summary · about
related talks
44mStrategic Domain-Driven Design for dummies
38mWhat I talk about when I talk about Domain Driven design
16mDDD is not enough: the future of software development -
59mDomain-Driven Design - Where Rubber Meets the Road
35mTrivialization of DDD or Not?
31mIs Domain-Driven Design Overrated?
42mDomain Driven Design - So Your Code Speaks Plain Language
05mModel Driven Software: Putting the Cart Before the Egg