Ir al contenido principal

Moon Machines


The race to the moon just began after the second world war, the world giants were facing off (United States of America and the Soviet Union, east versus west) - The Cold War. This is translated to a competition in which both sides are involved in a confrontation with various branches: political, social, military, scientific and economic. But from all of these, let us focus in the scientific part (even though in the video you can dive under the surface to understand whydecisions were made and you relate those scientific advancements with political and social matters).

This was quite an instructional and interesting video. There are a couple of sections I enjoyed but the most likable - in my humble opinion - was when they were explaining IBM's gyroscope technology to have a reference as to where were they, I find this the most clever and genius way to implement a solution as they attacked on all fronts: budget, space, simplicity.

As an addition, I find honorable and respectable how IBM was so sure their technology would work so they blindly-ish (sic) trusted it on their flight to California, flying all across the United States.

A phrase I remember, and I can empathize specifically was when it was told that “walking in the moon was easy compared to landing the Apolo on its surface” (not exactly their words to be honest).

Why do I empathize with it? Because sometimes in our everyday lives we think that X is such a hard task/goal/objective but not really… personally, I find that the way to achieve X is n-times more complicated, most of the time (if lucky) we know where we want to get to, but have no idea of how to get there. All these men/women who got one of mankind’s greatest achievements are infinitely admirable as they just do what it takes, they proposed something and they got it (let’s forget the why’sand let’s just focus on the how’sand what’s: 
-      Why – many political, social, etc reasons
-      How and what – achieve landing in the moon and going back to Earth safely with their crew.


Comentarios

Entradas populares de este blog

Who needs an architect?

Since I was a little kid I always wanted to change things to work in a more efficient/easier/convenient way, as simple as organizing my toys as per usage, this idea evolved all the way to my professional career. Currently I manage projects of commercial systems and what I've found are many learnings: Similarities between a project manager and a software architecture Get $#!T done, a PM has to ensure communication and that workflows happen, as well as an architecture according to the lecture, has to have some high convincing skills, as his recommendations have to be listened and applied  Experience and responsibility As said previously, recommendations and tips... there's nothing like experience of getting involved in projects in order to have your voice have a valid and substantial background Importance and scalability A PM as well as a SA must have under their scope how easily their project/software will be taught, learned, scaled, this is their res...

Software Architecture

In the lecture of Code Craft we can see how software architecture is a high relevance topic for computer science, talking about how its evolution has increased the investigation and study cases. "Initial system design"... this is what Goodliffe mentions architecture is. This takes us to three pillars or cases in which architecture has jurisdiction: validation, discrimination and communication. Previous cases have direct impact in how you can avoid work duplication, redundancy, and wasting efforts (validation) When having proper software architecture, you improve communication as this helps with a high level view of what may be a complicated system or difficult to read to all stakeholders in a project. As for discrimination, it says how some situations can generate problems while decision making, having this concerns validated  we can then discriminate  some options. Mainly, the purpose of the lecture is to understand the importance and objective of s...

Microservices

From monolithic to microservices . This is dangerous and even though this is how my mind works, sometimes, may be limiting our minds. The idea of microservices, I believe is an amazing approach to development, and much more currently that we have whatever/anything/everything as a service , companies tend to have cloud solutions and plug n' play compatibility with different services. The microservices architecture must be an approach that jumps into your mind immediately whenever you think of implementing something in a company, or as a developer, developing for a company. Nothing's more scalable and easier than services connected in between just by API endpoints. I'll defend microservices architecture all the way. (: