Who Needs an Architect

For today’s blog i had to do a reading of an article by Martin Fowler which talks about, who needs a software architect? and most importantly, what is a Software Architect? Before reading this article I encourage you to think, What is a Software Architect for you? What is his job? Would you like to become one? You can find the article in the following URL http://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf and I highly recommend you read it, since the ideas you have about it might change after reading it as I did.

At first glance, we think of a software architect of the person who will set up the tools and environments to use during a project, thus, the people who are going to work on such project will follow as it is specified, a person who is highly experienced on topics to choose the development platform,  however an architect is not only this, it is not imperative and the software development project should be aware of this, since there will always be better ways to handle the problem, for example in a software project to develop a web page in X time of months, the software architect says to use the platform Java because he's used to it, however this might no be the best choose, for some cases the team might have more experience on another platform like Node.JS which would be better for short times of development, this way, the software architect should be aware of this and make a consensus of the platform to be used, a key-factor to remember is that a software architect should have more experience than their developers, this way to act as a "guide" to them, a software architect encourages people and improves their ability with different platforms, it's like developing their own team with skills so projects will be easier in a future, this way a software architecture is a kind of leader which will let the team do their job, and he will handle the hard stuff when needed and teach the team how was this done.

This was a great reading and I hope you like it too