Difference between revisions of "Self-explanation"

From Learning
Jump to: navigation, search
(Created page with "'''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...")
 
Line 1: Line 1:
 
'''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.
 
'''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) [http://www.indiana.edu/~pcl/rgoldsto/courses/dunloskyimprovinglearning.pdf] calls a 1983 study by Berry "the seminal study on self-explanation".
  
 
==Software engineering==
 
==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.
 
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.

Revision as of 21:20, 20 September 2018

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.