Explore >> Select a destination
|
You are here 
|
talesfrom.dev | ||
| | | | |
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. | |
| | | | |
friendgineers.rosenshein.org
|
|
| | | | | Leon's musings on software development | |
| | | | |
venam.net
|
|
| | | | | In a previous post, I've underlined the philosophy behind Domain Driven Design, DDD, and now I'd like to move to a practical approach that handles real issues in software development and architecture, requirements that constantly change, and models that are never precise, never current, and/or never using the best technology available.... | |
| | | | |
jonathan-frere.com
|
|
| | | This review is largely in response to the article "It's probably time to stop recommending Clean Code", and the ensuing Reddit discussion. A lot of really interesting points were brought up, but the big question that the author themself wasn't able to answer was: "What should we recommend instead?" I believe the book we should be recommending is A Philosophy of Software Design by John Ousterhout. In this post I want to spend a bit of time reviewing it and giving an overview of the contents, and then I want to explain why, in my opinion, it is such a good recommendation. | ||
