SIGCSE 2019: public accountability
What, nine months since my last blog entry? Well ... read the previous entry to read why.
Seriously, though .... my annual trip to the SIGCSE 2019 Symposium just concluded. And I'm going to head back to the office on Monday, right into the middle of a campus-wide fight (sigh), find the pile of grading that I need to work on, and forget about all the interesting ideas I encountered. The pile of paperwork I collected will end up in a corner of the office, only to be encountered a year from now when I clean the office and have long since lost the opportunity to put some of what I learned into practice.
Will that happen again? Yeah, probably. But maybe I can do something to help with that.
So, in what follows, I'm going to capture the ideas I ran across, mostly from the little notebook I picked up in the exhibit hall (thank you, SIGCSE 2020 organizers), and what I'd like to do about them. Maybe publicly speaking the words into existence will make it more likely that something will actually happen with them.
If you like, feel free to ask me about these ideas in the coming months, to hold me accountable. Or, if CS education topics aren't your speed, go ahead and move on to the next item in your news feed.
Last chance to bail out ...
Okay, here we go. These ideas are in no particular order. Also, I'm not necessarily going to unpack these, so the notes may sound a little cryptic. If you want to ask me about them, please do so.
My friend wants to do a podcast with me. We're not exactly sure what we'd do, except maybe talk about CS education. Neither of us are particularly qualified, but our friends say they love to hear us talk about stuff. How do you start a podcast? How do you make it work? Especially when we're separated by, oh, 1200 miles or so?
Debugging. A special session talked about "debugging as productive failure". David DeLiema gave a taxonomy of activities that constitute good debugging. Deborah Fields talked about celebrating bugs, and bug-based pedagogies. Colleen Lewis says that students think finding bugs is easy (it isn't) because usually the fix is easy once you've found it. Some of my students struggle with debugging. How do I find a way to help my students learn to debug better?
program-wars.firebaseapp.com hosts an online card game to teach programming and security concepts. Is this something to promote?
CS-300 and diversity: some articles to consider adding to the reading list:
- "Google teams": article on how Google found that inclusion leads to better teams
- Article on "mathematics of harassment" that I can't seem to find right now: points out that harassment affects underrepresented groups more simply because there are fewer members available to be harassed.
- Active bystander training: is there a gentle introduction somewhere?
- Replace article on the old ACM code of ethics with a link to the new ACM code of ethics.
Exploring privilege session: applications to CS-300, AP Workshops, CETL?
- "Unpacking the Invisible Knapsack", McIntosh, 1988
- Microaggression exercise: for CETL? for APSI?
New data sources for CS-102: bridgesuncc.github.io
Poster on seminar on worthiness & belonging (see notes in my bag): something to bring to ACM-W chapter? Or CETL?
All those photos of book covers you took? Process them, order copies, skim them online, do whatever to get it done.
SIGCSE Reads. Go order the 2019 books and then order the 2020 books.