Re:Behaviours to avoid in a software architecture role
by AnHonestComment on Tuesday February 02, 2021 @02:00PM
(#26005067)
That’s something Amazon does well:
Principal engineers are expected to give talks about their experience, which are heavily attended in person and widely shared.
It’s not perfect, but it’s less abstract when one or two concepts at a time, they explain why those truism through their personal experience.
“Earn Trust” is a truism — but being able to search for talks by the keyword “earn trust” where a high level engineer discusses different situations from their career and how they handled them is useful.
When we down near the bottom hear "lead by example", it's facile to find the nearly useless obvious veneer to it, but if we could attach the original odyssey that led that engineer to tell their story ... we might agree with the lesson. But retellings upon retellings compress, simplify and gloss the original story into a cliche.
Each thing in this list sounds obvious, but if one can picture the opposite of the advice to be false, that reflection might actually lead an individual to growth.