Chapter 2: Moon Machines = Moochines?

So last class we saw "Moon Machines: Navigation Computer" and it was very interesting for me to see all the things that went on "backstage" for making the moon landing a reality. All the calculations, optimizations, new developed technology and the people behind it were truly amazing, as well as making ground breaking technology on the go.

Apollo navigation system

But the thing that interested me the most was the process of how they got an initial model and then they built from there; making it smaller, more resistant, optimizing space, response time, number of processes and prioritization rules. It all started when the contract went to the MIT to develop the guidance system, even though the budding industry that had already built guidance systems was not considered. The initial navigation system was based on inertia, physical resistance of any object to any chance in motion, tested with success on an airplane, only diverging from its course to correct itself from external factors.

I also liked how the project adapted itself to fulfill the needs of reaching the moon. First, they got a functional navigation system, then they started adapting it to “space” standards, as gravity and other important factors would affect how the machinery made its calculations. They later brought aboard mathematicians to optimize calculations, as well as other programmers to remove redundancy in the navigation code. Finally, the concept of “semaphores” rose as a need to start prioritizing important tasks over other minor duties to avoid overloading the computer with unnecessary calculations when critical task were being executed.

Concluding, building a navigation system was a difficult task, facing great challenges in systems engineering, physics, mathematics and other fields. Great organization, teamwork, and precise calculations were needed to archive their goal, just as any other objective, we must discipline ourselves to reach our targets. I´m sure we will learn through the course of this class the aptitudes we need to make successful systems through careful design and architecture.

References:
Science Channel (--).Moon Machines: The Navigation Computer.

Comments

Post a Comment

Popular posts from this blog

Chapter 4: Architectus Reloadus vs Architectus Oryzus

Image
So, who needs architects anyways? Here lies one of the most important roles in the software world the unstoppable Architectus Reloadus. After reading the article, it reminded me of an image picturing 2 groups of people; each group having either a boss or a leader commanding them. While the boss was just instructing where to go and what to do, the leader was working with its group. This is the same analogy we get in the article with the 2 types of architects mentioned, the  Architectus Reloadus  and the  Architectus Oryzus . Architectus Reloadus  is the architect that proclaims himself as the  most important part of the project , as the design is made only by him, leaving the other developers to follow. While the  Architectus Oryzus  works within the team to improve the team’s level so they can approach harder and more complex issues. In other words, the Architectus Oruzys  is a guide, skillful enough for being the anchor of the team, and clearly selfless, as he works at the
Read more

Chapter 9: Microservice Architecture: A whole new Architectural world.

Image
After reading the article, I started relating microservice architecture with the activity we made when we talked about components and Lego bricks in class: This type of architecture is made of smaller and independent services that are linked together to form a concrete service. With the image below, we can see a clear representation of how this is conceptualized. However, there is a small detail that separates microservices from monolithic services; while the later gathers all functionality into a single process, the microservice separates each part of the functionality into a separate service, allowing scaling with distribution of the services, replicating as needed. This is the aspect I liked the most; low key planned modularity for software architecture (or at least that’s how I see it) There are a lot of interesting features of this type of architecture (with a heavy approach to encapsulation, as I dare to confirm), such as Componentization via Services, Organized ar
Read more

Chapter 11: Metaprogramming

Image
The last article read was “An Introduction to Metaprogramming”, an interesting article where Ariel explains the concept and some examples of metaprogramming. Starting of describing the different types of metaprograms, like compilers, interpreters, parser generators, assemblers and preprocessors, metaprograms come in many shapes and forms, which main goal is to eliminate or reduce error-prone programming tasks. I have heard of this concept as a utopic approach to things, however, I haven’t seen metaprogramming first hand. At first, I thought it was a really complex way to do things, but after reading the article, it doesn’t go that deep into weirdness. Beginning with the first example; it clarified how the concept of metaprogramming works, a script that wrote another file with the code expected. While the ruby snippet shown was not some other world stuff, but the example is pretty clear, we can write codes through code. Now, the second example goes a little bit deeper
Read more