I've often been glad not to be held to the standards of doctors. How many guesses does it take to figure out why a copy onto the clipboard didn't work? Or why a

I've often been glad not to be held to the standards of doctors. How many guesses does it take to figure out why a copy onto the clipboard didn't work? Or why a shift+middle-drag panned instead of rotating? Most of my troubleshooting doesn't involve million-dollar equipment and hours of travel. If I was forced to troubleshoot the way doctors have to do--with real human pain and weeks between a visit and a lab test and another visit and two fights with insurance in between, and trying to get by with the $400 test instead of the $4000 test and an xray instead of an exploratory surgery. Tech people do complicated troubleshooting all the time. Sometimes we test an idea in 15 minutes to rule something out. Sometimes we just comment out 20 lines of code and recompile. Sometimes we have to schedule a system failover and make sure we've got a really good plan to justify the cost and inconvenience. But mostly it's 3 or 4 or 10 guesses to narrow things down and we don't sweat it. I mean, if a mouse isn't moving, reboot. If it still doesn't move, swap in a different mouse. If it still isn't working check the driver... If a doctor tried that approach with your hip...