Home > Musings, Team Work > Gross Generalizations: Software Evangelists, Rock Star Developers, Senior Developers, and Software Architects

Gross Generalizations: Software Evangelists, Rock Star Developers, Senior Developers, and Software Architects

July 13th, 2008

Generalization like rumors usually have some truth to them _ at some point, someone formed a thought around a frequently observed piece of truth and… Viola! A generalization was born (or maybe a rumor). Generalizations are incorrect for every single possible case (the exceptions), but there is truth to them.

That’s my disclaimer; now let’s have fun with generalizations.

The Software Evangelist

The epitome of an Evangelist can be observed on Sunday morning TV:

SHEBBA-WABBA-MULLA-MONEY-POWER-BOOYACKA-POW-BOW!!!!

A congregation frying like bacon on the floor, 800 numbers requesting money seared into your TV set, and an Evangelist at the helm orchestrating the show.

Evangelists are a great source of inspiration, excellent communicators, and great leaders. However, they often present a one sided biased opinion, a narrow focus, and can be driven by ulterior motives (money, power, viewership, readership, etc).  Listen to any Evangelists with a grain of salt.

Rock Star Developers

Rock Stars are on MTV, and featured in tabloids – they live hard and die young. 

The lyrics of Great Big White describe the life of a rock star:

Well I’m a wasted rock ranger
I live the life of danger
On the road to find a higher high
The music of wild rock will get me by

Some companies seek out “Rock Star Developers”, here’s an excerpt from an email I received:

are you a Rock Star? I have an opportunity for a rock star … I am reaching out to you in the hopes that you might the star I and the client are looking for!

So, what is a Rock Star Developer? My perception is a: narcissistic, self-centered, prima donna _ someone who doesn’t work well in a team, doesn’t listen, does whatever they want, and lacks dependability. Hiring a Rock Star Developer probably isn’t recommended – unless your organization has a liberal guitar smashing policy, doesn’t mind drunken belligerency, and is run by a one man show.

Senior Developers

Everyone wants a Senior Developer, but occasionally these developers are more senior than developers, and certainly not senior developers _ often the developer’s age (not experience) determines their title. Studies have shown that a developer with 2 years experience can perform at the same level as a developer with decades of experience. Still some Senior Developers have an unexplainable need to let the world know of their seniority through email signatures, resumes, business cards, LinkedIn profiles, and so on.

If you work for 10 years, do you get 10 years of experience or do you get 1 year of experience 10 times? You have to reflect on your activities to get true experience. If you make learning a continuous commitment, you’ll get experience. If you don’t, you won’t, no matter how many years you have under your belt. – Steve McConnell, Code Complete 2nd Edition

Software Architects

Software Architects can be glorified Senior Developers – an architect might be a developer who is senior (like a curmudgeon with a walker) that needed a new title.

Thoughts on generalizations:

There are two sides to these generalizations, the people who claim to be, and the people who are. The people who claim that they’re a Senior Developer are usually impostors, whereas the person who is a Senior Developer is collectively regarded as one by their peers.

Generalizations (like metaphors) are communication mechanisms, sure, there are edge cases and exceptions. Occasionally I encounter aversions to generalizations. Responses like: “Hey that’s not completely true, X,Y,Z disproves that”, or “Naw… that’s just incorrect” seem to be made when we forget that we’re just using generalizations.

What generalizations stick out in your mind?

Author: Adam Kahtava Categories: Musings, Team Work Tags:
  1. July 14th, 2008 at 06:14 | #1

    The generalizations you make point out the meta-generalization that software development isn’t a meritocracy when it should be. The developer who is generally regarded by his peers as a senior developer, but paid as an intermediate, is not a happy senior developer. Especially if his direct reports are the authentic versions of the developers higher up the chain.

  2. Adam Kahtava
    July 16th, 2008 at 06:14 | #2

    @Daniel,

    I couldn’t agree with you more.

    It’s unfortunate that many large companies try to impose a structured hierarchy of seniority on their employees. In the knowledge worker / IT field an alternate approach has to be taken. Employees need to be rewarded for their ongoing professional development efforts and passions – or they need to move into the contracting world. :)

  3. July 17th, 2008 at 06:15 | #3

    I loved your description of the Software Evangelist. However, I hope that certain "evangelists" don’t come across this way, even on their worst days! :)

  1. No trackbacks yet.