About

I teach secondary Computer Science, and I hold a Masters in Education Technology. Most of what's on this site started the same way: a classroom problem that an existing tool didn't solve, built during a prep period and tested on thirty students who weren't shy about telling me what didn't work.

That's the constraint I design under. A tool that's pedagogically sound but takes ten minutes to explain doesn't survive a fifty-minute period. A tool that's slick but doesn't change what a teacher can see or do in the room isn't worth building. The projects here sit at that intersection on purpose — each one names the classroom problem before it names the stack.

My students are old enough to handle a real tool, and quick enough to abandon a clunky one by the second week.

Outside the classroom, I build in whatever the problem calls for — vanilla JavaScript, TypeScript and React, a Python script — but always as something portable: no login tied to my school's account system, no server only I hold the keys to. A tool built to leave the building is a tool another teacher, student, or maker could actually pick up and use.