Naming conventions and code maintenance

Dealing with other peoples code came up in a thread today and I posted the following link, i remember reading it ages ago and have just re-read it. Is is one of the funniest things I've read re coding and an epic masterpiece in its own right. Followed properly you can guarantee you'll never be out of work!

I can't decide which is a better tip

1. Misleading names
   
   Make sure that every method does a little bit more (or less) than its name suggests. As a simple example, a method named isValid(x)should as a side effect convert x to binary and store the result in a database.

1. or
   

1. Choose variable names with irrelevant emotional connotation. e.g.:
   • marypoppins = (superman + starship) / god;

1. • http://thc.org/root/phun/unmaintain.html