On Tuesday November 5 at Noon Pacific we’ll discuss the next chapters of the Peeragogy Handbook. We’ll be asked to reflect on our motivation. Why are we engaging in these activities?
The Handbook is not just a book one reads in order to gather information. It’s about actually doing stuff. It asks you for instance to ask yourself questions such as what the problems are you want to tackle and how peer learning and production could help you.
The book also mentions how peeragogues tried to build an accelerator. The fun thing is, in a previous version of this reading group we tried the same thing. We could discuss how the project went and what lessons the experience offers. Mind you, the accelerator program in my previous reading group was about ideation and offering feedback, there was no financial investment.
We’ll also discuss yet another experiment, the 5PH1NX case study. Students were incited to take their learning into their own hands. Things did not always work out smoothly. It seems just handing over a project is not necessarily a good approach, sometimes students want to build from scratch. The principles used for this experiment, called ‘the Law’, were as follows:
- You cannot “obey” or “break” The Law. You can only make good decisions or bad decisions.
- Good decisions lead to positive outcomes.
- Bad decisions lead to suffering.
- Success requires humanity.
- “For the strength of the Pack is the Wolf, and the strength of the Wolf is the Pack.” -Rudyard Kipling
- “The Way of the sage is to act but not to compete.” -Lao Tzu
- Be honorable.
- Have fun.
- Sapere aude.
Is this a good Law? Anything we would change or add?
Let’s try to start the next chapter, about patterns (if we cannot go that fast, we’ll discuss this next week).
Patterns is anything with a repeated effect. In peeragogy, it’s to repeat processes and interactions that advance the learning mission. There are also anti-patterns, frequent occurences that are not desirable.
The architect and design theorist Christopher Alexander is the author of the book Pattern Language (1977). Read more about Pattern Language here.
Ward Cunningham, the inventor of the wiki, pointed out that wikis are tools to share and modify patterns. Maybe the experts among us can explain a bit more about Ward Cunningham and stuff such as Federated wikis and how these would relate to patterns.
This is a general outline we could use to describe patterns:
Title: Encapsulate the idea – possibly include a subtitle
Context: Describe the context in which it is meaningful. What are the key forces acting in this context?
Problem: Explain why there’s some issue to address here.
Solution: Talk about an idea about how to address the issue.
Rationale: Why do we use this solution as opposed to some other solution?
Resolution: How are the key forces resolved when the solution is applied?
What’s Next: Talk about specific next steps. How will the active forces continue to resolve in our project?
Again, the book is a call to action: it offers many patterns but also invites you to make your own pattern language.
We’ll study many patterns during our reading of the Peeragogy Handbook and hopefully build some ourselves.
If you want to join the reading group, just let me know.