Hidden Figures

 It was the first time I had seen the movie Hidden Figures, I really liked it. It was a really nice story about women and especially black women and their contributions to science. I believe it is important to recognize the role of women in science and engineering. Also, the movie helps as a grim reminder that segregation was not that long ago, that it was less than 60 years ago, and that there are still people that lived through that period of time. Of course, I am not saying that racism is no more, but we have made progress on that, nowadays there aren’t segregated bathrooms. The part where the boss of Katherine broke the sign in the bathroom so that she would not have to go to another building. Also, the actress of Katherine did an excellent job ranting about why she missed like 40 minutes every day, you could see the frustration with circumstances she could not control.

There were several good scenes in the movie, but the one I might have liked the most was when Mary Jackson was in the courtroom and convinced the judge to allow her to assist to an all-white school, as she gave a good speech and the actress portrayed really well that scene. I believe the character of Dorothy was the one that the movie neglected the most as it is the one with the least scenes I remember. Seeing some of the differences between the movie and real life, I am glad that they managed some of their goals earlier than in the movie and that some of the hardships in the movie were exaggerated. I totally understand why they changed things to make for a more entertaining experience as I believe that the courtroom did not happen, she just asked for an exception and was given one.

Comentarios

Publicar un comentario

Entradas populares de este blog

Is design dead?

  “Any unneeded complexity makes a system harder to change in all directions except the one you anticipate with the complex flexibility you put in”. I believe that quote of the reading is the one that does a better job explaining why you need simplicity in the code and the strong point of programming for the present, not for the future. As indeed making a part of my code easy to modify would need that I make the assumption of what type of change would be needed in the future. I really like his moderate posture or coward as he calls it because in some of the things he mentions regarding design or having absolutely no architecture at all, do sound too extreme especially when in situations where is clear from day one that you do need a database. I particularly like his posture in regards to architecture of doing it, but take it as a sketch not something written in stone as you do not know what possible requirement changes come in a project or what specific issues come during the programmi
Leer más

SOLID

  The SOLID principles are really good advice and were explained in a really simple way during this article. Some of them I had already heard as in the past I have read one of Uncle Bob’s books during the Videogame project course. The Single Responsibility Principle is the only one of the principles that until now I always have in mind while writing classes, although being honest just as the article says it is not always that straightforward what would be considered doing only one thing, so sometimes I may not apply it perfectly. The Open/Closed Principle and the Liskov Substitution Principle those are principles that are new to me and certainly go against some of the things I knew.   Because I had learned to use inheritance in those situations, although reading the article I agree that abusing inheritance may not always be a good idea as it may leave the code in an unpleasant state or generate side effects. The Interface Segregation Principle I never had thought about doing that,
Leer más

Software Craftsmanship

  I have been trying to avoid of thinking of programming as a craftmanship since some years ago because we were kind of thought that it was incorrect. During our software development courses we were taught that treating it as a craftmanship was what caused it. But the way uncle Bob explained it as a craftmanship did resonate with me as indeed you do feel proud of your code when it works, and when you manage to program an elegant solution or a clean code it does feel better. Also, everyone has their own way of programming for example when in a group project I see a variable with an unholy name such as ‘iiiiiiiiiii’ I immediately ask Óscar if he did it, and with people you have programmed multiple times you get a feeling of how they code. Maybe it is not a wrong way to see code after all if you can follow the software craftmanship manifesto, which indeed as they say it is not nearly as popular as the agile manifesto. The points in them do sound like really good programming practices to
Leer más