a manifesto · the page where I tell you, plainly, what we're trying to do here

What ZeroCourse Is For.

A letter, not a sales page. Read it slowly. If a paragraph in here makes you flinch — in either direction — that's information.

read
§01
The premise
The market sells short arcs. Engineers live long ones. Most platforms are optimised for the wrong axis.
§ 01 · the premise

Built for the longer arc.

Most platforms that teach engineers are optimised for one outcome — usually a job, sometimes a certificate. That's a fine outcome, but it's not the whole picture of an engineer's life, and it stops being useful the moment the learner outgrows it.

ZeroCourse is built for the longer arc. It's a place a learner can come to at twenty, return to at twenty-eight when they're scared of being replaced, return to again at thirty-three when they want to leave their job and build something of their own, and still find it speaks to them at forty-five when they want their work to count for something larger than the deliverable.

To do that honestly, we have to teach more than syntax.

A platform that grows with you, instead of aging with the job market.

§02
Who this is for
Five archetypes — not five products. Five stops on the same path. You'll likely move through several.
§ 02 · who this is for

Five readers. One platform.

No archetype is hidden, no archetype is primary. You'll likely move through several of these over a career.

01
The absolute beginner.
You've never written code. You're here because you decided this is something worth learning, and you want to learn it from people who'll teach it honestly. We start where you are, and we don't pretend it's easier than it is.
02
The student.
University gives you a degree; we want to give you employability, and the depth that will still matter in ten years.
03
The mid-career engineer.
You've shipped for years on assigned tasks. You never quite learned the principles underneath, and now AI is getting better at what you did. We help you become the kind of engineer who's harder to replace, not easier.
04
The would-be founder.
You want to leave the job and build a SaaS, a consultancy, a product, a small business. The technical skills are part of it; the rest is communication, sales, money, negotiation, the politics of running a thing. We teach all of it.
05
The engineer who wants leverage.
You want your work to matter — to a community, to a movement, to the planet, to a problem worth caring about. Depth and conscience compound here.

Not every learning path on the platform serves every archetype. Some paths are foundations and assume nothing; others are advanced and assume you've done the foundations. Each path tells you, plainly, what it expects you to know before you start. That honesty is part of the contract.

§03
What we believe
Seven beliefs. Each one shapes a decision someone else might make differently. Each one is load-bearing.
§ 03 · what we believe

Seven things. Load-bearing, all of them.

Most platforms tell you their values in adjectives. "Excellence. Innovation. Community." Here are seven beliefs in sentences — each one shapes a real decision.

1
Depth beats fluency.

Anyone can prompt an AI. The differentiator is judgment — knowing when the AI is confidently wrong, knowing the tradeoff it didn't surface, knowing the principle underneath the abstraction. We're built around that judgment.

2
We don't redo work that's already done well.

For most technical topics, world-class free resources exist — MIT OpenCourseWare, the canonical books, the rare YouTube channels that teach honestly. We're not going to rewrite those in our voice and pretend we improved on them. What we add: framing that motivates, the engineer's-lens connection from the topic to your actual work, and — most importantly — the pedagogy that verifies you actually learned what the resource taught.

3
Where original teaching is needed, we do it.

The non-technical curricula — communication, negotiation, money, politics at work, discipline, the craft of teaching — don't have canonical resources written for engineers. So we author them. Politics at work as a multi-agent system with private state. Negotiation as API design under uncertainty. Imposter syndrome as signal versus noise. This is where we teach, in our voice, because nobody else is.

4
Pedagogy is the through-line.

Spaced repetition, Bloom's taxonomy, deliberate practice, the Feynman technique, growth mindset, scientific debugging — applied invisibly across every curriculum. You won't see the jargon. You'll feel the difference. Whether you learned a topic from us or from MIT, our pedagogy verifies you got it, schedules review when memory would otherwise fade, and tells you when you're ready to move forward.

5
The non-technical skills aren't soft.

Communication, negotiation, money, politics, discipline, the craft of teaching — these decide more careers than any algorithm. We treat them as load-bearing infrastructure for a long working life, not as garnish.

6
The engineer's job is partly civic.

What gets built, who it's built for, whose attention it captures, whose data it stores, whose work it replaces — these are technical questions and they are also questions of conscience. We don't separate them. The civic dimension shows up where the engineering does.

7
The goal is to make ourselves unnecessary.

We want you to leave with the skills, the questions, and the agency to keep growing without us. That's not a marketing line; it's a pedagogy. An engineer who needs a tutor forever didn't learn.

An engineer who needs a tutor forever didn't learn.

§ 04 · what we won't do

A short list of explicit refusals, kept short on purpose.

Because what a platform refuses says more than what it offers.

We won't help you build mass surveillance, predatory finance, manipulative attention engines, weapons targeting, or systems designed to harm people who can't consent to being harmed.
We won't promise you a job. We promise you the skills and the discipline that make jobs more likely. The market does what the market does.
We won't promise you'll succeed as a founder. We promise the curriculum that gives you a real chance.
We won't pretend AI will leave the field unchanged, and we won't pretend it will replace everyone. Both are evasions. The truth is more useful.
We won't lecture. The civic register on this platform is matter-of-fact. We trust learners to bring their own conscience and meet good questions honestly.
§05
How we teach
Two registers, no pretending. The pedagogy is the same; only the source of the teaching varies.
§ 05 · how we teach

Two registers, and we're honest about which is which.

register 01 · we are a guide
on most technical topics

We motivate the topic — why it matters, what it sets up, what your work has been quietly assuming about it. We point you to the specific resource that teaches it best (often free, sometimes paid, named honestly either way). We tell you what to focus on and what to skip.

Then you go consume the resource. When you come back, our AI tutor (Bodhi) checks if you actually learned it — by asking you to explain in your own words, work problems, ship a project. If there are gaps, Bodhi names them. If you're ready, you move forward.

register 02 · we are the teacher
on the non-technical curricula

Politics, negotiation, communication, money, discipline, imposter syndrome, the craft of teaching — these don't have canonical resources written for engineers. So the curriculum, the prose, the worked examples, the engineer's-lens framings come from us.

The pedagogy is the same — Bodhi verifies, spaced review consolidates, projects integrate — but the source of the teaching is here, in our voice. Because nobody else is going to write it.

verification is ours regardless of register
A learner who skips our framing and goes straight to MIT OpenCourseWare can come back, and Bodhi will assess their understanding the same way as the learner who read every word we wrote. The platform measures what you know, not what content you consumed.

You'll write real code on real GitHub repositories, run real tests, get reviewed. You'll be assessed against real cognitive levels (Bloom's), not score totals. You'll revisit concepts at intervals tuned to how memory actually works. You'll be asked to explain things in your own words — which is the moment you find out whether you actually understand them. The infrastructure stays the same; only the source of the teaching varies.

§06
Who runs this
One person, named, with a point of view. You should know whose values you're absorbing.
§ 06 · who runs this

One person. One voice. A name attached.

ZeroCourse is built and edited by The Engineer — a software engineer with ten years of shipping, building this for the version of himself who was starting out, and for the engineers around him now refusing to be made obsolete. The voice on the platform — the tutor, the curriculum, the choices about what to teach and what to refuse — comes from one person with a clear point of view. That's deliberate. You should know whose values you're absorbing.

The civic and pedagogical foundations draw on traditions I find most honest. None of these are decoration. They shape every page.

Buddha
Upaya — meeting the learner where they are.
Ambedkar
Education is empowerment, not dependence.
Feynman
Understanding through explanation.
Vygotsky · Bjork
How memory and difficulty actually work.
Dweck
Growth as language.
— signed
The Engineer
Ten years in. Still shipping. · founder & sole editor of ZeroCourse
§07
The contract
Six promises we'll keep. Three we honestly refuse to make. The rest is yours.
§ 07 · the contract

If you stay with us, we promise.

01A curated path through the world's best learning resources — free where possible, paid only when the paid resource is genuinely the right one.
02Original teaching where original teaching is needed — primarily on the non-technical skills nobody else writes for engineers.
03Verification that you actually learned what you set out to learn — through Bodhi, through projects you ship to real repositories, through spaced review that catches what fades.
04A tutor that won't write your code for you and won't pretend you don't have to do the hard part.
05Honest framing of where the field is going, including the parts that are scary.
06The questions worth asking — about your craft, your career, and the work you put into the world.

We don't promise enlightenment, riches, or a guaranteed outcome. Those are honest promises to refuse.

— welcome

If that sounds like the kind of platform you want to learn on, welcome.

There's a lot of work ahead of you. Most of it is yours to do. We'll be here.

— signed
— The Engineer
May 9, 2026