<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.programmableinfrastructures.info/index.php?action=history&amp;feed=atom&amp;title=Learn%2CUnlearn%2CRelearn</id>
	<title>Learn,Unlearn,Relearn - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.programmableinfrastructures.info/index.php?action=history&amp;feed=atom&amp;title=Learn%2CUnlearn%2CRelearn"/>
	<link rel="alternate" type="text/html" href="https://wiki.programmableinfrastructures.info/index.php?title=Learn,Unlearn,Relearn&amp;action=history"/>
	<updated>2026-04-14T08:45:40Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://wiki.programmableinfrastructures.info/index.php?title=Learn,Unlearn,Relearn&amp;diff=177&amp;oldid=prev</id>
		<title>Seda: Created page with &quot;In a conversation with Ted Byfield, he commented that Introduction to Clouds as infrastructure sounds like a place to unlearn and relearn the history of computing and how software production works. Unlearning and relearning is also a (pedagogical) approach used by Constant vzw and continues to be part of TITiPI&#039;s work. Constant used it, for example, in workshops where participants were invited designers to unlearn their practice using Adobe project, and instead relearn (...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.programmableinfrastructures.info/index.php?title=Learn,Unlearn,Relearn&amp;diff=177&amp;oldid=prev"/>
		<updated>2024-11-20T10:34:21Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;In a conversation with Ted Byfield, he commented that Introduction to Clouds as infrastructure sounds like a place to unlearn and relearn the history of computing and how software production works. Unlearning and relearning is also a (pedagogical) approach used by Constant vzw and continues to be part of TITiPI&amp;#039;s work. Constant used it, for example, in workshops where participants were invited designers to unlearn their practice using Adobe project, and instead relearn (...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;In a conversation with Ted Byfield, he commented that Introduction to Clouds as infrastructure sounds like a place to unlearn and relearn the history of computing and how software production works. Unlearning and relearning is also a (pedagogical) approach used by Constant vzw and continues to be part of TITiPI&amp;#039;s work. Constant used it, for example, in workshops where participants were invited designers to unlearn their practice using Adobe project, and instead relearn (or reconstruct a collective practice) using FLOSS alternatives. TITiPI uses the term also to unlearn typical hierarchical make up of institutions as well as their relationship to technology. The approach apparently has already traveled to management circles, although some of the articles suggest it comes from Alvin Toffler who was a business person and a futurist. Below are some popular references to put the concepts into their broader context. &lt;br /&gt;
&lt;br /&gt;
An educational perspective (with the use of the three concepts as part of a broader cycle): https://www.educate-me.co/blog/learn-unlearn-relearn&lt;br /&gt;
&lt;br /&gt;
Pedagogical/psychological use of the term: https://blog.learnlife.com/learn-unlearn-relearn&lt;br /&gt;
&lt;br /&gt;
Forbes use of the term during COVID: https://www.forbes.com/sites/margiewarrell/2020/06/12/learn-unlearn--relearn-what-got-you-here-wont-get-you-there/&lt;/div&gt;</summary>
		<author><name>Seda</name></author>
	</entry>
</feed>