Non-common architect


In this reading, written by Martin Fowler, entitled "Who Needs an Architect?", an attempt is made to explain, in a terrible but useful way, what an architect is, specifically, a software architect. In addition, the author tries to define what is a software architect through mental exercises, or some attempt with linguistic absurdities.

On the other hand, the author talks about his epistolary exchanges with other characters in the area of information technology, in which the true definition of what a software architect is, or something similar, is discussed. Much of the text is devoted to this.

Finally, the author exposes the expert developers, saying that only they know the true definition of what makes a component important, and so the author continues to expose the industry, in search of a true definition for software architect.

Comentarios

Publicar un comentario

Entradas populares de este blog

4 + 1 = 5?

Today I'll talk about the the 4+1 view model, which basically consists in four sections and an extra section which is the +1 part, that allows us to make better software architecture. I will explain these sections in order to understand better this concept. This fourth section is the logical view, the development view, the process view and the physical view. The extra one is called: Use-Case View/Scenarios. The Logical view talks about class diagrams, communication diagram, sequence diagram, state machine diagram, and an object diagram. All of these in order to obtain an object model, what components will be made and how will the behave. The development view is about, component diagram and package diagram, all to the make the organization of the assets during the development work, in other words, which belongs to what. The process view is about concurrency and synchronized aspects. These mean activity diagram and ...
Leer más

WarGames

Ever since I read through the part of Ready Player One where the movie 'War Games' appears I've been thinking that we should watch it in class one day instead of the other media that we usually do watch (Silicon Valley). I even mentioned it to some of my classmates out loud. I know that watching it was probably planned in the course all along (I believ that it's in the nature of our professor to have things planned like that all along) but a tiny part of me still likes to believe that he overheard me saying it in class and thought 'you know what? yeah we should watch War Games one of these days' and so he mercifully got it and played it for us. Anyway, I really enjoyed the movie. Even though our professor warned us that the movie was old and that it showed a lot I don't quite believe it did. Not enough for that warning. Where it did, it didn't bother me at all. I think that when a movie is good like that my brain just accepts the universe i...
Leer más

SOLID Principles

Hi everyone! In this week, we'll talk about SOLID principles. So let's get to it. The first principle called "Single Responsibility Principle" is one of the easiest to understand but at the same time one of the hardest to apply. To get a class to have only one responsibility, there has to be a very good software design, but developers must also devote time to code analysis (especially those that are dedicated to maintenance). Otherwise, programmers will simply do what is faster and simpler: Add code wherever it is going to work (Apparently) what was requested by clients. The principles with which I do not agree at all are "Open / Closed Principle" and "Liskov Substitution Principle" since I believe that the base classes should have the flexibility to be modified as long as the repercussions of the modification are understood. On the other hand, I think that classes must certainly be made to be extended or replaced by functions, si...
Leer más