Model Driven Software: Putting the Cart Before the Egg
summary
Argues that building a domain-specific language of customer nouns and verbs lets users read and validate requirements in pseudocode, then transforms that DSL into a visual representation (simpler than UML but drillable) and runs a code generator to produce C#, Python or other target languages. Requires an initial framework tied to the domain built on existing libraries; once language and generators are debugged the pipeline reliably produces working application code and customers call it magic.
AI-written summary · about
related talks
38mWhat I talk about when I talk about Domain Driven design
10mSpecification-driven development and model-driven architecture with AI
44mStrategic Domain-Driven Design for dummies
01mSoftware doesn't tolerate ambiguity
01mPlatform Engineering is Domain Driven Design
42mDomain Driven Design - So Your Code Speaks Plain Language
47mThe linguist programmer
01h 00mFrom Domain Driven Design DDD to Delivery