cross-posted from: https://programming.dev/post/54023908
Hi!
I’ve never read any of Uncle Bob’s books. But I have taken interest in “Clean Architecture” as it seems like a good solution to make mid to large sized projects simple to understand and maintain.
I think MVC gets too much coupling and fails at larger projects, same with n-tier. But I’m not sure about anything right now (software design is a very complicated problem after all).
So I was wondering if you friends who have used Clean Architecture in production can share your knowledge and experience with me about this design?
Is it actually good and worth investing in?
Footnote:
I’m especially weighing this architecture because Uncle Bob’s writings are really hit and miss. I don’t see him as a master or guru so I take everything he says with a grain of salt.


Not the exact book, but the same author.
I’ve read two of his books (clean code and clean coder), and there are things I agree with, absolutely. There are also things I vehemently disagree with.
The main value I gained from them was by reflecting on the scenarios and his ideas on approaching them. Afterwards I made up my own mind on the subject.
They contained a good deal of subjects that I, as a very junior dev at the time, hadn’t even begun to consider, and by being aware of them, I could more easily approach them when encountered in the wild.
There’s also a historical aspect of knowing what has inspired, affected, or motivated, other ideas and approaches.
Take it for what it is, one person’s opinions. Some you’ll probably agree with, some you won’t. Just because someone is out was regarded highly in a field does not make their word gospel. It makes it worth thinking about and forming your own opinion though.