Moon Machines

Moon Machines

The struggle to take the man to the moon

So, tonight I just finished watching this documentary called "Moon Machines EP3: Navigation Computer" in Youtube. To be honest, I've never been too keen into space and aeronautics, so my knowledge about spaceraft technology and history is not great. I've always supposed that aerospacial engineering ought to be quite a challenge, and probably Apollo 11's mission to put a man in the moon is the peak representation of years of research and development of hundreds of engineers and scientists. However, I cannot help but to state I am completely astonished by the content of this documentary, as it relates one of many obstacles that engineers had to face in order to achieve the mission in time and quality: the navigation system in space. 

The first thing that caught my attention is the fact that the US government chose a university as the main development centre (MIT) to achieve the mission, even when there were already navigation-tech entreprises that had applied to obtain the same position. It is encouraging for a student to know that not always big organizations with specialized technology and facilites have what it takes to complete a task or develop new tech.

And then comes the limitations of computers in the 60's. Adjusting and adapting the sizes of computers in order to fit into a spaceship sure sounds quite ponderous, however, as a programmer, what I couldn't help to imagine was the pain it surely was to program by hand and then print it in hundreds of different holed cards in order for the computer to be able to process it, and don't even mention the hours it took to give an output, and the possibility of this output not being correct. I mean, I've commited plenty of mistakes while programming, and by itself it's often quite frustrating and desperating when you cannot manage to get the desired performance of your program. Now add to that frustration the hours of processing data that took to a giant machine that could barely stand 72Kb. It's unbareable.

However it's intrguing how nevertheless the limitations of their decade, they successfully managed the objective and took the man to the moon in 1969. Many persons say that the amount of work and effort was such that they lost family and marriages in the process. I do think this is a shame, because they gave everything to achieve the purpose and many of their loved ones didn't seem to have the ability to stand up with them.

Comments

Post a Comment

Popular posts from this blog

War Games

War Games War Games is a sci-fi movie from 1983 that narrates the story of David Lightman, a teenager that trying to hack into what he thought was a videogame development company accessed instead into a top secret military base computer and initialized a "game" called Global Thermonuclear War, which ran a simulation of a nuclear war between the USSR and the USA, driving everybody mad as they thought the simulation was a real deal, and giving a head start to a potential World War 3. Even though it is considered a classic, I must admit I had never seen the movie, not even heard about it. I watched it without knowing a thing about the plot, and I enjoyed it more than I expected to be honest. However there are a lot of things that I found a little absurd and highly unlikely to occur in real life. The plot itself, for instance. Just to think that a kid by accident has the ability to enter a military base is something I found too fictional to my taste, even when we are talking...
Read more

Software Architecture

The power of good software architecture The importance behind a simple, yet efficient design. In the chapter 14 of his book "Code Craft", author and developer Peter GoodLiffe talks about the importance and influence of good software designing. I found it quite practical (and a little unconventional) how he describes the different styles of architecture in software through comparisons with pasta. I was so hungry yet intrigued while reading through the descriptions of each type and the different applications each have for different situations. I always find it overwhelming how easy it can seem to make a good base to develop software, and yet there are so many sources and lectures on how to get it right, as it is clearly underestimated how challenging it can result to make not only a functional software, but flexible, modular, esthetic, and reliable. And the most difficult thing of all is that there are NO right answers. There are NO instructions or guides on how to b...
Read more

Understanding the SOLID Principles

Understanding the SOLID Principles In a section on the book “Ace the Programming Interview: 160 Questions and Answers for Success”, Edward Guiness talks about a set of practices to have simple and efficient code: The SOLID Principles. The acronym stands for:  Single Responsibility Principle Open/Closed Principle Liskov Substitution Principle Interface Segregation Principle Dependency Inversion Principle The Single Responsibility Principle (SRP) states that each class should have one and exactly one responsibility. Only experience and practice will help you determine what one responsibility envolves, The Open/Closed Principle (OCP) says that each class should be open for extension, but closed for modification. When adding new behavior, we should leave the base class alone and instead create new inheriting classes, and avoid unexpected consequences for the original subclasses. The Liskov Substitution Principle (LSP) says that the less inheritance we h...
Read more