Our purpose

Stay sharp when shipping gets easy

Agents draft and merge faster than ever. Tech Professor exists so the people who ship still learn what went out, on purpose, from the real code.

The problem

Fast merges, thin understanding

It's never been easier to ship. Skim a plan. Click Approve. An agent writes the feature. The PR is green. Merge.

The cost isn't speed. It's that nobody had to think through the change. Over weeks that softens into habit. Over months you can click your way through a codebase you no longer understand. You're still "productive," but you're no longer learning.

Continuous learning used to be optional. When agents do most of the drafting, it's how you keep the craft, not just the merge.

The moment of truth

You approved the plan. Do you understand what shipped?

The tradeoffs. The edges. The lines that will matter in the next incident. If the answer is "I skimmed it," the thinking never happened.

What we believe

Four commitments we build against

Continuous learning is the job

When agents draft most of the code, staying sharp is how you remain an engineer instead of someone who only clicks Approve.

Agents draft. You understand.

Agents are fine for writing the first pass. They are not a substitute for knowing what shipped.

Understanding has to be earned

Skimming a plan is not learning. Tours, quizzes, and flashcards make you do the work that makes knowledge stick.

Teams learn what they merge

A green check is not shared knowledge. The change only lands when the people who ship it can reason about it.

What we build

Learning you can't fake

Point Tech Professor at a repo, a PR, or your docs. It writes a guided tour, a quiz, and flashcards based on the real files that matter.

Tours: walk the real files step by step.
Quizzes: prove you can reason about the change, not just skim it.
Flashcards: keep the hard parts from fading after the PR merges.
Tutor & Verify: ask in context, and run Verify when you want to know if material still matches the code.
MCP: the agent that shipped the change can turn it into the course your team takes. It helps teach; it does not replace understanding.

What we are not

If a surface rewards skim-and-click, we've drifted

Not AI docs that replace reading the code

We ground learning in the real lines. We do not summarize them away.

Not a chat that answers so you never struggle

The Tutor helps you reason. Quizzes and tours still make you earn the understanding.

Not a replacement for review

We make review stick as learning, so the next incident is not the first time you really look.

The team

Built by one engineer who felt the fog

Vilfred Sikker Dreijer is building Tech Professor so people who ship with agents can stay sharp — and review doesn't have to be the boring bottleneck.

Meet the team

Keep understanding what you ship.

Point Tech Professor at a repo or PR and start with a tour.