Who needs an Architect?
This article is about mainly about the relevance of architecture, and it gives a funny analogy at the start which is that if you design a building it is very difficult to change the basement but in software development with design patterns you can make shifts to the foundations of your architecture without impacting the entire software “basement”.
In this article focuses on the idea that architecture is the shared understanding of the design when working on a software project and that the architecture is where you will decide the components and interfaces that will be used, and those are the most important parts of architecture and the ones developer focus on.
It is important to know that by having a good architecture, we can play with the components in a smart way and make the system reversible, good software architecture wants to avoid the replacement of irreversible components, there isn’t a perfect way to write software but having a good architecture is crucial to accomplish software that is going to be maintained easily and that is going to evolve and grow without many complications for the developers.
This was a really interesting reading and it makes you evaluate many things of how we write code and how we should write code to make it more efficient and overall, better.
Comentarios
Publicar un comentario