Why we went quiet for a month

Our last post went up on June 17th. This one is going up a month later. If you noticed the gap — and a few of you emailed to ask — you deserve a straight answer instead of a vague one.

The short version: we spent the month building instead of writing about building. The longer version is worth telling, because it says something about how we think about this place.

What actually happened

June and July are enrollment months. Families are deciding what their kid does in August, and that meant our attention went where it had to go: the programs themselves, not the newsletter about the programs. We were finishing the Edge AI Lab curriculum, tightening the activities pass, and doing the unglamorous work of making sure a kid who shows up in three weeks has a good afternoon, not a rough draft of one.

Writing a blog post takes an hour, maybe two. Getting a six-session robotics curriculum right so a fourteen-year-old doesn't spend session three staring at a broken environment setup takes a lot longer than that, and it doesn't announce itself the way a published post does. We chose the thing nobody sees over the thing everybody sees. We'd make the same choice again.

Why we're telling you this instead of just resuming quietly

We could have just started posting again and let the gap speak for itself. We didn't, for the same reason we don't do streak counters in the activities room — manufacturing the appearance of constant motion is a kind of lie, and we don't want to run this blog on the same trick we refuse to put in front of kids.

A library doesn't apologize for being closed on a holiday. It just says when it reopens and means it. So: here's when we reopen, and here's what's coming.

What's coming

Starting today, we're publishing weekly through mid-September. Not because a content calendar told us to, but because we have a genuine backlog of things worth saying and a rhythm that's easier to keep than to restart every few months. Over the next several weeks:

• What's actually in the free printable library, and why it costs nothing
• A plain guide to which of our four zones fits which kid
• What "age-appropriate AI" really means at 8 versus at 16
• What a mentor in our room actually does, hour to hour
• A parts list for a kid's first robotics build that isn't the Jetson series
• Why we don't grade the projects
• The questions parents ask us most, answered without the sales voice
• How we landed on four zones instead of one program
• What changes for a kid the moment a stranger — not a parent, not a grade — uses the thing they built

That's the list. We're not going to pad it and we're not going to skip a week because something got interesting elsewhere. If we go quiet again, we'll tell you why, the same way we're telling you now.

The actual point

The point of a blog like this one isn't to prove we're busy. It's to think out loud, in public, about the decisions behind the place — the ones that don't fit on a program page. A month of silence followed by a vague "we're back!" post would have skipped the only part worth reading: the reasoning.

So: we're back, we know why we left, and we'd rather tell you the boring true reason than a more interesting false one.