The misunderstandings about software architecture start with the name. What our architects really do is much closer to cleaning up ghettos than designing high-rise buildings.

After 20 years as a developer, I finally acquiesced and accepted a 18-month role as a solution architect. This talk is a collection of lessons learned, such as:

Architecture is the wrong metaphor.
Work in thin, complete cycles.
You only realise the cost when you follow the rules yourself.
Build non-blocking collaboration systems.
You are there to help.
Let them fail.
Get and give feedback.
Be onsite.
You are also a salesman.
And you thought you could now tell everyone what to do... 🤔

I'll explain the practical advice behind these phrases. This should majorly help those trying to work as, or interact with, software architects and technical leaders.