Making the case for code quality
Imagine you're working with developers who habitually write 300 line nested methods full of errors, possible errors, etc. etc. Applications regularly throw exceptions as a matter of course, and much time is spend hunting odd intermittent bugs. 

How do you go about making the case for better code and better standards? How do you make the case to developers who are used to coding in a particular style (badly) and don't see the need or benefits of change? 

I suppose as a side question, what's been your experience with working with people in this kind of a situation, and what have you done that's worked positively?

Making the case for code quality
===

Imagine you're working with developers who habitually write 300 line nested methods full of errors, possible errors, etc. etc. Applications regularly throw exceptions as a matter of course, and much time is spend hunting odd intermittent bugs. 

How do you go about making the case for better code and better standards? How do you make the case to developers who are used to coding in a particular style (badly) and don't see the need or benefits of change? 

I suppose as a side question, what's been your experience with working with people in this kind of a situation, and what have you done that's worked positively?
