My last post covered some of the issues I’ve had to troubleshoot with variables lately, but didn’t cover the strategy for doing so.
When troubleshooting UI Policies, often the best thing to do is simply to deactivate all of the policies and then turn them on one at a time until you see the behavior that you’re trying to stop.
Sometimes, depending on what you’re seeing, turning them off one at a time until you see a particular behavior start or stop is the way to go.
Really, when bug hunting, it’s always best to look for strategies that allow you to pin the bug down to a specific section of code. Generally, if you don’t find the bug right away, then it relates to something that you either don’t understand well, or which you understand incorrectly. By eliminating big chunks of code, you reduce what you have to look at to something that is much more manageable.
That drastically improves your odds of figuring out what is driving the bug. It’s a strategy that I’ve learned, forgotten, and then relearned again. I tend to use it instinctively until I run into a new tool, application, or technology. Then, for some reason, I seem to forget to bring the principles with me that worked so well with previous tools and technologies.
A big hat tip to my coworkers Kim and Tatiana for reminding me the right way to go about debugging something. Hopefully it sticks for the next novel situation I find myself in.