As programmers, we often take incredible pride in our skills and hold very strong opinions about what is 'good' code and 'bad' code.At any given point in our careers, we've probably had some legacy system dropped in our laps, and thought 'My god, this code sucks!' because it didn't fit into our notion of what good code should be, despite the fact that it may have well been perfectly functional, maintainable code.How do you prepare yourself mentally when trying to get your head around another programmer's work? 
How do you overcome your own coding biases when handed legacy code?
experience;development process;code quality;coding standards