AI doesn't make you a dev. Fundamentals do.

We are surrounded by software that nobody understands.

Open any modern app. Open the codebase. Open the dependency tree. Then ask the engineer who shipped it what happens when the bytes leave the function call. Most won't know. Some won't care. A few — the ones we want to talk to — will care a lot, and that's the population this site is for.

The autocomplete generation

A whole generation of devs grew up with autocomplete that finishes their thoughts before they finish thinking. It's a remarkable tool. We use it. We're not anti-AI.

But there's a difference between using a tool and being one. The tool that writes your code so fluently you stop noticing what it's doing has stolen something from you — the slow, painful, frustrating, irreplaceable process of understanding.

You don't learn architecture by reading generated code. You learn architecture by writing wrong code, watching it crash, debugging line by line until you grasp why the universe punished you.

What gets cut when you optimize for speed

Bootcamps optimize for the demo: a working app in 12 weeks. AI tools optimize for the next token. Tutorials optimize for the “30 days” promise on the thumbnail.

All three optimize away the same thing: the mental model. The picture in your head of where memory lives, when the GPU is idle, what the compiler does with that loop, how the kernel schedules your thread.

That picture is the fundamental. Everything else is grammar.

Why we exist

Zero Engine teaches the picture. Slowly. Densely. From scratch. Without an engine, without an AI copilot, without a shortcut.

Forge — our first course — covers C++, OpenGL, and Vulkan. Not because game dev is the only place fundamentals matter, but because game dev is the place where fundamentals can't hide. The frame budget is 16ms. The GPU doesn't care about your abstraction layer. If you don't understand the machine, the machine wins.

Lab Notes is the slow-drip essay series. Engine internals. Patterns AI hasn't learned to fake. Things we wish someone had written for us five years ago.

And someday, when the code is good enough that we'd want to read it ourselves, we'll open-source the engine.

What this isn't

We're not anti-AI. We use Claude every day. We'll teach you how to use it well — by giving you the foundation it can't.

We're not gatekeeping. The fundamentals are public knowledge — Hennessy and Patterson, the Vulkan spec, the Linux kernel source. We're building the curated path to them, in the order that works.

We're not promising fast. The opposite. If “hardcore” on the thumbnail repels you, we're not the brand for you, and that's fine.

Who this is for

Devs who've already shipped some software and know the satisfaction of actually understanding a bug. Senior engineers who can feel themselves drifting toward AI dependency and want to pull back. Career-changers who are willing to spend three months learning the machine instead of three weeks learning a framework. Game-dev hopefuls who refuse to limit themselves to Unity dropdowns.

If that's you, you're early. Welcome.

— Zero Engine