Skip to main content

Why is an architect?

 




This week's (very short) article, Who Needs an Architect?, Martin Fowler explains to us the different definitions of architects that exist in the software world. The first and most common definition, which Fowler disagrees with, says that an architect is (s)he who helps identify what the most important parts of a project are, in order to give it structure. However, it is also mentioned that these parts are usually the most important because they are the hardest to change, so an architect's job should also include reducing the amount of these parts. Following the logic, by this definition, an architect's job is to reduce the amount of architecture. 

The second proposed definition, which I also think I agree with, is that an architect's role is more like a guide's. His purpose is to help the team become better by using his expertise, and communicating with as much of the team as possible in order to remove their blocks. I think the word architect still fulfills this definition. However, the role isn't to design the product, it's to, in a way, design the right team to work on that product.

I think the reason I agree with the second definition is because just like Thanos, change is inevitable. It's even mentioned in the article: flexible components are a little more complex than their non-flexible counterparts, but as a whole, a non-flexible system can be just as complex. That being said, since it's impossible to prevent change, you might as well have a solid team that will be able to tackle it. 

With that said, I think I agree with the idea that a "software architect", as is defined today, meaning someone who designs a system from the beginning in order for it to be more robust, is not needed in most cases. What is needed, is someone who is able to manage a team, is willing to teach, and knows how everything should work together, and what to do when it doesn't. We could change the definition and keep using the architect title, or come up with a new titleto cover this issue, either is fine by me, but I agree with the idea that an architect by today's terms isn't the most useful addition for most projects.

Comments

Popular posts from this blog

Is Design Dead?

 This week, we had to read Is Design Dead? by Martin Fowler. Just by reading the title, the thought of agile methodologies popped into my head, since they do involve design, just not as much as we're accustomed to. And not too surprisingly, Fowler reached a similar conclusion: design is NOT dead, it has just evolved along with us to keep up with today's standards.  Before, design was used to make sure that you knew everything you needed to get done, and it let you find any flaws in your plan beforehand. It was meant as an all-encapsulating process that all future code will be based on. Today, it has maintained its role as a guide, as to not make the developer feel totally lost, but with today's fast-paced work environment and ever-changing requirements, with the help of methodologies such as Extreme Programming, it has evolved to become more dynamic and easier to change.  For my personal opinion, I've had experiences (both academic and professional) where a bit of desig...

Man on the Moon

The third episode of Moon Machines, titled  Navigation Computer  tells us all about the process of building the Apollo Guidance Computer. It amazes me the amount of work that goes into a project of this size, and it has always surprised me how many people don't care about space travel, or even the amount of people who, despite seeing all the people involved and all the hard work, still deny the moon landing ever happened.  I also found it really interesting how seemingly unorganized MIT's software team was while working on this project. This isn't meant as a jab at them, but the fact that one of today's most prestigious institutions didn't have a well-defined plan speaks of how much project management and software development in general have evolved in such little time.  However, it's also funny to see how little things have changed in that regard, in the sense that even today, the amount of work that goes into developing software is grossly underestimated (even...