Who needs an architect?

It is real that building something is really complicated. Just imagine all the procedures that architects have to do in order to make a building stable. On the other hand, software is a little more complicated. There are many things that make the code complex, and in sometimes, hard to change. Just imagine a code that if you move one thing, you have to move a lot of more things. Making a code not hard to change is a challenge.

The question is why. Simple, we’re used to coding at a low level and that’s why making changes are sometimes really difficult. For example, if you’re a programmer, then you should now that when you are writing the solution to a problem and suddenly a better solution comes into your mind you erase all the code because you don’t know how to change it. That’s because schools teach us that we must write at a low level. But what if we try to code at a high level. Having this particular ability, we must be able to write code and change it easily.


And the article here has a lot of sense. Just imagine working at a high level as architects do. We must have an easier way to write code. But here comes the other hand of the business. Who wants to be an architect? If enterprises allow me to code in low level, then why I must move to high. First, we have to think and plan a lot. And I’m not paid for that. And we began to put a lot of excuses and never moving to a high level of thinking and writing.  But if we put that apart, maybe, we can create a lot of better things. Imagine if an architect thinks the same as us, then buildings will be a problem, but they are not. We shall move. Don’t you think so?

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