Ask HN: Advice for Fixing Bugs Correctly

I want to give something to my team[0] to encourage good practices when fixing bugs. People here have a bad habit of slapping an if statement or null check where it'll fix the immediate problem, without going further. So I'm looking for something that gives details about getting to the root cause, checking that there's adequate logging/informative error messages, etc. I can try to put something together myself, but I was hoping there are good resources out there that will do a better job than I can. [0] By "my team", I really mean about 20+ people I work with. We all work on the same product, but I'm not working with most of them at a level of detail where I can give hands on advice.