/explore
|
You are here 
|
herbertograca.com | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
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? |
|
| | | | | ||
| | | | |
nickhayden.com
I started a new role in October that has a strong focus on event sourcing and domain driven design (DDD). One of the recommended books in our on-boarding materials is Domain-Driven Design Distilled... |
|
| | | | | ||
| | | | |
www.softdevtube.com
Computers are orders of magnitude faster than when most of us started programming and yet a lot of software runs much slower than it should. Nobody likes progress bars. Slow code provides for a horrible user experience, drains batteries faster, and increases our cloud bill. This session explores some of the reasons why software is |
|
| | | |||
