Engineer → Teacher

27 years building software.
Now I teach it, for the AI era.

Computer science for grades 9–12 and for professionals. Teaching, system design, mock interviews, and mentoring engineers and engineering managers.

Jacob Hite in an open-plan engineering office, rows of desks and monitors behind him and birthday balloons hanging from the ceiling.
Alchemy, 2022.
A room of children seated on the floor of a wooden schoolhouse in South East Asia, with two adults teaching at the front.
Volunteer teaching, South East Asia.
1999
BS Computer Science, CU Boulder
27 yrs
shipping software for a living
2011
moved to South East Asia
CELTA
certified in Chiang Mai, 2011
2026
switch from software engineering to teaching about it

What I do

Three rooms, one idea

Whichever room I'm in, the job is the same: get you from "I have no idea how this works" to "I built that, and I can tell you why it works." What that takes is different every time, so the structure below is a starting point, not a package.

The method

AI can write the code. It cannot own the decision.

So we don't teach students to "code with AI." We teach them to direct, inspect, test, and improve software that AI helped produce, whether that is Claude, ChatGPT or an agent inside Replit. This is the loop a project settles into. Click a stage. How much of it somebody touches in week one is a separate question; it grows with them.

1Observe2Specify3Design4Implement5Explain6Test7Review8Deploy9Learn

Stage 1 of 9

Observe a problem

Start with something that actually annoys somebody. Not "build a to-do app", but "my roommate keeps forgetting bin night."

Graded onCan you describe the problem without describing a solution?

AI can write the code. The person shipping it still owns the specification, the verification, the explanation, and the decision to release.

The through-line, whatever we build

Everything else

Have a look around