I was involved in a really exciting project a few months ago and now that it's available, it's time to tell everyone about it.
There's a new book on teaching CS in K12 - Computer Science in K12. I got an email a few months ago from Shuchi Grover. Okay, actually a DM over twitter. I hadn't officially met Shuchi although I'm pretty sure we've been at the same table or group in a conference or two but I did know her from reputation.
Following up on my last post I thought I'd talk a bit more about course development. According to most powers that be it's all done ahead of time. Organizations and companies with curricula to sell package it all up ahead of time lesson by lesson unit by unit. When I create a new course at Hunter, they demand a sample syllabus during the approval process with a week by week outline, assignments reading and more.
I spent a couple of days last week hunkered down working designing a CS Ethics course and of course it got me thinking about designing courses in general. One of the topics I've ranted on is my disdain for canned curricula. I've never been a fan. This isn't to say I don't want to leverage other people's work. I'll take sample curricula, lessons, and all the resources I can get my hands on but I'd never just deliver them as is.