Explore >> Select a destination
|
You are here 
|
nickhayden.com | ||
| | | | |
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... | |
| | | | |
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? | |
| | | | |
everythingfunctional.wordpress.com
|
|
| | | The answer to the question of whether we should write automated test suites has largely been settled. We absolutely should write unit tests, and possibly even integration and end-to-end tests. But as acceptance of this practice grew, and adoption became more widespread, a follow-up question arose; How many tests should we write? How do we... | ||
