Ir al contenido principal

Houston, Tranquillity Base here. The Eagle has landed

Throughout the years,  we have seen space as something far away and with lots of mysteries that we have not been able to solve or to even try to understand. An example of this is the "Dark Side of the moon" or even the theory of aliens and other lives. 

Even though those things are still a mystery, we still have the fact that we have visited space and even landed on the moon. This moment was really hard due to the fact that technology was not advanced and there was not enough research for creating what we needed.  Also, it is important to mention that people who developed software did not have a methodology to follow, so there were many malpractices in the development of some of the programs. 

In the case of the mission Apollo11, and the whole Apollo program, the US  government had some trouble due to the fact that they needed to ask universities to help them to develop the technology. 

These requirements and the stress of the due date for the program became the problems for the development of the project. In this case, MIT had the opportunity to prove to them that scientist has the knowledge and ways to create new things to help society. Also, there is a chance to show them that teamwork makes the difference, but the correct way to do it was the problem.  Another problem they got into was the freedom they had to solve each problem the US government asked them to solve. 

I consider that the teamwork and the innovation they had to go through was the real achievement in the mission, and also that we have learned there are some malpractices that nowadays programmers should not follow. The problems they had though the mission could have been skipped they had known there were a process and good practices such as documentation,  getting the requirements and doing what they been asked to do. 

This mission was something important in our history, and as engineers, we should learn from the problems other people have been through. Technology has evolved and we should understand the limits and needs of our society. 

Comentarios

Entradas populares de este blog

What we should do?

Nowadays we think that computer science is a big factory, where even though that our offices are fancy and do not look like an office, we just program to generate more code, so get more money.  In this case, we think that coding is just an alone activity that does not include more activities, such as the whole software engineering process or something like that. As we have known,  there is a process that we should follow to generate code in a more efficient way and something that our users really need and when they need it. As time goes by, there was a point where we thought that cascade method was the ultimate idea and that its use was gonna stay forever and that its use was something that we will need to use for a while. We might get this idea from other engineers where they just get the requirements at one point and to change just for special moments accept the change. The basis is of this idea is that these type of engineers have got just enough time to really see...

A kid? A kid just broke my program?

LNowadays is common to think that anyone can use your software. In this group of anyone, there is the group of people who know and people who doesn't. We, as software engineers, need to take I to consideration both sides because just anyone can get access to  information that might not be for them. A clear example of that is Netflix, which includes a restriction for kids, or YouTube and even Facebook. To get to that point we need to think in our users,  and what they could do. In software engineering there are many methods to create these elements and to really analyze if they are really necessary restrictions or add-ons. On the other hand, we need to take into consideration the data that we are managing and to really send it in the correct way  to avoid people who steal our information even though that we are not that famous or important. In the case of the movie  War Games, set at the begining of the internet connection as a service, who anyone can access just by...

“God is in the details.”

When we talk about architecture,  what we normally think are buildings, their characteristics, how they make beautiful our city. We do not think about the time architects take to build something big and beautiful, and how changes affect the whole project.   We know that architecture is something that has been evolving since the beginning of time, where people tried to build what they needed. But also, this science has been evolving and the way people build takes more time and there is science behind every decision they make.   When we think about the software we do not identify this process that we need to follow to create something functional, useful and that will be used, we think about the algorithms or complexity of the problem.  We are not used to planning, hear the necessities that people have and even the methodology that we should follow to keep our software for future generations.   I consider that this practice...