https://geisonbiazus.github.io/posts/All Posts | Geison BiazusHugo -- gohugo.ioen-usgeisonbiazus@gmail.com (Geison Biazus)geisonbiazus@gmail.com (Geison Biazus)Thu, 27 May 2021 09:30:00 -0300https://geisonbiazus.github.io/posts/applying-clean-architecture-in-go/Thu, 27 May 2021 09:30:00 -0300Geison Biazushttps://geisonbiazus.github.io/posts/applying-clean-architecture-in-go/<h2 id="introduction">Introduction</h2> <p>One of the problems I frequently see on many software projects is the coupling of the code and how hard it is to make simple changes without undesired side effects. This happens mainly because developers tend to focus on building the features without thinking about how the codebase will evolve in the future, and also without taking into consideration that the libraries and frameworks they are using today might not be the best option in some months or years.</p>