Codecraft: Software Architecture (Commentary)

Turns out I haven't been a very disciplined programmer after all.

Once code is compared to something so mundanely necessary as a building, one can see why following a pattern or plan while programming (specially if it's done as a collective effort) is so important. I believe the comparison of Software Architecture to regular architecture is very accurate since just a change in the pattern of building could be disastrous if such a structure (be it software or real) is not ready to be changed.

I keep seeing in all these sources that software architecture's general aim is to make code as flexible and change tolerant as possible for each specific case. Not implying that code should be terribly general (as the source states in this case), but that a general template may be created for different cases that could be developed in the near future. Similar code should be easily reusable should the need arise in a further project. Not out of necessity to comply any rules regarding software architecture or development good practices, but for convenience itself.

It should also be modular enough for it to be change with the less effort possible, which is something that happens very often in the industry.

According to all these guidelines, I haven't been doing a very good job at presenting (or even thinking about creating) a pattern to follow when programming, but I definitely see the utility of Software Architecture.

I can even think of several cases where software architecture could have helped me avoid severe design mistakes.