Clean Architecture: You probably don't want this
In today's episode, I'll return to the topic of excessive concern brought about by architectures that attempt to accommodate potential technological changes. Clean Architecture is the prime example of this today. Inspired by multiple layered architectures, it tries to lump everything together into one package to give you a kind of interesting guide.
Besides creating a concern that, in my view, tends to be exaggerated and probably unfounded, creating software decoupled from many things slows you down, makes you more prone to errors, and potentially leads you to use all the technology you've decided to bring into the project in a less effective way.
If you believe that technology should help you in development, why would you want to remain decoupled from it?
Links
Original post about Clean Architecture - https://blog.cleancoder.com/uncle-bob...
Post that gave rise to CDD - / ddd-para-aplica%c3%a7%c3%b5es-web-modernas
Article about the impact of CDD on refactoring activity - https://github.com/asouza/pilares-des...
Learn more about the Efficient Dev Journey:
About the training - http://deveficiente.com
Learn more about me :)
Github: https://github.com/asouza
Twitter: / alberto_souza
Instagram: / devênio