46

You write code.
A strange issue prevents you to proceed further.
Try one fix. Fails.
Try another Fix. Fails.
...
Try fix #28. Fails.
You decide to ask for help in the support forum.
You start writing your post, mentioning everything you've tried so far. You feel your social anxiety and fear the humiliation of being told "because you didn't try X, you idiot". Then you come up with an idea for fix #29.
(fix #29 normally involves Wireshark or similar low-level inspection tool)

Try fix #29. It succeeds :)

Comments
  • 9
    There's a term for that: Rubber Duck Debugging
    Just explain your problem so easy that even a rubber duck (or your grandma) would understand it. And while explaining you often realize what the problem really is ;)
  • 4
    @katho2404 I know right? StackOverflow should have three buttons: Submit, Cancel, Nevermind I just solved it by myself thanks to rubber duck programming
  • 0
    @NoNameCode I wasn't serious ;)
  • 0
    @katho2404 my grandmother is a rubber duck so this is a great debugging method for me!
  • 1
    to me this sounded like a dungeons and dragons description:

    roll for reproducible example
    5 : your example is not working says a SO user. roll for initiative...
Add Comment