The Importance of a Good Code Name

24 11 2005

Yesterday I attended a meeting with a member of a clients configuration management team. Eventually the topic of “what do you want to call your source repository” came up and we all looked at each other and blinked.

Eventually a neuron in my brain triggered and I realised that this was an opportunity to pick a code name! Several good options were put on the table but for some reason the development team leader baulked at them and opted for something mundane and boring ().

I can never understand why people choose grey names for projects, its their opportunity to put some of their personality into the project, but more importantly a good code name serves several useful purposes. A good code name:

  • is a short hand way to refering to the system.
  • is great for starting elevator pitches to executive management.
  • is a way of avoiding analysis paralysis on namespace naming.

If I have convinced you to create a code-name for your project, here are a few rules that I would stick to for .NET projects:

  • Avoid acronyms, they look like crap in namespaces.
  • Prefer a single word codename, two word tops.
  • Make it easy to search and replace in code.
  • Place names, people names and funny words make great code names.

Do you have a code name for your project? If not, make one up and just start refering to the project as that – see how quickly your co-workers catch on.


Actions

Information

5 responses to “The Importance of a Good Code Name”

24 11 2005
Deepak (00:00:00) :

Mitch,

I had a similar experience in one of the companies I worked with few years ago. This organization was embarking on a major project, and the management could not decide a name for the project. After many meetings and polls it was smartly decided to call it “Project Rose”

Of course inspired by this

“What’s in a name? That which we call a rose By any other word would smell as sweet.”

24 11 2005
Eddie de Bear (00:00:00) :

Funny you mentioned this, we had a project naming meeting earlier in the week. The name, Draper… (After Jon Draper)

28 11 2005
Kieran Jacobsen (00:00:00) :

What about sub projects, or code ports to other devices? Say Desktop app to Pocket PC? Should the name stay the same?

28 11 2005
Mitch Denny (00:00:00) :

Hi Kieran,

The project name is the name for a piece of effort, not just a piece of software. Microsoft changes their code name from version to version so i guess there would be no problem changing it for a platform change.

Then again - there are no hard rules.

14 03 2006

Leave a comment

You can use these tags : <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>