Computer Science Education Week wrapped up yesterday, and if you weren't paying attention: this was the week Barack Obama sat down at a laptop in the White House and wrote a line of JavaScript, making him (apparently) the first sitting president to ever write actual code. It happened last Monday, Dec 8th, as part of the Hour of Code push from Code.org, and by Tuesday my Twitter feed was just wall-to-wall screenshots of the guy in a blue button-down clicking through an Angry Birds tutorial.
I'll be honest, my first reaction was pure cynicism. Drag-and-drop blocks that snap together to move a bird forward one square isn't "coding" in any sense my brain wants to accept. I learned on a hand-me-down keyboard with a cassette deck, typing out BASIC line numbers one at a time and getting a syntax error if I so much as breathed wrong. So watching a room full of dignitaries clap because someone dragged a "move forward" block into a loop felt a little like watching people learn to cook by microwaving a Lean Cuisine.
Then I actually sat down and did it myself Saturday night, mostly out of spite, and, fine, I get it now.
The Code.org Angry Birds one (there's also a Frozen-themed one if you're into that, my niece definitely is) isn't trying to teach you Python. It's teaching the shape of the thing before the syntax gets in the way. Loops, conditionals, the idea that a program is just a sequence of instructions a dumb machine follows literally and without judgment, that's the actual lesson, and honestly it clicked for me faster in block form than it ever did staring at a semicolon I forgot in 2004. I finished the hour in about twenty-five minutes and immediately went and did the JavaScript version of the same exercises just to see if the underlying logic mapped, and it does, almost one to one. That's kind of the point.
What got me thinking harder about this, though, wasn't the tutorial itself. It's that something like 20 million people reportedly did an Hour of Code session this week, across 180-something countries, per the numbers Code.org's been putting out. Whether that stat is exactly right or a little rounded up for the press release, I don't actually care. The scale of it is the story. A decade ago "learn to code" content lived in forums and used-bookstore textbooks with a floppy disk taped to the inside cover. Now it's a browser tab, no install, no compiler, works on a school Chromebook. That's the actual shift, and it happened quietly while everyone was busy tweeting screenshots of a president clicking a mouse.
My complaint, if I've got one, is about the framing more than the tool. Every article this week used some version of "kids need this to get jobs," and sure, that's true, but it's such a joyless reason to hand a kid their first loop. I didn't learn to program because I was thinking about a career. I learned because I wanted my text adventure game to stop printing "You are dead" every single time regardless of what I typed. The motivation was fixing something broken and stupid that I'd made myself. None of the Hour of Code stuff really replicates that feeling of janky, personal ownership. It's polished, it's guided, there's a progress bar. Good pedagogy, probably. Less fun than staring at your own mess at 11pm trying to figure out why the dragon keeps eating you before the intro text finishes.
Anyway. If you've got a kid, or a niece, or just twenty idle minutes and some leftover cynicism like I had, it's still up at Code.org even though the official week is over — these things don't expire, they just stop getting press coverage. Worth the twenty-five minutes. I'm not going to pretend one browser tutorial turns anyone into a programmer, but as a front door, it's a lot better than the one I walked through.