In the latest episode of Rite Gud, we talk to @ChrisBookishCauldron about how we read and why we read. What’s the point of reading when there are other ways of getting information? Does reading make you a better person? And why are so many Americans so bad at it?
y'all there is not a "what the fuck" big enough for what I read in this and am starting to hear in https://features.apmreports.org/sold-a-story/
I mean. This makes a lot of things I've seen around the internet make so much more sense, and also, how do we get out of this?
just in case anyone thinks the immediately above characterization must be overblown: readers are encouraged to intuit meaning for passages based on guess work instead of reading words and interpreting them
i could feel the blood draining out of my body. many of the teachers quoted here are effusive about how the system "felt" to them. phonics were bad because it "felt old fashioned." they wanted to believe in what they were being sold because it "felt" empowering and comfortable
fucking up decades of lives based on vibes, for profit: the american way
education has never been accessible to me, but having been in compulsory schooling around these times makes it easy to imagine many of my worst teachers were just going "thank god! this one can read" before ignoring me (and my many and obvious non-academic problems)
Having now listened to all of Sold a Story, I can confirm this is not an exaggeration and it's truly shocking (not least because Bush of all people was sort of on the right side of history on this one). I almost cried in public hearing one girl be so excited about being able to read after the school failed her and her dad had to teach her himself.
I don't teach children how to read, but I do teach uni students how to program, and this has got me thinking: should we be doing more to teach students how to read code?
The stakes are nowhere near as high1, but I'm starting to convince myself there are qualitative similarities here. In Sold a Story they use an example something like a kid reading "sleeping" instead of "napping". It kind of makes sense, but it's just not what's on the page and it's not the mistake you'd make if you were actually reading the word, they're just guessing from the surrounding context.
Thinking back, I've noticed similar mistakes from students when I ask them what a bit of code does and why. Most egregiously, one student got the 'what' right, but when pressed on the actual code reason 'why' they thought it was fundamentally because of the function's name. I originally attributed this sort of error to 'magical thinking', i.e. they read the code/parsed the syntax but attributed magical semantic meanings to variable names, but now I'm wondering if the more fundamental problem is they're not truly reading the code in the first place, or even more terrifying, they never learned how to read properly.
To be clear, that's a particularly extreme example and obviously you can't get into university without being literate, but if that literacy was acquired with these guessing/'three-cueing'/'whole-word' methods, then you'd probably use those same methods when learning to read a programming language and it's going to be 10x harder. I'm not sure how widespread this problem is among our UK2 or international students, but either way I'm gonna put a lot more thought into teaching students how to read code.
-
See: Parenti on the joy literacy and the dejection of illiteracy
-
Three-cueing seems to only have been officially discredited in 2006, and even then it still had/has some inertia: https://rrf.org.uk/2018/07/30/phonics-developments-in-england-from-1998-to-2018-by-jenny-chew/

