Skip to main content

Moon Machines


Today we are going to talk about a documentary by the SC (Science channel), were it talks about how the NASA created the APOLLO’s navigation system which helped the astronauts to land in the moon.

In the 60’s, the United States went through a difficult time, because it was during the period of the Vietnam War and the Cold War, the civil rights movements and many other stuff, and thanks to the tension between the americans and the soviets, along side the armaments race there was also a race to be the first in space too.

During this period, the president, John F. Kennedy focused on winning the “space race”, so that he invested many resources in the NASA, but not everything went like expected. After lots of failures the NASA started to hire engineers from the MIT to create the navigation system to reach the moon.

After all of this trial and error period, they finally succeeded to create the system technically from scratch using only a storage of 72KB, for us now this may seem quite remarkable and somewhat incredible because of the simple fact to create a navigation system of this magnitude in just 72KB, that and the fact that this concept of system was a term mostly unknown for the people in the time.

I think that the NASA took a great risk with this project, now I know  that it was worth it, but at the time it was a really tough call in matters of money mostly, not because of the creation of the spaceship itself, but all the logistics, resources and money involved in the software for the navigation system and all the maths involved in the creation of it, also the calculations for the landings, ignition, trajectory and all of that stuff, but now we can really reassure that it was totally worth it.

Comments

Post a Comment

Popular posts from this blog

Is Design Dead?

On today’s entry we are going to talk about the article “Is design dead?”, which talks about how the design has been changing through the years and how the good practices were developed in order to create a good design. Is no lie that for all the people that develops software, is kind of difficult to come up with a good design because of the lack of and standards to create it, other areas may have standards or even a methodology, but not us. Because of these needs, developers have created a bunch of good practices, not to create, but to reach a good design probably in a 85% of success. For example, a good practice is a that the code we create has to be modular in order to make corrections or complete alterations in a easier, this changes may occur for many reasons, manteinance, update the information or just to simply chage the entire code to something more efficient, the same goes to the design, but the problem is that a design is more difficult to modify when is already d...
Post a Comment
Read more

Microservices

On today’s blog entry we are going to talk about the Microservices architecture. This architecture has an approach where when we are developing a single app, we develop it as lots of small services, each of them running on its own process and communicating with each other with something that can bind them together. Now I have already used microservices without knowing I was actually using them, perhaps this architecture is quite intuitive for best practices or something like that, but anyway the author of the article gives some characteristics about this which are the following: ·          Componentization via Services: The components of the microservice need to be gather into libraries that will be used later on by the microservice to communicate with remote parts of the whole program. ·          Organized around Business Capabilities: This characteristic refers that we need to create divisions, e...
Post a Comment
Read more

Understanding the SOLID principles

On today’s blog we are going to talk about the SOLID principles, which were discovered by Robert Martin, the famous Uncle Bob from the podcast of the previous entry. This principles are recommended to be used whenever someone wants to create an object oriented program. There are 5 principles where the acronym SOLID comes from which are the following S ingle Responsibility Principle (SRP) -> it says that any class should only have one responsibility. Yet, the author ends up saying that there might be some classes that have two responsibilities (the invoicing class that has some logging routines). In the end, I didn’t understand this principle well because I found the explanation confusing (as the author said, practice is much more difficult than theory).  O pen/Closed Principle (OPC) -> open extension but closed modification Although the author says that if you change a parent class method it might kill another part of the ...
Post a Comment
Read more