Who need an architect?

This blog is dedicated to article "Who needs an arhitect?" by Martin Fowler. The focus of this article is mainly to define what architecture and an architect really means and what do they mean in software engineering.

What is architecture?
As the article states, this is one of the biggest and hardest concepts to explain, that's why the author only states that architecture is about the important stuff, (whatever that is). That's right, no on actually knows what architecture is, but I can give you a nice and better definition that is later specified:

"In most successful software projects, the expert developers working on that project have a shared understanding of the system design. This shared understanding is called ‘architecture.’"

Why is an architect important?
I consider most importance in architecture comes from experience. When you work in really large proyjects or systems, you can notice it starts to become uncontrollable and messy really fast. This is no problem to a good software architect since he has the experience to know where to put things around, how many microservices or tomcats are needed, load balancers, database selections, etc. An architect is a guide of the project that generally has worked with multiple architectures and systems and knows the best way to go through.