Skip to main content

Hidden Figures


On today’s blog I’m going to talk about a movie called Hidden Figures, directed by Theodore Melfi and released in 2016. I watch this movie during my class of software design and architecture and I have to admit it, I liked it, but not that quite much, is the kind of movie that you could see in a Sunday morning on tv, at least for me.

The movie talks about three women and how they helped the NASA during the space race to make during the cold war (I think it was during the cold war) against the Russians. In the movie there are introduced three women, Katherine Goble, Mary Jackson and Dorothy Vaughn, who are trying to contribute and make their own way through their jobs in NASA. More importantly the movie shows how they struggle because of the discrimination at the time, so they couldn’t receive the treat they deserved, all of this happened during the NASA project of the first man to the moon.

For many of us, we can´t imagine that kind of discrimination, but in the movie,  it shown clearly crude, for example, there were two types of bathroom, the one for white people and the one for colour people, specially designated places in the public transport, even different color of coffee mugs! Literally that’s insane

The movie really shows how these three women break their necks in their jobs to move forward in their career and make really good contributions to their area, not only because they were geniuses, but the effort and perseverance they had to step aside the problems and face them face to face, and win, and that is what everyone should do, not everyone is a genius, I’m not a genius, but with enough effort, anyone can achieve great things.

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