Slobodan Dan
Full stack developer, manager, writer, with over a decade of experience in the IT industry, including large code-bases, enterprise scale applications, team-leading, Lean, Agile and SCRUM management frameworks and software architecture.
Details...
When the titles in the IT industry no longer represent seniority or knowledge, they become vanity titles to be displayed to recruiters and customers.
The true architect is not a title. It is a path I follow on my way to becoming a good software architect.
Uncle Bob's definition of the goal of the software architect is minimization of manpower in all phases of development, deployment, and maintenance.
— Uncle Bob Martin (@unclebobmartin) September 27, 2020
Similarly, he argues that the goal of software design is to minimize the effort required in order to meet the needs of the customer. In other words, if the software is easy to change, the design is good, and vice versa.
The authors of Team Topologies further argue that due to Conway's Law organization design requires technical expertize. To quote Allan Kelly, as the authors did in the book: "...someone who claims to be an Architect needs both technical and social skills, and they need to have a say in organizational structures and personnel issues, i.e. they need to be a manager too."
These and similar ideas from some of the amazing books I read led me to define the five tenets of the true architect.