Software principles that last don't come from architects in glass offices. They come from practitioners who noticed what kept working.
These principles arose from doing the work. They did not descend from on high from those far removed from the work.
This, I feel, is the most fundamental truth about doing work: those without dirty hands are wrong. Doing something makes you right.
Pretty much every IT architect I've worked with, has had very faded and unrealistic technical knowledge.
That is often a significant counterpoint to the team. Where they frequently have more 'upto date' knowledge but lack the experience to understand past endeavours.
I think the closest analogue in IT to building architects are actually product managers.
And sadly a lot of IT architects only seem to exist because companies still struggle with the very flat career hierarchy of IT. What they really need to learn is how to recognise and reward good people working at the metaphorical coal face.
But 20 years in, I'm yet to find a company whom would just recognise someone for being a bloody good engineer and nothing more.
