A01375332 - Arquitectura de software

  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

  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

  “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

  The reading did raise two important questions one that I had thought of before and one that I had not, and I believe the one I had not thought about is important to answer the other one. The one I had not thought about was, what is software architecture? I just took the definition given in class at face value, and that definition was really similar to the one given by the IEEE. I just accepted that architecture was that even though it was abstract enough to not be sure what specifically entails the term. I believe that those cynical definition given by the author feel more specific, like they help more to recognize what is software architecture. The question I had already asked myself is, when does someone becomes and architect and what are the qualifications? I asked myself this because seeing the tittle I just thought I definitely am not an architect, but what would it take to become one, or when do you know you are one. The tittle sounds kind of arbitrary because as seen in last