Recently I’ve seen a series of posts between some deep technical and some broad technical architects. It even included the disparaging of a person I find beyond reproach personally.
It was an interesting discussion.
Prior to that I spent another month living in the world of Business Architects, yay or nay.
Part of me says all of this is because we are becoming a profession. It is important (definition wise) when you become a profession to have the lines and boundaries of your profession clearly defined.
But there are other things going on here. I find it interesting that people are hung up on the concept of technical skills. What are technical skills? For that matter when you think about an architect and we think within the boundaries of skills themselves what are we really looking for?
- Organizational Dynamics
To me those are the core architect skills. The others skills around technology are lesser skills – why? Because frankly they are easier to teach someone. I have a friend who designs bridges (that go over rivers). He once told me that being off an inch cost a million dollars.
Without the four skills above – it doesn’t matter how smart the architect is, they will end up with a bridge that misses by more than an inch. The days of technology for technologies sake are over. The business is the driver as it should have been all along.