Domain-specific languages with PHP
summary
Argues for building internal DSLs on top of an existing language (PHP shown), rejects external languages and language-forging overhead, demonstrates using DDD building blocks (entities, value objects, aggregates, a service like an invoice number generator), shows tests as executable specs and cites testDocs for readable test names, warns against one big model, recommends many small models and keeping infrastructure out of domain code so the approach actually stays maintainable.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:12Domain-Specific Languages
- 2:25Domain-Specific Language?
- 12:20Should a computer program be...
- 14:33Problem: Terminology
- 16:57Glossary vs. Code
- 18:51Requirements Documentation
- 19:54Program/Documentation Gap
- 20:43Behaviour-Driven Development (BDD)
- 22:24Tests as executable specification
- 23:47DDD patterns as building blocks
- 26:16Ubiquitous language
- 27:33Nouns and Verbs
- 29:19Summary
related talks
38mIntroDDDuction
27mConfessions of a Backend Developer
54mHexagonal Architecture in DDD
37mMultilingualism makes better programmers - beyond PHP and JavaScript
39mSimply About the Complex — Domain Driven Design
58mObjects, Testing and Responsibility
34mLevel up with a Microservices architecture
40mBarely Enough Design