I love how "shotgun debugging" works.

Let's say the microwave doesn't work. I put my burrito in it, press buttons. Nothing happens.

Any sane person would trace the possible cause: Check if it is plugged in, maybe the fuse is blown? Nah, we don't have time for this: Let's try shotgunning it!

- Turn the burrito upside down.
- Try aligning the burrito in different cardinal directions.
- Press random buttons
- Remove burrito wrapper
- Separate burrito into single components, sort them onto a plate in a nifty layout and try microwaving that.
- Remove each component of the sorted burrito plate and try microwaving the plate with less and less items.
- Try microwaving each separate item and then later reassembling them back into burrito to see if it gets heated after the act.
- Try putting a cat on top of the microwave.
- Pour water on cat
- Notice a strong reaction involving water and the cat.
- Try catching the cat for additional testing.
- Go to the hospital to get stitches on your open wounds.

Later write a bug report to the maintainer: "Microwave doesn't work. Tracked the issue down to the moisture level of the cat, additional testing needed."

  • 43
    This is just fantastic! And I’m not sure whether try/catching the cat was an intentional pun, but it is appreciated.
  • 5
  • 35
    The worst thing is, half the time the cat temporarily fixes it.
  • 5
    Actually, some of these are usable debugging techniques, for example: disassembling a program (finding the part that causes the difference between functioning and malfunctioning) is a very good idea if you have no clue where the source of the bugs is (hint: it's the overdue meat)
  • 5
    @TempestasLudi I personally recommend you run debugger first. :)
  • 1
    @ClySuva ah, right, that is a good idea most of the time.
  • 0
    That’s creativity right there!! 😂😂😂😂😂
Add Comment