Is it CS for All or is it All for CS? CS for All, to me has always meant exposing all students to CS for two reasons. First, so that every student gains some understanding of CS and also so that some of those students might be inspired to go on and study more CS. For that basic understanding, that should include a few things - the way a CS person thinks and problem solves, what a CS person does or might do professionally, and also specific practical skills that students can employ regardless of what they pursue in the future - that is programming.

To finish up, we'll look at some of the other sessions I attended but first a couple of notes. One thing I again noticed was the lack of pedagogy sessions. Maybe I missed something but other than Nifty Assignments, which isn't really about pedagogy and doesn't interest me much anymore I didn't see anything. This is nothing new but at least a couple of years ago we had "It seemed a like a good idea at the time" coordinated by Jim Huggins and Dan Garcia in all their pink suited glory and Colleen Lewis's "Micopedagogy" session (I hope I'm remembering the name right).

So last week I completed my second and final week back at Stuy teaching CS. We spent Monday finishing up the mode lesson and then spent most of the week on this topic - writing a computer program to automatically decode something "encrypted" with a Caesar Cipher. The post I just linked to was from when I first taught the lesson. I've refined and reworked it considerable since then but the gist is the same.