Spent 6 hours trying to get two tools to talk to each other. Turns out it was one checkbox I missed.

3 comments

3 Comments

Question if six hours was really necessary or if you just got stuck in a rabbit hole. Most of the time these issues come down to one tiny thing you could've found in 10 minutes with a fresh set of eyes. Does it actually work now or are you just hoping it does?

andrew_baker914d ago

Respectfully, I don't think that's always the case. I spent a solid five hours tracking down a weird memory leak in a Docker container last month and it turned out to be a super obscure kernel module conflict that no fresh set of eyes would have caught in ten minutes. It actually works now after finally finding the right kernel parameter to disable the module, and I verified it with a few hours of stress testing. Sometimes those rabbit holes lead to deeper understanding of the system, even if they feel wasteful in the moment.

xenam8413d ago

Five hours on a kernel module issue? Been there. Spent a whole Saturday once tracking down a printer driver that was corrupting PDFs. Turned out to be a single bad cache file. Felt like a waste until I learned more about the print spooler than I ever wanted to know.