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.

Comentarios

Publicar un comentario

Entradas populares de este blog

An Introduction to Metaprogramming

It is impossible that after reading this article we can´t remember the Programming Languages class. That part of the course when we began to learn about metaprogramming also I remember that in the class’ book were pages that have the quote that said that if is not necessary to create a macro don’t do it or in my case don’t try to do it and this was because that topic is difficult to understand, this topic was not an intuitive knowledge, I think that you need to be a high level programmer in order to make this kind of code. This kind of code calls himself a program that generates other programs or program parts, yes, this sound a bit confusing. So, the professor Ariel Ortiz told us in the Programming Languages class that the people who recommend to don’t use metaprogramming only if it is very necessary are people that don’t know how to create macros and the potential that these tools have and, in the article, we can see reflected that hypothesis of the professor. Even he puts an exam
Leer más

Understanding the solid principles

This article talks about the SOLID principles which in fact as you known is an acronym that stands for five principles of object-oriented programming and design. Those principles allow us to avoid dependencies. So that means that the more things you depend on the greater the chance of something will go wrong. The principles are: Single Responsibility Principle, Open/Closed Principle, Liskov Substitution Principle, Interface Segregation Principle and Dependency Inversion Principle. I will talk about them quickly and explain why are they so important in our life as programmers. The single responsibility principle talks about that a class should have exactly one responsibility. That means that we have to have classes with a specific purpose and not mixed classes that if we erase something all the code went wrong or different. The open/closed principle talks about that a class should be open for extension but closed for modification. That means that we have to counter the tendency for
Leer más

Hidden Figures

In this post, I will discuss the movie that we saw in class: "Hidden Figures" directed by Theodore Melfi in 2016.    It's the second time I've seen Hidden Figures and 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 they were, but because, despite being in the 21st century, in my care
Leer más