Five Reasons Software Developers Hate Software Architects

The nice folks over at DZone were kind enough to run an article I wrote today entitled “Five Reasons Software Developers Hate Software Architects“.  Here’s how it begins:

I remember it well.

In 2005, after twelve years as a developer and project lead inside HP IT, I agreed to a promotion that gave me the swanky sounding title of “HP.com Chief Architect”. I went to a friend of mine who I’d done a lot of both Java and .NET development with to tell him my good news, and what was his reaction? He immediately began to hum the Imperial March from The Empire Strikes Back and congratulated me on joining the software engineering dark side. “You’re one of them now,” he teased with a nod and a knowing smile.

For the rest, head on over to DZone.  If you like what you see, a bump using the Digg-like voting system they have over at DZone would be a huge help to get this seen by a wider audience.

Advertisements

Tags: , ,

3 Responses to “Five Reasons Software Developers Hate Software Architects”

  1. Apu Shah Says:

    Check out http://97-things.near-time.net/wiki

    There are alot more tips there for architects that are invaluable.

  2. Josh Says:

    I think you need to make a distinction between a software architect and an enterprise architect. You are really mixing a lot of jobs up here…

    A tech lead usually goes to the meetings, but still codes on the project.

    A software architect designs the top level structure of the project, but still codes on the project.

    An enterprise architect uses word and visio more than an IDE.

    Usually the tech lead and software architect are combined roles. The enterprise architect role, however, usually is, and should be completely separate. Their job is to architect multiple projects to work together, but their use of technology is from a very high aspect, and there is no code involved.

    Some of your points work a lot better in the enterprise architect realm than in the software architect realm (losing touch with tech, delegating, taking credit).

  3. petecj2 Says:

    @Josh – good points all. Given that different companies define things differently, I have only my own experience to go by. I attempted to define what I meant by “architect”, but as you point out, that definition can be an entire conversation with no right answers.

    I would absolutely agree that the problems I described are worse the higher you go up. Using your definitions, they are definitely more prevalent for enterprise architects than for software architects.

    —Pete

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: