3 ms·
You should make sure they've actually stayed around in their companies a few years to see how it actually behaves. I've seen a bunch of architects that regularl
by rb808 10y ago
You should make sure they've actually stayed around in their companies a few years to see how it actually behaves. I've seen a bunch of architects that regularly move on to the next hot project, before the old one is properly completed. The architect never sees all the problems that come from their grand ideas so they dont get to learn what is practical. There is a big difference between architects that know all the hottest tech and buzzwords, and an architect that can deliver a reliable and maintainable platform.
- alistairSH 10y agoI wish I could triple up-vote this. I've worked with a few architects who were great at envisioning fantastic, pure systems that looked great on paper. But, were nearly useless at actually building these systems and making them work in the real world. That might be ok if the role is a pure R&D role, where they're "playing around" with the latest technology and ideas. We have some of those positions at my current employer. But, it's not very good for an architect who will be embedded with a team of developers.