Easy peasy, it's the 3rd blue line above the purple line /s
https://github.com/takaakit/uml-diagram-for-ddd-example-in-e...
I can't believe someone took time to generate such a thing, as if it is useful to anyone
Easy peasy, it's the 3rd blue line above the purple line /s
https://github.com/takaakit/uml-diagram-for-ddd-example-in-e...
I can't believe someone took time to generate such a thing, as if it is useful to anyone
If it is this complicated for a demo project for the purposes of the book, in my opinion, it shows it’s completely inadequate for handling anything remotely real.
Project ongoing for five years, 10 devs on the team, each year two resigns and two joins, some good, some mediocre, can you imagine them mess this will be? And that’s not even a large project, it’s just an average but real project size.
KISS / YAGNI goes a long way.
Thanks for saying this. UML is beyond useless, almost nobody understands it, almost nobody does it right and almost nobody uses it when they need to (because it makes no sense to them).
I completely disagree. UML is one of the best tools to communicate system designs and behavior in a high-level language that is easy to understand. Like everything in software engineering, you can make things very hard to understand or you can focus on making things easy to understand, and if you do not take the time to familiarize yourself with the basics them everything sounds very complex and useless to you.