Voting at DZone is super easy, but you aren't logged in. Login and vote now.
By cohagen69
via codingthearchitecture.com
Published: Feb 12 2008 / 03:29
At our last user group, we asked people what they thought the key difference between the developer and architect roles was. Vision and "seeing the bigger picture" are the most common themes, although responsibility and leadership also feature heavily.
Comments
nightwind replied ago:
I'm against the whole "architect" vs. "developer" thing. Having an architect sitting in an ivory tower dreaming up perfect abstractions while to developers in the trenches have to deal with the latest uber-slow database queries and limited hardware is outright dangerous to any project. Ideally you have a part-time architect that is in close contact to his fellow developers. He will uphold the vision, enforce coherence and identify bottlenecks, while at the same time keeping an eye on the technical realities and the everyday challenges. Being a senior developer in his heart he will assist with code style and technical difficulties and will be respected by his (programming) fellows. He is aware all abstractions are leaky, and that sometimes - but not too often - underlying technical/framework/development issues will have an impact on the design model, and quickly admitting design deficiencies he will adjust his model to match reality.
Well at least I'm trying here ;)
Voters For This Link (11)
Voters Against This Link (1)