> Just Don't. Leave it the fuck alone. Reminds me of a passage from "Working Effectively With Legacy Code" by Michael Feathers. The book is about dealing with

> Just Don't. Leave it the fuck alone. Reminds me of a passage from "Working Effectively With Legacy Code" by Michael Feathers. The book is about dealing with those times when you absolutely must make changes to that old system. This is from the end of Chapter 1: It's tempting to think that we can minimize software problems by avoiding them, but, unfortunately, it always catches up with us...In poorly structured code, the move from figuring things out to making changes feels like jumping off a cliff to avoid a tiger. You hesitate and hesitate. "Am I ready to do it? Well, I guess I have to."