Self-explanation: Difference between revisions
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
Closely related to self-explanation is a technique called ''rubber duck debugging'' (or ''rubber ducking''), where a programmer explains a software problem to themselves (or someone who knows nothing about programming) to help them debug code. | Closely related to self-explanation is a technique called ''rubber duck debugging'' (or ''rubber ducking''), where a programmer explains a software problem to themselves (or someone who knows nothing about programming) to help them debug code. | ||
==See also== | |||
* [[Learning by teaching]] | |||
* [[Feynman technique]] | |||
==External links== | ==External links== | ||
* https://siderea.dreamwidth.org/1368412.html | * https://siderea.dreamwidth.org/1368412.html | ||
Latest revision as of 20:10, 3 October 2021
Self-explanation is a learning technique where the learner explains the steps they take in solving a problem or their processing of new information to themselves.
History
Dunlosky et al. (2013) [1] calls a 1983 study by Berry "the seminal study on self-explanation".
Software engineering
Closely related to self-explanation is a technique called rubber duck debugging (or rubber ducking), where a programmer explains a software problem to themselves (or someone who knows nothing about programming) to help them debug code.