Is design dead?

What I found most important in this article is how it addresses the fact that, today, designing a software architecture has become something extremely complex, but why? Simply the applications that the engineers develop become too complex to know, from the beginning, everything that is going to be needed and the problems that are going to be generated. This is why having an initial architecture, as the project progresses, it is modified too much or left aside due to its futility; however, we cannot begin to program an architecture without having a base, a planning.

This reminds me of when we made our life plan in high school and many people said "Why do we do this? We don't know what will happen in 5 years, everything may change." And of course, everything changed. But having made the life plan allowed us to have a slightly clear picture of where we were going, it allowed us to take small steps towards where we wanted to go and whenever there were doubts we could consult that life plan to find out what was next .

Something similar happens, in my opinion, with the design. It is not something that should be followed to the letter, but it is a kind of guide that you may or may not follow depending on how the project is developed, but if you do not have it there will be no way to go to the place Right.

In my opinion the design is not dead, it has only evolved into a completely different thing. It is designed less and produced more, yes. But this design is more abstract, less specific and allows to be permeable in the development of the project for future changes. It focuses only on the fundamental parts that should not change to meet the system's requirements, but leaves the most specific things such as technologies, service architecture, database, for the consideration of the people who will develop the project, etc.