The team
Vilfred Sikker Dreijer
One person building Tech Professor. No team page theater — just me, and why I started.
I felt myself drifting into brain fog
Agents took over more of the drafting. Shipping got easier. Staying sharp did not.
I built Tech Professor because I could feel myself slipping out of the loop. Agents write faster than I review. I wanted a way to stay in the loop — to keep improving, learning, and challenging myself.
That, to me, is the most important thing for staying relevant as an engineer while agents keep getting better. The tools improve at a rapid pace. They are not perfect machines. They make mistakes. Those mistakes are for humans to catch.
But if an agent writes the code and builds the tests, how do I keep up enough to tell it when it got something wrong? How do I improve so I can steer it better?
Review and learning are the slow part now
Code review is becoming the choke point. Learning and giving feedback are too.
So the second motivation is simple: how do we make understanding systems more engaging, while also sparking new ideas and concepts — instead of treating review as a grind you race through?
My goal for Tech Professor is to push on both fronts: keep honing my skills, and shrink the bottleneck for understanding systems.
I'm one person. Feedback helps.
If you have ideas, bugs, or just want to talk about the problem — I read everything that lands here.
In the app
Signed in? Open your profile menu in the sidebar and hit Give feedback.
Stay sharp when shipping gets easy.
That's the purpose. The product is how I'm trying to live it.
Your privacy
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.