I know it is more than three years old but if you are interested in Clean Architecture you should take your time and
watch it. Uncle Bob explains nicely - and a little bit funny as usual ;-) - what the Clean Architecture is about,
how the puzzle is built up and why it has to be like this.
And as a summary for this video and as an outlook to my next post here is the key message:
The post gives a nice introduction by first motivating clean architecture by looking at the
short comings of the traditional layered approach. It then gives some history about the Clean Architecture.
Finally the post briefly introduces the Clean Architecture itself - the circles and the dependency rule.
It was a nice read - looking forward to read the follow-ups.
I have created a YouTube video explaining in detail how I would setup a project following
the Clean Architecture and how I would scale the structure as the code base grows:
How do I make my architecture “scream”?
According to Uncle Bob an architecture “screams” when it clearly expresses its core business purpose.
The top level folder structure, the project/DLL names and the namespaces should express business aspects rather
than frameworks or other details.
Athena is a web application implemented in ASP.NET MVC. But is this important?
I could switch to Ruby on Rails or Node.js - it wouldn’t make any difference for the business.
Why do we let such details impact our project structure so often?
Every now and then I come across questions on how to handle dialogs in MVVM pattern with WPF.
Honestly, most of the solution proposals I don’t like as they - from my perspective - somehow
“violate” the MVVM pattern.
Of course there are endless very good posts out there about Markdown + Jekyll + GitHub Pages and I am not going
to repeat what others already have nicely documented. So let me just summarize my setup and referring to
others for more detailed explanations.