http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660You may find this interesting [jkarlsson.com/.../the-locality-of-code-changes/](http://jkarlsson.com/blog/2009/06/24/the-locality-of-code-changes/)http://ayende.com/4212/areas-of-pain-vs-frequency-of-change#comment2http://ayende.com/4212/areas-of-pain-vs-frequency-of-change#comment2Sun, 27 Sep 2009 07:56:18 GMTYou know, there's something to be said for leaving code that's working in production untouched. Not every small change requires a massive rewrite of all the code around it. Every new line of code carries the potential for bugs. If it's time-tested and not often in need of maintenance, the only thing necessary to change may be a few comments here and there as you re-discover thought processes. You may have to hold your nose while you do it, but being a good developer isn't about rewriting everything you touch. Good for you for advocating sanity, even when it flies in the face of most developers' natural inclinations. http://ayende.com/4212/areas-of-pain-vs-frequency-of-change#comment1http://ayende.com/4212/areas-of-pain-vs-frequency-of-change#comment1Sat, 26 Sep 2009 11:58:06 GMT