bradreeder
commented
7 years ago Serendipitously enough, I mentioned the idea of creating a pattern language for F&C to @sofer and it turns out it's one of his favourite books and that he's been attempting to do the same thing for some time. Life's weird like that.
To keep documentation in one resource here's my original email:
Originally my idea was that over time through a focus on student (user) testing we’d distil our curriculum down to a set of interwoven patterns that when sufficiently tested become a part of our language that the master-repo embodies.
Then when it comes to curriculum planning, all you have to do is initiate mentors into the community's pattern language and they can continue it, improving and introducing new patterns to test.
S-G-C’s focus then really becomes about discussing the community’s pattern language. Verifying through student feedback what is a good and bad pattern, and over time marking student feedback from each iteration against patterns to quickly get a sense of how verified they are. It feels like it could be a good democratic model to me.
When I was given the course facilitator role https://github.com/foundersandcoders/business/issues/113 this resource was the blue-print I originally had in mind for what's now the master-reference.
This project will be an experiment I intend to work on alongside my time in the role. It is a community-centred resource and anyone is welcome to contribute.
It won't be used as a resource for curriculum planning unless it reaches maturation & there is consensus that the methodology developed here would be useful. I've separated it from the master-reference into this repo to reflect that as it can always be merged in later.