#common core

The thing is, there's a reason that standardization takes hold in so many domains. Agreeing on a common standard enables collaboration by many entities without any need for explicit agreements or coordination. The existence of the ANSI/SAE J563 standard automobile auxiliary power outlet (AKA "car cigarette lighter") didn't just allow many manufacturers to make replacement lighter plugs. The existence of a standardized receptacle delivering standardized voltage to standardized contacts let all kinds of gadgets be designed to fit in that socket.

Standards crystallize the space of all possible ways of solving a problem into a range of solutions. This inevitably has a downside, because the standardized range might not be optimal for all applications. Think of the EU's requirement for USB-C charger tips on all devices. There's a lot of reasons that manufacturers prefer different charger tips for different gadgets. Some of those reasons are bad (gouging you on replacement chargers), but some are good (unique form-factor, specific smart-charging needs). USB-C is a very flexible standard (indeed, it's so flexible that some people complain that it's not a standard at all!) but there are some applications where the optimal solution is outside its parameters.

And still, I think that the standardization on USB-C is a force for good. I have drawers full of gadgets that need proprietary charger tips, and other drawers full of chargers with proprietary tips, and damned if I can make half of them match up. We've continued our pandemic lockdown tradition of my wife cutting my hair in the back yard, and just tracking the three different charger tips for the three clippers she uses is an ongoing source of frustration. I'd happily trade slightly sub-optimal charging for just being able to plug any of those clippers into the same cable I charge my headphones, phone, tablet and laptop on.

The standardization of American education has produced all the downsides of standardization – a rigid, often suboptimal, one-size-fits-all system – without the benefits. With teachers across America teaching in lockstep, often from the same set texts (especially in the AP courses), there's a massive opportunity for a commons to go with the common core.

For example, the AP English and History classes my kid takes use standard texts that are often centuries old and hard to puzzle out. I watched my kid struggle with texts for learning about "persuasive rhetoric" like 17th century pamphlets that inspired anti-indigenous pogroms with fictional accounts of "Indian atrocities."

It's good for American schoolkids to learn about the use of these blood libels to excuse genocide, but these pamphlets are a slog. Even with glossaries in the textbooks, it's a slow, word-by-word matter to parse these out. I can't imagine anyone learning a single thing about how speech persuades people just by reading that text.

But there's nothing in the standardized curriculum that prevents teachers from adding more texts to the unit. We live in an unfortunate golden age for persuasive texts that inspire terrible deeds – for example, kids could also read core Pizzagate texts and connect the guy who shot up the pizza parlor to the racists who formed a 17th century lynchmob.

But teachers are incredibly time-constrained. For one thing, at least a third of the AP classroom time seems to be taken up with detailed instructions for writing stilted, stylized "essays" for the AP tests (these are terrible writing, but they're easy to grade in a standardized way).

That's where standardization could actually deliver some benefits. If just one teacher could produce some supplemental materials and accompanying curriculum, the existence of standards means that every other teacher could use it. What's more, any adaptations that teachers make to that unit to make them suited to their kids would also work for the other teachers in the USA. And because the instruction is so rigidly standardized, all of these materials could be keyed to metadata that precisely identified the units they belonged to.

The closest thing we have to this are "marketplaces" where teachers can sell each other their supplementary materials. As far as I can tell, the only people making real money from these marketplaces are the grifters who built them and convinced teachers to paywall the instructional materials that could otherwise form a commons.

Like I said, I've got a completely overfull plate, but if I found myself at loose ends, trying to find a project to devote the rest of my life to, I'd be pitching funders on building a national, open access portal to build an educational commons.

It may be a lot to expect teachers to master the intricacies of peer-based co-production tools like Git, but there's already a system like this that K-8 teachers across the country have mastered: Scratch. Scratch is a graphic programming environment for kids, and starting with 2019's Scratch 3.0, the primary way to access it is via an in-browser version that's hosted at scratch.mit.edu.

Scratch's online version is basically a kid- (and teacher-)friendly version of Github. Find a project you like, make a copy in your own workspace, and then mod it to suit your own needs. The system keeps track of the lineage of different projects and makes it easy for Scratch users to find, adapt, and share their own projects. The wild popularity of this system tells us that this model for a managed digital commons for an educational audience is eminently achievable.

So when students are being asked to study the rhythm of text by counting the numbers of words in the sentences of important speeches, they could supplement that very boring exercise by listening to and analyzing contemporary election speeches, or rap lyrics, or viral influencer videos. Different teachers could fork these units to swap in locally appropriate comparitors – and so could students!

Students could be given extra credit for identifying additional materials that slot into existing curricular projects – Tiktok videos, new chart-topping songs, passages from hot YA novels. These, too, could go into the commons.

This would enlist students in developing and thinking critically about their curriculum, whereas today, these activities are often off-limits to students. For example, my kid's math teachers don't hand back their quizzes after they're graded. The teachers only have one set of quizzes per unit, and letting the kids hold onto them would leak an answer-key for the next batch of test-takers.

I can't imagine learning math this way. "You got three questions wrong but I won't let you see them" is no way to help a student focus on the right areas to improve their understanding.

But there's no reason that math teachers in a commons built around the (unfortunately) rigid procession of concepts and testing couldn't generate procedural quizzes, specified with a simple programming language. These tests could even be automatically graded, and produce classroom stats on which concepts the whole class is struggling with. Each quiz would be different, but cover the same ground.

When I help my kid with her homework, we often find disorganized and scattered elements of this system – a teacher might post extensive notes on teaching a specific unit. A publisher might produce a classroom guide that connects a book to specific parts of the common core. But these are scattered across the web, and they aren't keyed to the specific, standard components of common core and AP.

This is a standardized system that is all costs, no benefits. It has no "architecture of participation" that lets teachers, students, parents, practitioners and even commercial publishers collaborate to produce a commons that all may share and improve upon.

In an ideal world, we'd get rid of standardization in education, pay teachers well, give them the additional time they needed to prepare exciting and relevant curriculum, and fund all our schools based on need, not parents' income.

But in the meanwhile, we could be making lemonade of out lemons. If we're going to have standardization, we should at least have the collaboration standards enable.

I'm Kickstarting the audiobook for The Bezzle, the sequel to Red Team Blues, narrated by @wilwheaton! You can pre-order the audiobook and ebook, DRM free, as well as the hardcover, signed or unsigned. There's also bundles with Red Team Blues in ebook, audio or paperback.

If you'd like an essay-formatted version of this post to read or share, here's a link to it on pluralistic.net, my surveillance-free, ad-free, tracker-free blog: