I've noticed that some software names occasionally raise an eyebrow.
I'm thinking of:
Did you ever get into trouble for using software or creating software with an odd name like these?
Server Helpdesk Issue Tracking is not a good name for..that. Just FYI.
In the "olden days" of VMS, I had a little fun with logical names. Just for the heck of it I defined one that simply pointed to "SYS$LIBRARY:" and called it "SYS$LIBERRY:" after the way most people pronounced it.
And while it's not software, we DID put the following into our official policy document for the timesharing node who's name on the network was "MERLIN", after the sections outlining the security policies that software covered (public accounts, privileges, accesses, etc):
"Physical security for MERLIN is provided by Digital's security farce"
Only one person ever caught that.
Apple would not allow me to use the word "tapeworm" in a method definition because they were worried that someone might sift through the binary file and see the symbol name.
We once made a reporting solution for a app that was originally named "Dynamic Reporting Tool" or (DRT) management was not fond of us referring to the reports as "DRT Reports". So they made us change it to "Dynamic Reporting Engine". That led to all kinds of more muffled comments about Chronic, Gin and Juice, etc etc and remains the name of the engine to this day.
I also have a small app that deals with i18n called "3CPO" (since he was protocol/translator droid. Never got in trouble for that one...then again its a tech only app.
JBoss Drools is hard as hell to argue for in corporate meetings, because nontechnical decision makers have a real hard time taking the name "Drools" seriously. "Drules" might have been a much, much, much more sound choice with the same pronunciation.
FCKeditor recently changed its name.
ScrewTurn wiki also seems to have a name acceptance problem.
I was working in a huge rush on my file system API to get it out the door before the deadline. I had no time to test or proofread my code, and unfortunately I mispelled an important function call:
creat()
I have had lots of problems with software which uses "real" words as names.
Particulary when you want to google for examples.
Say you have a problem with your curses program validating hex input. Try coming up with a google query that won't give you lots of useful hints on how to give your boss a plague of boils.
One of the many reasons to ditch curses in favour of ncurses.
I once got crap for naming a control "OHPaparazzi"; it was a user control whose only function was to switch on a web cam and take snapshots of users without giving any feedback to the user. I thought it was a fitting name given the stealth nature of its' behavior, but the chief namespace officer disagreed. He argued that Paparazzi is not an english word, so I had to change the name... :) ...the moral aspects of taking photos of users without letting them know was - oddly enough - for some reason nothing they were willing to discuss...
Oh, and in the same app/project I also implemented a user control called the 'nurse browser'. I never got in trouble for that one, and I don't think anyone else did either... ...but certainly could have... :)