Add a comment

 

Re: The key difference between developer and architect roles

I do believe that the following only applies to a small number of architects and that my own experiences have been fairly disproportionate. Unfortunately it does have to be mentioned as a difference I have seen as something peculiar to some successful (work and money) architects. Generally developers that have the following traits as part of their normal personality quickly move to architecture or anything other than development. As a developer of quite a few years I have found some architects are keen to press forward with a 'vision' that is simply based on their personal (that is unprofessional) likes/dislikes and knowledge/ignorance of technical subjects with little, if any, consideration for what the client needs and can afford. When these project hit major problems causing serious delays and cost overruns these architects are quick to wash their hands of responsibility leaving the developers to fix the major architectural flaws. Of course once the Developers have got it all working the architects (if they haven't moved on to another victim) are quick to bask in the praise while blaming any problems as 'development' issues. Essential some architects are the most arrogant egotistical individuals in the IT industry with their primary skills being socio-political manipulation. This isn't to say they are not very smart and reasonably knowledgeable they just work for them-self with only fated regard for the business client, the project success, and others working on the project.

Re: The key difference between developer and architect roles


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).