One of the yukky areas of code that we deal with is legacy code.  Whether it be taking old asp code and bringing it up to 3.5 asp.net, or C# code that has evolved beyond recognition, we all end up dealing with it.  My pet technique now with advent of refactoring tools like Resharper is to rename methods to reflect exactly what they do.

So - the 172 line validateUser method becomes, ValidateUserShowErrorLockedOutStatusLastLoginAndAccessPrivileges(username, password)

Why is this good?  Well, if I *can't* refactor it into smaller methods because it's all so inextricably intertwined, at the least, I'm highlighting this fact, and telling the next poor person who wanders along, just what the function does.  And when you review the code later for targets to refactor - this one suddenly sticks out - just because of the name.

My all time favourite though was...

CalculateFeeOnPortfolioForBrokerageTransactionSubscriptionAndApplyFeeToAccountAndRollFeeUpToGLAndPrintTransactionStatememtAndIfEndOfYearPrintFeeSummary()

Seriously.