Every feature I built for MathTabla was teaching me something. Almost none of it was making it past my own head.
That's what this blog is for.
The Problem With Building in Silence
When you're working alone on infrastructure — pedagogical or technical — the insights compound inside a single skull. Code comments catch some of it. Notes catch a little more. But synthesis doesn't happen until you're forced to explain yourself to someone who isn't you.
No forcing function meant no synthesis. No synthesis meant the why behind each design choice stayed fuzzy, even to me.
What to Expect
This isn't a marketing blog. It's a working log. Three things show up here:
- Pedagogical reflections — why specific design choices exist, grounded in what I learned in classrooms with students who'd already given up
- Technical deep-dives — how individual features work, including the bugs, the dead ends, and the parts I'm still unsure about
- Demo walkthroughs — short pieces tied to interactive prototypes you can actually touch
The Habit Stack
The trick is to attach writing to work I'm already doing:
- Build a feature.
- Write about what building it taught me.
- Publish.
Each loop forces one thing to become explicit that would otherwise stay implicit. The act of writing is the synthesis. Publishing is the commitment device.
If MathTabla is going to be educational infrastructure, the reasoning behind it has to be legible to someone other than me. This blog is how I get there.