Who needs an architect?

 

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 week’s reading every program has an architecture, therefore I had already designed architectures before yet I would not considered myself an architect as my programs have neither to experience fast changing requirements, have not experienced an unexpected increase in users, neither have been used for long periods of time, nor had to be maintained. They haven’t been tested in any of those ways and I am sure some of them would not be able to handle those tests, I know I lack experience, but in the future when I am able to do more robust code would that automatically make an architect or when do you know that someone is ready to make those hard design decisions.

I certainly like more the idea of having an Architectus Oryzus.

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