Worst thing I ever named anything

A friend of a friend used the names of his ex-girlfriends as variable names...

I am so gone win this one, I have so many I can't even remember those anymore, lol. Wait a second let me find some gems

1 -> pleaseDontBecomeFalse = true
2 -> flag1, flag2, flag3, flag4 till 99 (I won't say why, please don't ask me)
3 -> CONSTANTS = [88, 124, 99, 927];

dataObject

I recently named a binding type in an Angular project and it royally fucked the compiler, which gave literally nothing in the way of what the actually error was. Took me house to figure it out...

ContentProcessor. MessageReceiver. MessageSender. DataProcessor. There are so many it's hard to choose from. In my defense, I'm forced to use such names.

In the .Net world there's a naming convention of adding suffixes to classes - like FileNotFoundException which is kinda dumb IMHO.

I mean, you only use exceptions in two places: throw and catch. You know if you have throw new SomeClass() in your code, SomeClass is derived from Exception, same as if you have try {...} catch(SomeClass x) {...} - so why not just call it FileNotFound?

I'm not alone in this, there are other developers that share the same sentiment. In fact, I once read about a software engineer that got so sick of it he had all his classes add with Thingy.

Also, I once named one of my variables Yevgeni, but that was in honor of a fellow developer that got fired :-)

I like using a parent-child naming, especially in SASS. However when lots of elements are nested it can give some names that are actually not understandable at all at first glance, such as getGameDetailsRankingRowFieldNumberClasses.
It means : "A function that returns the classes of the div corresponding to the field 'number' in a 'row' of a list called 'ranking', which is located in the page 'gameDetails'."
Hence I try renaming things with short, easy names when possible. It's a little sacrifice but, when done properly, it is much useful!

iveHadEnoughJustF***ingWork()

People don't let me name things. I tend to like "easter eggs", including in things as simple as names. People don't like to have been using things for months only to have someone with a similar proclivity come on board and start sniggering. =)

Once upon a time in Ruby on Rails land, I created a model called Case.

I've had methodWhichShallNotBeNamed() and doStuff().