Is Design Dead?


Today I will talk about the article Is Design Dead? by Martin Fowler (May, 2004).
I think it is important to design first and then code, this will avoid the code and fix. Also, the quote that says “if you listen to your code a good design will appear” it doesn’t make sense. It is very interesting to know that there are two styles of design.
    The most common and disastrous is Evolutionary Design, as the design of the system grows as the system is implemented, this style makes it difficult to change the system. On the other hand, we have the Planned Design, here the designers don't need to write code because they aren't building the software, they are designing it, in this way, they avoid entropy by making decisions and carrying out the development of the software.
    Although the second style is much better, it still has faults, not designing and coding at the same time, it can introduce complex problems in the programming stage. The other fault, which I found quite interesting, is that the designers do not codify more outdated technological issues and lose respect for those who code.
    Designing a system can be a very heavy and one of the most difficult tasks, 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 many factors that can completely modify the design, such as the requirements, those that can be adapted in a certain way or even with a good requirements survey, can avoid the changes in the requirements, but what if something changes the business it would be more difficult and can not be prevented.

Comentarios

Publicar un comentario

Entradas populares de este blog

Hidden Figures

Today I will talk about the amazing movie titled “Hidden Figures”. Normally in those times they didn’t recognize all the women were part of important projects and this movie is one example of how they used to hide the work from the matchless Katherine Johnson. I can say that it has become one of my favorite movies.     The film tells the story of three African-American women who worked for NASA in the early 1960s, collaborating in an important space program. These brilliant women achieved incredible goals that seemed impossible because they were women and African-Americans.     What impresses me about these women is their intelligence, their strength, their perseverance and their struggle that allowed them to demonstrate that they were more than capable of being involved in areas that were considered suitable only for the masculine intellect, such as science, mathematics and engineering.     I can identify a little with those great women of that movie, not because of how brilliant t
Leer más

Understanding the SOLID Principles

Today I will talk about the Edward Guiness’ book section titled “Understanding the SOLID Principles”. First of all Solid is an acronym that stands for five principles of object-oriented programming and design. These principles help to avoid dependencies between the classes. S-Single Responsibility Principle O-Open/Closed Principle L-Liskov Substitution Principle I- Interface Segregation Principle D-Dependency Inversion Principle Talking a bit more of these principles we are going to explain each one: Single Responsibility Principle: This principle states that one class should only have one responsibility so the changes in that class do not end up affecting unrelated critical features on the system. This happens from a single action to a set of processes. You can take a view that a single responsibility refers to a group of related business processes. The stamina and tolerance determine how far you go Open/closed Principle: This principle talks about that classes should be op
Leer más

Microservices

Today I will talk about the article “Microservices” by James Lewis and Martin Fowler (March, 2014). This term is used to refer to a way of designing software in small independent services that will work together. This is used mainly in business applications and has some peculiar characteristics.     In other words Microservice Architecture means, a microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with each other. These services are built around business capabilities and are independently deployable.     Microservices have a great advantage over a monolithic application, because this style does not put all the functionality into a single process, and  if you want to make a change you do not need to rebuild the application.     Of the most interesting things that this design pattern has is that each microservice can be seen as a black box, and thus remove a bit of the comp
Leer más