/explore
|
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.codeandunicorns.com
|
|
| | | | | Recently I was diving deep into Antipatterns and found them terribly interesting. Here is a list of quite many different sourced possible antipatterns and their wag abound descriptions. Big ball of mud: Simple way of saying it: An apocalypticmess. | |
| | | | |
initialcommit.com
|
|
| | | | | When talking about process in software development, the first word that comes into your mind is SDLC (Software Development Life Cycle). | |
| | | | |
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? | ||
