Adam Culp has posted a three part series to his blog with some guidance about how to create "clean code" in your application development:

Whether we’re experienced developers or newcomers, we’ve all seen code that could/should have been done better. Many times it’s even code we ourselves wrote and revisited later for one reason or another. I, for one, have seen my share of code written by a “past me” and wondered what on earth I was thinking when I wrote that. Of course there has also been times when I was hired to fix another developers code, and it can be scary also.

There's three posts in the series:

• Part 1, Dirty Code (cause/effect)
• Part 2, Dirty Code (why we do it)
• Part 3, Dirty Code (how to spot/smell it)