I picked up robert martins "Clean Code". It reads beautifully as if it was all common sense. Basically if you had to put into words everything you ever saw as 'clean code' it would look alot like the first chapter of this book, but then Bob goes on to show you exactly what those words mean with code samples and in depth reasoning why code craftsmanship will make your daily programming life easier and more enjoyable.

Bob makes us remember some of the ordinary things like making sure to use short methods (and then make them shorter than that!) and take time to refactor bad code to some clean code instead of adding comments.

He talks about the reasons to use procedural code with data objects and then OO code but why to stay away from "Hybrids" of the two.

I read half the book in a single setting because it was just so amazing to read some of the practices I'd love to be able to replace our existing legacy code with.

Fowler tells us in 'refactoring' to be sure to have automated unit tests before we do any refactoring, so make sure you pick up Michael Feathers' book on Legacy Code to know just how to get your legacy code under test before taking on any 'clean code' practices with existing code.