Tim O'Brian reminds us in Creative Class Naming to add some flair to the namespaces that refer to our in-code data and actions. I have used this technique on many occasions, especially for ideas which may be dificult to explain (or to remember!). By way of O'Reilly Dev Blogs.

You may not think that your company's fancy e-commerce system can afford to have an object named Bouncer, but I urge you to reconsider. Bouncer communicates the idea better that AuthenticationEnforcementObject or ServletSecurityFilter. Source

Then there is syntactic sugar. Our friends =~ and && may not have a lot of flair, but help reduce the caffeine intake required to maintain a developer's interest in the task at hand. They add a lot of expressiveness to the code, not to mention compactness.

Let's invent some new characters.

Perl 6 has just about exhausted every combination of non-alpha characters, yet perl programmers want more. During one particularly long afternoon at Java, I was thinking about how unicode could be used to create new symbolic representations of the oft-used functions and classes in perl. Ok, I admit it. I was fantasizing about perl. It gets worse.

In text editors such as gvim, and instance of DBI could look like a stack of pancakes. The foreach would be represented by a loopy arrow. CGI, a spider web. XML::DOM, a who knows what. WebObjects Builder expresses this concept a bit in the page editor. This wacky, programmers-only character set could lead to quite an interesting keyboard (as if the shift key weren't enough trouble for some people).