Ah I see, thanks for the link. I don't think the case I talked about is the same case as Rubber duck debugging. It's not to read aloud (maybe in front of another programmer or audience). It's more like, if your students or end user read the documentation and still have some questions left at the end. And ask you the questions about stuff they did not understand.
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments