Who needs an architect?

This week's article was a little short, but there are many ideas that can I can come up with. Basically, what the article was trying to do was to show the importance of architects, especially software architects. We have come a long way on our major of comptuer science, and it is time to start thinking big. Most of the projects we have worked in school are small projects which almost all of them consisted on a set of approximately seven classes, a database and a web server. Maybe for these projects you do not need a special person to check or validate the whole system. 

But as the world progresses, organizations require bigger and more complex information systems and applications. Many of them involve the use of applications interacting with each other. Now, with that being said a special role or person is needed for a whole system to work. This includes knowing how a system interacts with a database, an application programming interface (APIs), with other classes, operating systems, etc. Also, the needs and objectives of the organizations constantly change, which requires the development team constant changes to the software. 

Who needs architects? Nowadays almost any field needs an "architect" who knows how to assemble the correct pieces. One of my professional goals is to in one point of my life be an architect, I do not mind if software architect or even cloud architect, at some point in my life I want to design, work and do high level activites which need abstraction. 

Concluding this blog, I hope (I think almost every blog I have written for this assignment) that in the software design and architecture course, we get to know important methodologies used in modern day organizations. Being an specialist in something requires hard work, but being an architect needs beside the knowledge, cooperation with your team, having communication skills, and, know what the goal is.