3rd Design: Software Architecture or: Do we have time for that?


If I had to summarize my experience with most of the professors in my college career, it would be with the phrase: “I know you think it’s unnecessary, but one day design will save your life”. It’s funny because, for most of the 8 semesters I have been at this school, most of the students (including me) have thought about the longsome and “boring” job that is the process of establishing high-level decisions and general schematics for software projects. I now think that this activity is vital and can save a lot of time, effort and tears. The bad news, it’s one of those things that I had to live in order to learn.

Last semester, I was working on one of the famous i-semesters. Our task was to build a webpage that allowed registered users to see content according to their preferences and current skill level. When we started working and a teacher asked us to make several diagrams and split all of the responsibilities into modules, we all took it as another homework that we just “completed”, with much pain and laziness. However, as time went on and we realized that we had no idea of how to continue or if there were any errors on most of our code, those first designs helped us a lot. They helped us realize what was unnecessary or out of scope. With those documents we were able to save a lot of time and complete the project, although we had to redesign them around 3 times. 

I think the chapter and its overall contents are very clear and highlight the importance of using design as a means of achieving our goals in an efficient way. However, I know that because I have lived it. If I read this book around one or two years ago, I think that I would have dismissed most of its content without much thought. I think that life and real projects can be the best teacher for that kind of knowledge.

Comentarios

Publicar un comentario

Entradas más populares de este blog

10th module: Going Micro(soft)

The article talks about a general overview on the architectural style known as microservice. While it isn’t exactly new or niche (many of my friends who work in mobile and web development use it), it is a rather interesting change from the usual monolithic services, and I think it points towards a trend that has been going for most of the history of the software industry. I am talking about modularity and our preference for smaller units whether it is for hardware or software elements. One example of this is how companies went from giant IBM supercomputer centers over to servers and then going a bit   further distributed systems, among other things.     The authors talk about one of the so-called disadvantages of the microservice architecture being that changing interfaces or code from one service to another can be a lot more problematic than with a monolithic architecture. I, however, disagree, not so much that it can be quite difficult, but rather, that it is not a fault of
Leer más

7th Design: WarGames

It has been a long time since I have seen a movie from the 80’s. I had forgotten how corny they can be, not that it is a bad thing, and it is just that they are not as common as they used to be. I really liked the film; it made me laugh with all the ridiculous situations and all the liberties it takes when David hacks into stuff and gets out of situations at the nick of time. For the most part, it showcases what was a very serious topic (the Cold War) as a parody of itself, with chubby militarymen, threats about launching nukes at the slightest provocation and a paranoid government that would even suspect a 16 year old of Soviet espionage just because he has low grades but he is smart. There are, however, some plot points that I just could not get out of my head while watching the movie. First of all, I do not think that Joshua’s nature when David plays a game with him is justified or fully explained. At the beginning, one of the main WOPR engineers tells the spokesperson from
Leer más

11th module: Metaprogramming

While metaprogramming was a topic from the Programming Languages course that was somewhat covered, at least for my group in Semestre I, this article is easy to understand and shows the effectiveness   of this kind of practices that are as old as Lisp itself. Through simple examples I was able to understand the principles and motivations, as well as simple, although strange looking examples. I think metaprogramming deals with a very natural desire for all humans, which is to make things easier through automation and we reached that point in programming quite some time ago, through several generations of languages, paradigms and pattern designs. Maybe I find the examples strange because of the use of Ruby. While I’ve the pleasure of working with this programming language throughout this semester, I just can’t seem to get myself comfortable with all of its “peculiarities”, like its use of loops or just how easy it can insert new code anywhere through class extension. In the case o
Leer más