Computer Programmer Inflation

I was thinking the other day about the changes over the years in what we call people who write computer programs. Back in the day, we called these folks computer programmers. A rather fitting title, one would suppose, for a person who programs computers. But one would suppose wrong.

Shortly after computer programmer became the "official" title, someone, somewhere, somehow decided that it wasn't enough. After all, computer programmers do more then program, they analyze a problem and then write a program. They should, therefore, be titled programmer/analysts. One would suppose that such analysis is an implicit part of the job, much like how writers need to think about something before they actually write it. But one would suppose wrong.

Unlike the computer programmer title, programmer/analyst seemed to stick around for quite a while. In fact, it was only fairly recently that we all became software developers (or, developers for short). The change this time around was all about image; you gotta admit how much sexier developer sounds over programmer. Certainly one would suppose it's pretty hard to "sex up" an industry whose Steves out number its women (see the Steve Rule). But one would suppose wrong.

Believe it or not, developer is on its way out and we're in the middle of yet another title change. If you think about it, the problem with developer is that, if any one asked what a "developer" is, you'd have to expand it to software developer. Software == Computers == Programming == Nerdy. We can't have that!

This is where the title solution developer comes in. We're the guys who you call when you have a problem. Doesn't matter what the problem is, we will develop a solution. Heck, we can even develop solutions (by programming a computer) for problems that don't exist. We're that good.

But where do we go from here? First, we need to reach the maximum level of ambiguity possible. I'm not an expert at coming up with job titles, but I suspect solution specialist is a step in the right direction. Of course, once we've gone all the way to one side, the only place we can really go is to other extreme: a way more overblown/descriptive/nerdy sounding name than needed. When solution specialist (or whatever) expires, I really hope the replacement will end with -ologist. I would really like to be an -ologist of some sort. You know you'd like it, too.

Published Friday, April 29, 2005 2:17 PM by Alex Papadimoulis

Comments

Friday, April 29, 2005 2:53 PM by Mike

# re: Computer Programmer Inflation

Solutionologist
Friday, April 29, 2005 3:03 PM by Jason Mauss

# re: Computer Programmer Inflation

I've talked with colleagues before about just renaming everyone's job title to 'Problem Solver' since that's really the bottom line of what you do.

Problem Solverologist? meh.
Friday, April 29, 2005 3:32 PM by David Cumps

# re: Computer Programmer Inflation

Art direction, we're designers :)

So, add 'Designer' :)
Friday, April 29, 2005 3:49 PM by Steve Hall

# re: Computer Programmer Inflation

In some shops, titles have de-evolved into "Shinola Shoveler"...

Personally, I'd like to see an end to this move towards "sumtin' Engineer" titles, and instead get the word "craft" or "art" in there somehow (as a tribute to our revered holy work, TAOCP by Don Knuth). "Problem Crafter"? "Crafty Problem Solver"? "Shifty Solution Crafter"?

In my current company, we've actually got some folks with the title "Computer Scientist", which is pretty ambiguous. Whenever I find out someone's gotten a "sideways promotion" to "Computer Scientist" I always ask them "Exactly what DOES a C.S. DO? What did YOU DO to deserve this? Where a white lab-coat into work a few times?" Invariably, it always boils down to the lame excuse that they got the title due to getting their name on a patent. (Afterall, engineers NEVER get their names on patents, only scientists, right?)

Obviously, more ambiguity can be had with a combination of the above: "Computer Science Craftsman" or "Software Craftsman" or "Software Solution Artist".

Now if anyone were to approach Knuth and suggest he change the TAOCP title to replace the "Programming" in the title with any of the aforementioned tags, I heartily support the spillage of blood! (I'll supply him the light saber...) ((Can you imagine a title of "The Art of Computer Solutioning"?))
Friday, April 29, 2005 4:23 PM by Chris

# re: Computer Programmer Inflation

I just got told that I missed out on a job because they expected me to be an analyst/programmer instead of a programmer after 7 years in the industry. We have 7 programmers where I work and 0 analyst/programmers but we all do analysis.
Friday, April 29, 2005 4:25 PM by uber1024

# re: Computer Programmer Inflation

I don't much care what my title is. It's the paycheck that's important.
Tuesday, May 03, 2005 7:27 PM by TrackBack

# Comicality Inflation

Wednesday, May 04, 2005 4:28 AM by TrackBack

# Computer Programmer Inflation

Alex Papadimoulis (he of DailyWTF fame) has posted a couple of v.funny articles recently:

Computer...
Wednesday, May 04, 2005 8:06 AM by TrackBack

# Titel Inflation

Griner post
Thursday, May 05, 2005 8:08 PM by Cindi

# re: Computer Programmer Inflation

Industry analysts have encouraged inflation in their research. Read about the real facts at http://blogs.ittoolbox.com/eai/leadership
Wednesday, May 11, 2005 11:34 AM by Peter

# re: Computer Programmer Inflation

Fred Brooks commented on the title "computer scientist" years ago.

http://www.cs.unc.edu/~brooks/Toolsmith-CACM.pdf
Tuesday, May 17, 2005 4:07 PM by Rob Garrett

# re: Computer Programmer Inflation

I have to disagree with your post, although it does make some convincing points. My understanding of programmer vs. developer label came about because of the shift in responsibility of each job role.

Back in the 70's and 80's we referred to people who punched instruction code into computers as "programmers.” Programmers had no role in the design of software, nor did they facilitate the requests of the client, this was the role of the system analyst. Typically, programmers were paid far less than analysts and were only given requirements to implement for given projects.

Fast forward to today. The industry is now flooded with individuals who posses Computer Science and Software Engineering qualifications. The fact that software development is now considered an "engineering" principle is testament to the fact that software creation involves much more than just coding. Thus, in my mind, the "programmer" is dead and we have a new title – the “developer.”

Developers are expected to know object oriented programming, object oriented design, and process methodologies (RUP, XP etc). It is not uncommon to see a developer in design meetings, code review meetings and for them to play a large part in creating test cases for developed software. Programmers, true programmers, are the people who, in my mind, are only responsible for writing software code and no more. Some employers still distinguish differences between programmers and developers. Many of the legacy UNIX and mainframe jobs involve programmers to keep these systems running on a day-to-day basis.

I do concur with one point that you make, and that is the one about this being a debate about image. Sadly, the market is awash with individuals that claim that they can develop good software; but in reality do a bad job. Therefore, image is everything when standing above the crowd as one of the elite. The “developer” title has a certain grandeur that is synonymous with excellence in the engineering field, whereas “programmer” does not.

Some may agree with you in that "programmer" and "developer" are titles for the same role, but ask 9 out of 10 programmers/developers what they would rather be referred to, and they will likely tell you "developer.”

Tuesday, May 17, 2005 4:17 PM by Alex Papadimoulis

# re: Computer Programmer Inflation

> Back in the 70's and 80's we referred to
> people who punched instruction code into
> computers as "programmers.”

Actually they were called punchcard girls. Though their actual job title was coder.

> Programmers had no role in the design of
> software, nor did they facilitate the
> requests of the client, this was the role of > the system analyst.

Go back and read books from the 70's and 80's, specifically M.A. Jackson's Principles of Program Design to get an idea of how the terminology and roles were like. Job roles haven't changed since then. Only titles.

Programer/Analyst = Developer
System Analysts = Business Analyst
System Designer = Architect

Experience and Skill correlate to rank (Programmer I, II ... VI). A "1" is fresh outa college, a "3" knows a bit more, a "6" is a total guru.

Same roles. Some differences. BS Semantics.
Friday, May 20, 2005 1:24 PM by Bob, London

# re: Computer Programmer Inflation

This guy started before most of us were born.
He said back then they were called 'computers'

Weinberg explained, "the title software developer did not exist; the word software did not exist."


http://www.devx.com/enterprise/Article/27631

Tuesday, June 20, 2006 9:21 AM by Arni, Reykjavik

# re: Computer Programmer Inflation

Peter Naur coined the term datalogy which is heavily used in Scandinavia -- e.g., the Danish word for computer science is datalogi. Thus computer scientists/(software) developers/programmers/whatever could also title themselves as datalogists.

# ChrisBellini.com » Blog Archive » i would’ve been a great ninja

Tuesday, July 18, 2006 8:43 AM by arjoy

# re: Computer Programmer Inflation

wd

Leave a Comment

(required) 
(required) 
(optional)
(required)