Software Architect?
Hi everyone, today's blog is quite a thrilling one. I found Martin Fowler's article very interesting and with some hot takes that I wouldn't have thought about myself. We are presented with the idea that the concept of an architect and what they should do is very subjective and in a way, as he states it, a social construct of what developers think is important for the system they are going to implement. You could say that there is a lot of responsibility in the architect's hands for what the end product will look like, deciding which components are important and even essential to the main structure of the system. By this definition it kind of makes project management and software design and architecture as a single person mission. As the article says, I agree that this is too much responsiblity for what we would call a software architect. Deciding on whether or not something is to be considered important for the development process should be a collaborative effort. En