Inside a Session
We start wherever the student is. Sometimes that's a calculus problem due tomorrow. Sometimes it's a question they've been carrying for weeks. I listen first.
Then we work the problem together, out loud, so they hear how an engineer's mind moves through complexity. Not just the answer — the thinking. The pauses. The wrong turns that teach you more than the right ones.
From the solution, we extract a model — a reusable mental framework the student owns. Then a few short reps. Not busywork. Just enough to make it stick. And at the end, one minute of reflection: what clicked, what didn't, what they want to carry forward.
Some days we're putting out fires. Some days we're building something new. And always, underneath everything, we're working on the person.
After the Session
The session ends. The work product doesn't. Every family receives a written summary of what we tackled, where the student stands, and what comes next — drawn from the full transcript by AI models I built, not from memory.
Students get something rarer: a worked-solutions packet. Every problem we solved together, typeset to publication quality — clean notation they can actually study from, not photos of a whiteboard.
And each semester, we sit down as a family: progress, goals, and whatever questions you're carrying. If something can't wait that long, we talk — anytime, on request.
Three Modes, One Mentor
When a grade is slipping, we stabilize. Problem talk-alouds, a structured weekly plan the student owns, reusable models that replace the nightly scramble. Panic drops. Grades rise.
When the fire is out, curiosity leads. Mini-courses on how CPUs actually work. Startup sprints. Logic labs. Nobody signs up for this part and nobody pays extra for it — it's what happens naturally when a curious kid works with a working engineer.
And always, we're building the person. The word for it is metacognition — thinking about your own thinking — and it's the thing I talk about with students more than anything else. The student learns to debug their own reasoning the way an engineer debugs a system: watch it run, find where it goes sideways, fix the pattern instead of the symptom. It's the inner operating system that outlasts any single class.
The Commitment
I keep this practice deliberately small — twelve families at most — because the work doesn't survive dilution.
Engagements are month to month. No contracts, no minimums. Real change still needs runway — and most families stay long-term — but they stay because the results earn it, not because paperwork holds them.
Sessions are weekly or twice-weekly, 50 minutes. The student owns their plan — my role is mentor, not manager. Parents receive a written summary after every session, a typeset packet of every problem we worked, and a semester review on progress and goals. If something can't wait for the semester mark, we talk — anytime, on request.
I respect your time. I ask you to respect mine. Twenty-four hours' notice for reschedules. Planning protects momentum.