My Intermediate Python Programming class is fully remote, in a program that has largely gone back in-person.
On teaching in-person vs remotely: a lot of the 'relative effectiveness' arguments I hear are speculative.
So I want to share some data with you from my class.
1/
FIRST: Where am I getting this data? I survey my students.
I survey my students 19 times per quarter.
Most pedagogy breakthroughs I've had found their seed in these survey responses.
Tonight, my students completed their 16th survey of the quarter. Here's what they said.
2/
There's this idea that live lecture universally works better than pre-recorded lectures, which my students watch outside of class.
I have subjective reasons why I disagree, but let's skip those and consider what students said.
Look at this. The margin here is not close.
3/
Now, this is small-n data (n=48). I don't IGNORE those 16 students who responded that they prefer live lecture. I dig into why they prefer it to debug leakages/oversights in my system.
But it's flatly not true that my students overwhelmingly would prefer live lecture.
4/
So my students watch their lectures in pre-recorded format outside of class. What do we do in class?
We do activities. Mostly, small group activities. Students are coached on how to collaborate in their small groups. I'm there to facilitate large group activities, too.
5/
"Group exercises? Students HATE those!"
Do they? Let's ask.
I didn't cherry-pick these responses. As you can see, not EVERYONE loves the format. The vast majority do like it.
Also notice the illuminative feedback largely isn't about the format; it's about the difficulty.
6/
Those students are right; my group exercises are f'ing hard. They're like that by design.
Why are they hard:
1. They have several steps; I want all groups to complete step, say, 3, but I include 4 & 5 to occupy the fast groups while everyone gets to 3. But...
7/
... these are CS students. The whole class is try-hards. No one wants to not get to 5. So that's a frustrating experience.
Reason 2: I'd rather they have an extremely challenging (which, yes, includes frustrating) experience in a venue where they're not being GRADED on it.
8/
For in-class activities, I grade on participation—not completion.
I'm already essentially forcing try-hards to fail at something. They're already at the minimum effective stress dose. Ratcheting that stress higher w a grade won't increase learning IMHO.
SO...
9/
...the CLASS has its frustrating bits, but the overall volume of time spent thinking "Am I going to fail this class" should be lower relative to the challenge.
I said I'd just talk data here but I knew I'd get this question so I figured I'd explain.
ANYWAY, anyway anyway
10/
This is about the best breakdown I've had on timing an in-class activity, by the way.
That blue wedge represents kibbitzing. That's a loss I want to minimize. In my experience, out of that yellow wedge, most complete the "minimum" but want to finish the enrichment steps.
11/
This one, for example, WAY worse.
/12
FWIW, my format would be much harder to execute in-person.
It would be hard to separate the groups enough in a room to avoid distracting cross-talk, and they'd have to either be in each other's personal space to work in groups, or share screen anyway.
/13
Takeaways? I guess, 3:
1. in-person class just WORKING better is not a universal experience.
2. Some adaptations to remoteness were actual pedagogical strides; we shouldn't leave them behind when we get back in the classroom.
3. SURVEY YOUR STUDENTS AND LISTEN TO THEM
14/14
• • •
Missing some Tweet in this thread? You can try to
force a refresh
DOC: Yikes. Broth has too much sodium. You'll raise your blood pressure
ME: That's the point. My blood pressure is low
DOC: *takes bp* ...wow. I...could prescribe something to raise your blood pressure
ME: *points at broth*
This summer in NYC, I fainted in the middle of a 500 person junk swap because I'd gone for a run and I guess hadn't fully rehydrated. THAT's how close to the line my bp runs.
Then when they took me to the ER, where my poor mother had to come visit me thinking I might've DIED /1
they wouldn't let me leave until my bp & hr returned to "normal." Except my usual 106/60ish and 48 doesn't hit "normal".
I had to wait until nurses weren't looking, have my mother shield me, and do jumping jacks so they'd let me leave.
The TV equivalent of french fries, the not-exactly-satisfying-but-momentarily-deicious stack of cable TV tropes in a trenchcoat that I've threaded the daylights out of on its queer representation: Lucifer
I've been looking up a lot of soup recipes lately.
Now, the way that I learn things is to avoid committing a bunch of seemingly unrelated stuff to memory by coming up with a framework that connects all the pieces together.
I give you: A Framework for Vegetable Soup
1/
STEP 1: Choose two vegetables.
I have no idea why it's two, but I can confirm that "garden soup" where you blend several together tastes gross to me so let's just accept the Magic Number Two for now
Note: I'm skipping "Green Box Credit" as a motivation. That's an extrinsic motivation created by employers in lieu of actual instructive hiring criterion, and its optimization is a 24h cron with an empty commit script to a public repo.
We're not counting that.
Onward.
2/
The next motivation for OS contribution is to learn.
Couple things about this one.
1. Code bootcamps and whatnot LOVE to recommend this to BEGINNERS, and it's one of the worst ideas I've heard these places consistently parrot. Here's why:
3/
As any infosec person will tell you, a company's greatest security vulnerability is its people.
So I was shocked that, in 2 years of WFH, tech largely ignored meeting security—despite the fact that many techies are cohabiting partners with employees of competitors.
Like,
/1
...sure, partners talk, of course.
But it's a little different to be having a Zoom about something, and the verbatim conversation is wafting through a set of speakers with a competitor literally sitting in the room.
But yesterday, I realized why companies aren't worried.
/2
My co-presenter and I stopped in a coffee shop. A few tables over, two young men were talking. LOUDLY.
I, and presumably anyone else in that coffee shop, now know:
- How their company's payroll is secured
- What software it's in
- The NAME of the person with blanket access
/3