Summary
Being an architect is not something you simply read about. You can’t memorize 10 rules and then be ready to change the world. Most of the time, it is a tedious path with many challenges.
In this chapter, we learned that as an architect, you need to make your influence felt in the team and collaborate with the people that work on the same product as you do. As a role that influences a wide range of stakeholders, you need to learn to communicate effectively and manage the information you get from each to make the best decisions for the product.
Holding a leadership position within the technical field does not spare us from being there for our team, raising our colleagues by giving feedback or mentoring. Maybe one of the ideas we need to get out of our systems is that while you are an engineer or a tech person, you don’t need to collaborate or have expertise in working with people. Great teams deliver great products. You can have a group of superstars owning...
