My coworker and I figured out a nasty bug in our own code yesterday. It was one of those "works on my machine" situations. We ended up using some of the strategies from @b0rk@social.jvns.ca 's zine, The Pocket Guide To Debugging, https://wizardzines.com/zines/debugging-guide/. We worked together, reproduced the bug, made a minimal example, identified and answered small questions, kept a log book, and analyzed the logs (a report from running the command). Eventually we solved it, and it was caused by a flawed assumption on our part.
Initially, the problem was daunting. It was involved with a tool, nuitka, that I'm not familiar with. It's a tool for compiling python applications into C and then makes a Windows exe file for running the application. It's somewhat niche, so I didn't find answers from web searches. I didn't know where to start, and things didn't make sense at all.
Having a set of strategies to fall back on was encouraging. It made the process a lot more fun too.