/explore
|
You are here 
|
www.milanjovanovic.tech | ||
| | | | |
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. Generally, the model represents a subset of our domain at an appropriate abstraction level to be able to solve problems related to that domain. |
|
| | | | | ||
| | | | |
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.martinig.ch
Immature software developers, test coverage, software architecture decisions, product increment, Java interview, retrospectives tools and test data generators. |
|
| | | | | ||
| | | | |
venam.net
We're used, as software engineers to try to make things perfect, to see things from above, to think we're great architects and creators. What's more important though is to create software that does an important job for someone. What are the best ways to create such software? |
|
| | | |||
