There are many pattern catalogs. Consider Christopher Alexander's for architecture in book form, Ward Cunningham's way more flexible one about programming in wiki form, Wise Democracy's (Tom Atlee) in carton card and web form (with comments/discussion below them), John Kellden's in text (and another variant that's potentially a card game), and in the last session of the reading group we learned about Group Works (print, website and app) for the facilitation of a meeting, where also this list is maintained: https://groupworksdeck.org/other-pattern-language-links
I'm not entirely sure how patterns are necessarily related to peeragogy except for how the project got influenced historically
but it makes sense to offer students and teachers some best practice patterns and an entire pattern language behind it which expresses how peeragogy can be applied, and especially the pedagogical aspects translated into a peer context/environment,
did you notice that it's kind of difficult to find the patterns in the book?
For review or extension of the patterns, I think the After Action Review could be a good source for informing the design of the patterns and the pattern language, where actual peer learning activities get analyzed to mine the healthy, nurturing practices from those, ideally supported by software as well that helps with the organization of the reviews and an ongoing review practice.
Iteration 3 was: "We can do something novel here with 'Next Steps' to shape the evolution of a collaborative project" (circa 2014)Iteration 4 is basically still in progress: We're going to try to "patternize" as much of the Handbook as we can. Also trying to get our 'Next Steps' are clearly sorted and aligned with patterns.
I think the plan with the more fully "Patternized" book is to make the whole thing a pattern catalogue, furthermore organised from the top down as one giant pattern with sub-patterns. This should make it easier!
Hooking patterns up with issue trackers (next steps) should be something we can 'export' from this project as a methodology that many others can use.
For review or extension of the patterns, I think the After Action Review could be a good source for informing the design of the patterns and the pattern language, where actual peer learning activities get analyzed to mine the healthy, nurturing practices from those, ideally supported by software as well that helps with the organization of the reviews and an ongoing review practice.Yes, 100%. It's a way to detect new patterns, and debug existing ones.
something i’ve thought about increasingly;
perhaps we can map out steps towards achieving this.
i think joachim stroh at diglife has been developing something with digital cards....might be a partial solution. need to have a look there
why is the focus on the handbook ... while the next steps, activity/progress tracking, all of the other useful components for project collaboration and its data remain with little attention?
We're not planning to print outdated "next steps" of the peeragogy project (except as examples) with a 1+ year paper book release cycle, are we?
What would that mean for the cycle of tasks/activities (very slow and long ones, maybe only capturing larger projects?), or the relevancy of the printed handbook
I see, helps with my question above as well, but then, what to do about all the theory chapters? Get rid of them, move them into a separate publication, force-fit them into the pattern template somehow?
Makes the patterns operatable, a mechanism to actually realize the repeated effects they're describing. I always wonder who needs patterns for what, if in a "soft"/vague domain, where patterns still can be used as a tool of passive analysis, but if there's no way to actively design or deliberately pick nurturing patterns and in some way actively applying them, they'll remain nice thoughts and theory, not necessarily solving the problems they're supposed to solve.
Same for the After Action Review (AAR), shouldn't those be captured/recorded as data in a format somewhere, possibly with the help of software (or alternatively manually)?
Which of the current activities could be AARed? The reading group? Handbook v4 activity (but that's not after the action yet)? The issues on GitHub (or better, the larger projects behind those)? Who is doing that where, when, how?
Is it important that somebody else reviews the action (not the trainee), potentially an arbitrary/random group of anonymous peers?
Thanks for the link. If it's not libre-freely licensed, how would one legally be allowed to build and share such a repository, and encouraged to do technical work for it?
By now, what would be a pretty good rationale for who needs this for what? I don't necessarily need patterns myself, hardly teaching topics, hardly involved in peer learning classes, not being aware of learning opportunities that are offered (except the actual regular online peer learning that happens unorganized, unstructured, circumstantial all over the place).
Naturally it’s possible to reimplement the patterns if they are useful! Copyright only covers expression, not ideas.
We are trying to design a useful approach for EVERYONE to have access to high quality learning opportunities.
We are trying to design a useful approach for EVERYONE to have access to high quality learning opportunities.
I'm not convinced yet... To me it became increasingly clear that the focus is actually on the pedagogical side and less on digital/peerness, and why not.
All the peer learning that goes on every day on a massive scale on the Internet, peeragogy doesn't seem to necessarily address or be compatible with it.
theoretically the population always has access to high quality learning opportunities if they only manage to walk to the capital and maybe get school attendance funded
it's not even that the teacher eventually learns the tech from SWATs but them doing some assisting work for the teacher, none of which necessarily represents the realities of digital peer learning, but instead better fits the traditional academic peer concept. OK, I may potentially read too much into the description presented in the chapter, but I think it may still illustrate the general point.
With a mixed audience of teachers from a physical/formal context, digital/software/tech people (but less so), learners/students potentially (who already and soon encounter the realities outside of formal institutionalized schooling), the Peeragogy handbook and project inevitably run into questions of how these different perspectives could possibly resolve, but even if they don't, it's always helping some audiences in some ways, to at least have a discussion about these topics, better than continuing with business as usual in any case.