On 2021-02-21 07:54:37 David T-G wrote:
|Hi, all -- | |...and then Dave Howorth said... |% |% On Sun, 21 Feb 2021 10:58:11 +0100 |% Per Jessen
wrote: |% |% > Carlos E. R. wrote: |% > |% > > Nothing like writing an email to see the problem. Now it |% > > works. :-D |... |% > drag her over to the blackboard and you explain the problem to her. |% > Always works. |% > </anecdot> |% |... |% how your code worked to the teddy, and he always pointed out where the |% problem was. |[snip] | |I was the cleaning woman or teddy bear to a classmate back in college. |We tended to work in the computer lab at the same time, and he would |suddenly walk up to me with his long fan-fold printout and start walking |me through his code before suddenly exclaiming "wait, it shouldn't do |THAT" or similar and walking away. It took me a few weeks to realize |that I didn't actually have to pay him any attention :-) | |On the other hand, Laura and I could never debug each other's code |because we always came at a problem from opposite directions. Two |different designs, both eventually valid products, but reading hers |always tied me up in "but it should be THIS WAY" knots. I guess that's |why we've made such a good team for nearly 30 years now :-)
Debugging one another's code (I look at your listing, you look at mine) never works, because you're not explaining your own code to another. When you explain your own code you have to elucidate the tacit assumptions you have made about what it does, and when you do that you show /yourself/ where the problem is. That's why you don't have to listen much to your colleague's explanation. Leslie
| |Fun memories ... | | |HAND | |:-D -- openSUSE Leap 15.2 x86_64