Is Design Dead?

When talking about software architecture, as a student, I think it is difficult for us to apply it normally in school projects, because we have many things to do and many times the time is limited, however, I think it is important to have a software architecture in companies, since it could be very difficult to understand how the system works. This is a case that I experienced when I started working, since, although they use a framework it is very difficult to see everything from a global perspective, and there are even several things that are hardcoded, I have tried to refactor but it is very difficult since those modules are used daily, then a small mistake could spoil the infrastructure, a roll-back can easily solves the mistake, but the downtime is terribly great.

Maybe I have already mentioned this, but designing a system can be a very heavy and difficult task, since that is where the structure and components of the software should be planned, and it is often very difficult to have future projections about what is missing or there are many factors that can completely modify the design, as are the requirements, those can be adapted in a certain way or even with a good requirement survey, changes in the requirements can be avoided, but what would happen if something changes in the business? It is more difficult and cannot be prevented.

It makes good emphasis on the design patterns, and I think it is right to say that possibly when we are doing code cleansing we are using them, even without knowing that we are doing it, but this must be something more thought to see the benefits and shortcomings of the pattern that we are using, and more if not even if we are considering a design.

And certainly, many times we decided to make progress right away, before making a diagram that can make things much easier. Students thing. But each strategy has its benefits and disadvantages, so it is up to us to decide which one is the best.