Moon Machines: The Navigation Computer

Moon Machines: The Navigation Computer


The "Moon Machines: The Navigation Computer" is a documental produced by the Science Channel and it tell us the story of how the MIT and the NASA joined efforts to produce the navigation computer system that should manage the landing of the Apollo 11 to the moon.
OK, once the resume is ended my opinion comes, I liked a lot the video, it was fun when the problem was presented like something obvious “we need to put a ridiculous giant computer in a spaceship” in that time it was a really difficult and almost impossible mission so it took a lot of effort and work team.

I liked how the documentary makes a route from the life and point of view of the involved people, it also shows the difficult of the problem and how some of them give up things of their personal life, in my opinion it was an extreme decision but now they are part of the history, so maybe it worth it.

Some of the challenges were the memory of the computer and of course, I mentioned already, the size, so the solution is now known as Apollo Guidance Computer.
One of the things I fond fascinating was how the operative system choose the tasks based in the “importance” they have. In this way, the OS could be sure, by itself, the most important tasks will always be accomplished.

I almost forgot it, the errors were written in a piece of paper, it does not seem like something the NASA will do, it is more like a backup I will do if I forgot my laptop.


At the end, I keep in mind two things, first, for every projects is important to have a plan, and follow it in the best way possible and creative solutions could not sound logical but an open mind can find a way to implement them.

Comentarios

Publicar un comentario

Entradas populares de este blog

Is Design Dead?

Is Design Dead? I am going to write about the article “is Design Dead?” By Martin Fowler, it was a interesting article and was written in a unfamiliar way considering the title. He starts talking about the extreme programming and how it is one of the causes of the poor pre design that nowadays is (barely) used for big or small development. Software development needs like almost everything a design which defines not only how it will work, but how to make the specific modules and what job they are going to perform to accomplish a global goal. And well he basically explains the differences between planned design an evolutionary design, that is the reason why I think the title is funny, two kinds of design but he says it is dead, basically what happens is that, the extreme programming and the constant use of the technique pushes the developers to use the evolutionary design. Why? Easy, the extreme programming is a practice thas searchs the simplicity in the creation of...
Leer más

Software Architecture

Software Architecture This week I read the chapter 14 of the book "Code Craft: The Practice of Writing Excellent Code" titled " SOFTWARE ARCHITECTURE Laying the Foundations of Software Design" the first thing we should do is define what is software architecture, as we use the word architecture sounds logical that a building comes to our mind, but talking about software we can take the idea of a structure, so the author told us we can join the concepts to create in our brain the idea of high level design but of course the reason of the “similarity” in the concepts comes because the software architecture is used to create a propitious place to make code, at the end this can be used as a guide for the development. Some benefits of the software architecture are that this helps to validate requirements and conditions of a project so it can be used in a more free way for the different areas like design and development and can help to “talk the same language”,...
Leer más

Understanding the SOLID Principles

This week the blog will talk about the article "Understanding the SOLID Principles" written by Edward Guiness, this is a brief summary that presents the definition of the SOLID Principles. The general objective of the SOLID principles, and so the author in the article, is to implement best practices in the creation of objects and classes in specific cases depending on the situation that is presented. And with you, the 5 principles *drumroll*: • Single Responsibility Principle • Open/Closed Principle • Liskov Substitution Principle • Interface Segregation Principle • Dependency Inversion Principle The first of this is the Single Responsibility Principle, it says that a class, should have just exactly one responsibility, just one reason or an only class of reason to exist. This responsibility should be implemented to the class, so for this reason a class just has one reason to be modified. Why implement this? Easy, in a big project you will have lots of classes ...
Leer más