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.
I say, its worth investing in and learning. Not necessary to force you to do this, but to see it from this view and if its any good. Sometimes drastically different views can change how you program, without completely getting lost into it. In example, a Python or JavaScript programmer who tries out Haskell and learns how it works, does not mean will completely convert to Haskell. But it might give the person good habits reason about future Python and JavaScript code, and prepare and handle it differently.