Joe McKendrick (usually spot-on) must not have gotten enough sleep last night when he states “….most developers could easily jump into the architect role.”
At least he observes that developers are smart people.
Interesting read and nice site layout. For a minute I thought you were using a competitor's blog services. :o)
It's a little hard to read, but that statement is actually attributed to "techboy_z" who is asking a question quoted from another source. (this is getting hard to read)
Personally, I like the concept of a "devarchitect". Suits me well. <grin>
The carpenter analogy is misleading. In construction, carpenters have trade-school education or learned on the job, whereas an architect has a college degree and spent years taking engineering and design courses. By contrast, in the IT field, both developers and architects have generally the same education and background.
It is my experience that at most companies, the distinction between the roles is one of title and pay grade, more than actual ability. I do, however, recognize that companies could decide to separate these roles and have different requisites for each. I think this is the exception rather than the rule.
O sea que cuando no habia arquitectos no habia casas? Y quien crees que diseño las casas de tus ancestros?
Me has desepcionado tio, adios a tu rss...
¡Hola Mike! Apesadumbrado si le ofendí. No era mi intención.
Perdone por favor mi mal español.
I'm not crazy about the analogy -- a good architect should understand carpentry but that doesn't mean that the carpenter would make good architects.
A carpenter is more like a "cook" -- while the architect is like a “chef” – the architect understands the bigger picture, while some carpenters may have the ability.
Of course I could be wrong (^_^)
Blake - I like your analogy better. I "borrowed" the carpenter analogy from some of the feedback to Joe's blog entry.