Shipping got easy. Knowing what you merged is still on you. Point this at a repo or a PR. You get tours, quizzes, and flashcards from the real files.
Tours, quizzes, playgrounds, exams, flashcards. A course if you want them in order.
A course is an ordered set of tours, quizzes, playgrounds, and exams. Same material for everyone. Each person has their own progress.
How should the charge API make retries safe?
An exam mixes multiple-choice with playgrounds. You have to reason about the change and make the code work.
Each run moves through reading the diff, scanning the repo, planning, generating, and saving. Jobs keep running if you leave.
A team is a shared space. Everyone works through the same sessions. Each person keeps their own progress.
New members join as Readers. Free, no seat required. They get their own account and their own saved progress.
A public team is a community. Anyone can join as a Reader. No seat required.
A green check is not understanding. Tech Professor turns the diff into a quiz or a tour. You can see who has been through it.
Quiz, tour, playground, and exam for this change.
The Tutor searches the repo, opens the files, and cites the line. It will not take the quiz for you.
auth.uid(), so answers only ever belong to you. Connect the Tech Professor MCP server. Your coding tool can turn a merged change into a tour, a quiz, and a course. It writes the material. You still do the learning.
Leaderboards and coverage maps for a private team or a public community.
Sign in, or browse public communities as a guest.
Tech Professor uses storage that is strictly necessary to sign you in, keep your session, process payments and remember your preferences. These are always on. We ask before enabling anything optional. See our Cookie Policy and Privacy Policy.