Thanks for your thoughtful comment Mike. #1 is a good idea. Defining 'good code' is hard, but I know bad code when I read it, and certainly code with a philoso

Thanks for your thoughtful comment Mike. #1 is a good idea. Defining 'good code' is hard, but I know bad code when I read it, and certainly code with a philosophy that I disagree with! I am definitely going to have to learn TDD after all the comments in this thread. Thanks for the recommendation of books, esp Feathers - a lot of my work is with legacy code. Thanks again!