Software architecture
Software planning and design was not something we gave the importance it has when we started programming, creating and developing small projects for our courses. It was only when we started making greater projects that we became aware of one of the statements the chapters make: having a mess spaghetti or subway-like it’s going to make it hard for you to know what you did, how to fix an error, where it was or to add more functionality. What I take from the lecture, besides the types of software architecture and how it resembles pasta, is how awfully important it is to plan and create a design in the early stages of how your project is going to be implemented to have clarity and help the detection of errors or lack of requirement fulfillments. Just what happened to us last semester when we had to redesign the whole project midway into the semester. Still I had not come up with the term software architecture and if it was not for that lecture, I still would be confusing it with othe...