I have friends that are Software Architects, many are quite good, but to be honest, I’ve never been much for the title.
It looks fancy on a resume but it connotes that one is only focussed on architecture and not on coding.
I.e., focussed on the thinking and not the doing.
I’ve always held the belief that writing code is the only way you get better at design and architecture, you get better from the doing of it, not the designing of it. And with that said, if we are all thinking and doing we are all doing Software Architecture. The Architects that do coding and designing are the best ones because they are keeping their hands dirty, laying the bricks that they designed out.
It seems a bit like a term we borrowed from the construction industry that sounded really cool and made really great developers sound even greater?
If I had to pick a term I’d want to bring over, I’d be a Mason – a Software Mason – because people would know what I’m doing, I’m laying the foundation with my code, I’m building security around the important parts of our products, I’m building.