I have the opposite position. I feel that meaningless (especially if there can be a subtle fun part) names are the only valid thing for internal projects. I've worked on so many that A) are difficult to impossible to name "descriptively" and B) over time, shifted away from their original purpose.

Meaning the long and awkward "descriptive" name becomes a lie over time. But the "code" name has no meaning, so it doesn't become wrong, you just need to maybe re-learn the meaning of the otherwise meaningless word.

See also: How do you descriptively describe the replacement/rewrite that does the exact same thing, but exists in some form while the other one does, also?