Self-explanation - Revision history

Vipul at 20:10, 3 October 2021

2021-10-03T20:10:10Z

← Older revision		Revision as of 20:10, 3 October 2021
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

Issa Rice at 09:35, 14 April 2019

2019-04-14T09:35:35Z

← Older revision		Revision as of 09:35, 14 April 2019
Line 8:		Line 8:

	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.

			==External links==

			* https://siderea.dreamwidth.org/1368412.html

Issa Rice at 21:20, 20 September 2018

2018-09-20T21:20:00Z

← Older revision		Revision as of 21:20, 20 September 2018
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.

Issa Rice: 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..."

2018-09-20T21:18:28Z

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..."

New page

'''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.

==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.