DEV Community

Discussion on: If it works ... don't touch it?

nbageek profile image
Patrick Minton

You've set up a straw man here. The question isn't really "Should I touch it?", it's "Should I touch THAT?"

Presumably there is some other feature/bug/thing that you could touch (if there isn't, the company has bigger problems). And any time you touch any piece of code, it's an opportunity cost, because there is some OTHER piece of code that you could touch instead.

Whether you are working for yourself or your client, you should work on the thing that has maximum value.