The Naming of Code

Inspired by T.S. Eliot’s The Naming of Cats

The naming of software’s a difficult matter
Don’t think of your product and name code the same
You may think of course I’m as mad as a hacker
When I tell you that code must have random-ass names
Worst of all there’s the name that your sales teams use daily
Such as Wunderlist, Shadur, or Gmail, or Blaim
Such as Toodur, or Spotify, or Snapchat or Twitter
Those do well for salesmen, but for devs are a bane
You may think descriptive names to be all the sweeter
Perhaps they’d survive the renaming strain?
Such as Mapper, Cart Service, Recommender, or Greeter
All of these, functional, and seemingly sane
But I warn you these names can seed problems ahead
For if change occurs, then you’re stuck with a lie
It’s safer to stick to a name disconnected,
Unrelated to purpose, and I’ll tell you why
But first some examples to warm up our forum
Such as Munkustrap, Quaxo, or Corpicopat
Such as Bombalurina, or else Jellylorum
Names that a poet might christen his cat
Examples aside, I’ve got reason to cover,
Why make my code’s purpose so tricky to guess?
That reason is that coding teams, over and over
Mold the purpose of projects to what they fit best
When next faced with this task of initial frustration
When you need a decision to avoid future shame
I implore you: consider, with no hesitation
A thoughtless, a playful, nonsensical name
An affable laughable
F-ing unguessable
Fun and yet memorable random-ass name