One hour after school. One real concept — AI, coding, hardware, or cybersecurity. Something to actually show for it when they get home.
Hi 👋 I'm Zach, and I am a software engineer turned high school computer science teacher. I got into education because I not only wanted to help students understand the technology they use every day. Coding, electronics, robotics, design — the stuff that connects classroom skills to actual jobs and actual life. I love it, and I'm good at it.
CubCode grew out of a gap I kept noticing: kids are surrounded by technology but most of them have no idea how any of it works. Not in a "you should learn to code" way — just basic understanding. That AI learns from examples. That hardware and software depend on each other. That encryption is math. Things that change how you move through the world.
So I built a program around those ideas. One concept per session. Something to build. Something real to explain at dinner. I bring everything — the laptops, the kits, the curriculum. Your school just needs to let me use a room (and maybe the wifi).
Each session stands alone — kids can attend any or all. Every one ends with something they built and something they understand.
Students train an AI model on their own gestures, then break it on purpose with bad training data. The goal isn't a polished product — it's the moment they realize AI isn't magic. It's pattern matching on examples they provided.
Starting from a template, students build a playable game — movement, score, win condition, all theirs. The template handles the blank-page problem so the session is spent actually building, not staring.
Students collectively describe a website while I type the prompts. They quickly discover that "make it cooler" produces nothing, but precise instructions produce exactly what they wanted. Language turns out to be the skill.
Students write code and watch a physical LED blink, a buzzer play a tune, or a sensor detect their hand. Every kid has a slightly different reaction to that first moment when something on the screen makes something real happen.
We start with paper — encode a message, swap with a classmate, try to crack it. Then we write a Python script that tries all 26 shifts at once and finds the answer in a fraction of a second. That's the lesson: not the code, but the scale.
New sessions get added as schools ask for them. If there's a concept your kids should understand and it isn't on this list yet, tell me. That's how this list grows.
Have a topic in mind that isn't listed? If it fits the format, I'll build it. Get in touch →
Schools don't pay anything. Families sign up and pay per session. I bring everything else.
One conversation — email or phone. We agree on days, which room, and when to start. That's it for your end.
A flyer goes home in backpacks. Parents sign up and pay directly through me. Your office manages nothing.
I arrive with my own laptops, hardware kits, and a plan. Students build something real every session.
CubCode runs after school in your building. Families pay $35 per session directly to me. Your school doesn't pay anything and doesn't manage anything.
I'm a licensed Colorado teacher. I've been teaching technology to high school students for years — robotics, electronics, coding. I'm background-checked and insured. I bring my own equipment. Nothing runs on your school's network.
If you want to talk it through, email me. If you want to just say yes and figure out details later, that works too.
No packages, no tiers. $35 per student per session. Families pay directly — your school pays nothing.
Whether you're a principal, an enrichment coordinator, or a parent who wants to ask if CubCode can come to your school — just reach out. I'm easy to talk to.