/explore
|
You are here 
|
qnoid.com | ||
| | | | |
ostash.dev
Like many of developers that were coding for the last few years, I was following mostly object oriented programming paradigm. Let's not go into details on its specific implementation (hopefully the reader is familiar with it. |
|
| | | | | ||
| | | | |
thejavaguy.org
Blog about software development |
|
| | | | | ||
| | | | |
islandinthenet.com
Island in the Net is been written and produced by Khürt Williams since 2005. Expect to find writing on technology, photography, nature, and cybersecurity insights with a reflective, journal-style storytelling. |
|
| | | | | ||
| | | | |
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? |
|
| | | |||
