Chapter 14. SOFTWARE ARCHITECTURE

This lecture captured me through the first lines of it, I think how he explained the concepts are very easy to get them, although the author doesn't go deeper in the concepts it explained them clearly, maybe it's because it's an introduction to the chapter. 

I recall once my professor Roberto Martinez Roman told us that programmers look a lot like architects because we also need to create first blueprints to create high-level software, and that's a phrase that will be stuck in my head for the rest of my life. And while I started reading this chapter I noticed that the author made the same resemblance professor Roberto Martinez did. Like architects would like their building to stay safe and see if it's feasible to build it, programmers would love their programs to stay without any bug or even worse problems. 

For that reason, Software Architecture helps us out to validate if it is feasible to program it also we can ensure that the code won't have any gaps hackers can penetrate. the architecture helps us to validate if we are not duplicating code. Software Architecture also helps us to communicate, it's very important that all the stakeholders are aware of what is going up. 

As in the book says the architecture is the initial system design, therefore it's the first approach to the project, it's very important that there is a specific person to do it, it's not an easy job, indeed, for you to become a software architect you must study day and night to achieve this goal. The architect must have the notion of what he's doing because his work will affect everyone.

I'd love to get all these good practices down, I don't like changing my code once I wrote it, and I think all these good practices will allow us to write more efficient code giving us the big picture.