A great .NET podcast and interview of Steve Smith. .

Be sure to check out Steve's article "Clean Architecture Sucks" . If you find that it does "suck" then you're not doing it right and therefore not reaping it's benefits.

While I really like much of what Steve says in the podcast about how to structure the code for Clean Architecture, it falls short by one important aspect: organizing modules by Visual Studio solutions folder as opposed to projects. The only real way to know if you're doing Clean Architecture right is by quantitatively measuring. How do you do that? Well by using Robert Cecil Martin's design metrics of course. These metrics are based on "packages" which in .NET speak translates to assemblies and therefore projects so you must structure your code with projects in order to capture the metrics. Done manually this can be a lot of effort for a non-trivial project, but you can automate it with the Roslyn API. I've done it so sample code and possibly tools forthcoming.