Explore >> Select a destination
|
You are here 
|
venam.net | ||
| | | | |
herbertograca.com
|
|
| | | | | Domain-Driven Design was coined by Eric Evans in his fantastic bookDomain-Driven Design: Tackling Complexity in the Heart of Software, published in 2003. Eric Evans book was key in formalisingmany of the software development concepts that today we take for granted. | |
| | | | |
blog.gougousis.net
|
|
| | | | | [AI summary] The text provides an in-depth exploration of Domain-Driven Design (DDD) concepts, including its purpose, key principles, and practical applications. It discusses the importance of understanding the business domain, the role of domain experts, and the use of models to represent complex systems. The text also covers various DDD tactical patterns such as domain events, aggregates, and the importance of maintaining domain invariants. It highlights the challenges and considerations in implementing DDD, including the need to balance technical design with business requirements, and the value of techniques like Event Storming for information gathering and modeling. The text references several notable speakers and resources, including Stefan Tilkov, Dere... | |
| | | | |
www.paepper.com
|
|
| | | | | Domain Driven Design (DDD) is an influential book by Eric Evans from 2004 - sometimes also referred to as "the big blue book". This blog post summarizes some of my own understanding of the book and gives you an introduction to domain driven design. Important definitions Domain The domain is the area in the real world which we are writing a computer program about. Model The model is our representation of our domain. | |
| | | | |
gist.github.com
|
|
| | | Generic `printf` implementation in Idris2. GitHub Gist: instantly share code, notes, and snippets. | ||
