Learning is a side effect. Building is the point.
There's no curriculum to complete or certificate to collect. You pick a direction, turn it into a real build with AI doing a lot of the heavy lifting, and learn exactly what you need exactly when you need it — while making sure you actually understand what you ship.
The builder loop
Every project — big or small — moves through the same loop, over and over.
How "Learn" actually works
Traditional tutorials teach syntax. We think the faster path is learning to direct AI to build with you, then reading, understanding, and owning every line before it ships — that's the real skill now, not memorizing a language.
Say what you want to build
No prior syntax knowledge required to start — describe the problem you're trying to solve, in Discord or to an AI assistant directly.
Turn it into a build spec
We're building a library of prompts members paste into Claude (or similar) that turn a rough idea into a concrete, scoped spec of what to build and learn. Coming soon — for now, ask in Discord and someone will help you shape one.
Build it, then verify it like an engineer
AI can draft the code. You still read it, test it, and defend it in review — that part isn't optional and isn't going away.
What we're building against
Every real philosophy has something it pushes back on. For us, it's these habits.
Tutorial addiction
Watching instead of building.
Framework obsession
Knowing a library, not understanding what it sits on top of.
Resume engineering
Building projects only because they look good to a recruiter.
Knowledge hoarding
Becoming skilled and refusing to teach it forward.
Blind vibe coding
Shipping AI-generated code you don’t understand and can’t defend in review.
Pick a direction. Start building.
Say what you want to build and someone will point you to where to start.