Our purpose
Writing code got cheap. Understanding it did not. What you learn from this change decides how good the next one is.
Tools can write the change, and more and more they can check it too. That settles whether it is right. It does not tell you what it does.
Development is not one loop that ends in approve or reject. What you learn from this change shapes the next one. It changes the next idea you have, the next question you ask, and the direction you pick.
Skip that, and the system moves on while your picture of it stays put. That gap is cognitive debt. Like technical debt, it is fine for a while. Then one day you cannot take part in your own codebase.
Writing code is no longer the slow part. Knowing what it does, and whether it is right, is.
A clear picture of the code lets you spot the better design, ask the sharper question, and steer the next change yourself.
Skimming a plan feels like learning, but it isn't. Tours and quizzes ask you to follow the code and answer for it.
A green check means the tests passed. Building together takes the same names and the same picture of the system.
Point it at a repo, a PR, or your docs. It writes tours, quizzes, and flashcards from the actual files, so what shipped becomes what you know.
Everything points back at real lines. We don't summarize them away.
The Tutor helps you work through a question. Tours and quizzes still leave the thinking to you.
Review decides whether the change is right. We help you understand it, so an incident is not the first time anyone reads that code closely.
The team
Tech Professor is built by Vilfred Sikker Dreijer, for people who ship code and want to keep learning it.
Point it at a repo or a PR and read the tour it writes.
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.