Explore >> Select a destination
|
You are here 
|
herbertograca.com | ||
| | | | |
vladikk.com
|
|
| | | | | Let's do a little experiment: try to explain the gist of Domain-Driven Design to someone who has no clue about it. This, especially doing it succinctly, is not easy. Heck, I struggle with it myself. Bounded contexts, entities, domain events, value objects, domains, aggregates, repositories... where do you even start? To find the order in the apparent chaos, I want to analyze the DDD methodology from a rather unusual perspective - by applying Domain-Driven Design to Domain-Driven Design itself. After all, this methodology is intended to deal with complex domains, isn't it? | |
| | | | |
www.milanjovanovic.tech
|
|
| | | | | If you were to glance at the folder structure of your system, could you tell what the system is about? Your architecture should communicate what problems it solves. This approach is called sreaming architecture. | |
| | | | |
www.codurance.com
|
|
| | | | | TDD is a software development workflow that involves code improvements in its life cycle. Understanding the design guidelines available will make it easier | |
| | | | |
128bit.io
|
|
| | | So for my posting forProject Euler 001, the Javascript code kind of upset me. It's not nice to look at and doesn't really solve the problem in a functional way. WithJavascript being afunctional programminglanguage it didn't sit well with me. Comparing the Javascript code to the Groovy and Ruby code there is one thing missing and it is the 'Range' type call. If I could have a call like that I could use some other calls like filter and reduce to get the same outcome. | ||
