Except that House's process is basically equivalent to making a vague guess of the problem and then quickly hacking it into production and waiting to see if anything else breaks.
Watching House helps make debugging less frustrating/painful. I didn't say that following House's example makes debugging happen any better. Occasionally, taking a page from differential diagnosis is probably a good idea, but obviously do whatever makes sense to your situation when it comes to deployment practices.
It's much more than that. First of all, his "guesses" are based on extensive experience and a very deep knowledge of anatomy, pharmacology, etc. Second, whenever he comes up with a hypothesis, he always orders tests to confirm whether he was right (but sometimes, the only available test is to try something on the patient and see what happens). And he's a big fan of Occam's Razor (there's even an episode by that name in the first season, I think), always looking for the simplest hypothesis that will explain the largest number of symptoms. All of these things apply to debugging too.
Comments
Except that House's process is basically equivalent to making a vague guess of the problem and then quickly hacking it into production and waiting to see if anything else breaks.
Watching House helps make debugging less frustrating/painful. I didn't say that following House's example makes debugging happen any better. Occasionally, taking a page from differential diagnosis is probably a good idea, but obviously do whatever makes sense to your situation when it comes to deployment practices.
It's much more than that. First of all, his "guesses" are based on extensive experience and a very deep knowledge of anatomy, pharmacology, etc. Second, whenever he comes up with a hypothesis, he always orders tests to confirm whether he was right (but sometimes, the only available test is to try something on the patient and see what happens). And he's a big fan of Occam's Razor (there's even an episode by that name in the first season, I think), always looking for the simplest hypothesis that will explain the largest number of symptoms. All of these things apply to debugging too.