5 replies to this topic

[eafkuor]

From "The Practice Of Programming", by Brian W. Kernighan & Rob Pike:

Quote

Explain your code to someone else. Another effective technique is to explain your
code to somcone else. This will often cause you to explain the bug to yourself.
Sometimes it takes no more than a few sentences, followed by an embarrassed
"Never mind, I see what's wrong. Sorry to bother you." This works remarkably
well; you can even use non-programmers as listeners. One university computer center
kept a teddy bear near the help desk. Students with mysterious bugs were required to
explain them to the bear before they could speak to a human counselor.

Best. Advice. Ever.

[LuthfiHakim]

Lol, I learn that from my own experience. Frequently when I am explaining my work to someone else, I would see the cause of known bugs, potential bugs, better approach/solution for already implemented features/functionalities, or (this one I hate the most) new interesting feature/functionalities. :)

[wim DC]

Quote

Sometimes it takes no more than a few sentences, followed by an embarrassed
"Never mind, I see what's wrong. Sorry to bother you."

Haha :c-lol: So familiar.

[zeroradius]

and oopsy bear has now been moved next to my computer :c-penguin:

[John]

This is absolutely true. Back when I was a n00b and asked questions on programming forums, while explaining the issue in a post, I often realized the solution before I pressed the submit button.

[Alexander]

John said:

Back when I was a n00b and asked questions on programming forums, while explaining the issue in a post, I often realized the solution before I pressed the submit button.

It was always my ideology to write informative questions, ninety percent of the time formulating the steps and what is output I find the issue.