Show and Classic: How We Built a Platform That Teaches Anything by Doing
Two Ways to Learn, Both Broken
There are two default ways to learn something technical, and both fail in predictable ways.
The first is watch: a video course, a lecture, a slide deck. Someone who understands the thing explains it to you. It feels productive. It has a completion rate below 10%. You watch two lessons, get pulled back into work, and never return — and even if you finish, you've watched *someone else* build understanding, not built your own.
The second is read and ask: documentation, a textbook, or now an AI tutor you can interrogate. Infinite depth, available on demand. The failure is the opposite of video — there's no spine. You don't know what you don't know, so you rabbit-hole, get lost, or bounce off the wall of text before any intuition forms.
Watching is too passive. Open-ended depth is too unstructured. Most platforms pick one and call it a day.
We built Alset around a different idea: you don't pick. You braid them.
One Spine, Two Altitudes
Every Alset course has two altitudes, and a learner moves between them without ever managing a "mode."
Show is the spine — a visual, interactive path you can't get lost on. It owns the *mechanics you can feel*. You don't read that a language model predicts the next word; you type a sentence and watch it predict, one token at a time. You don't read that "temperature" controls randomness; you drag the dial and watch the same model go from boringly predictable to gleefully unhinged. You don't read the definition of regression; you grab a line with your cursor and drag it until the errors shrink. Show is a flight simulator, not a manual.
The rhythm is always the same: Watch → Steer → Drive. First you watch the mechanic happen. Then you steer it — move the slider, drop the point, pick the bucket. Then you drive it yourself on a fresh problem. By the end of a Show session you haven't memorized a fact; you've *operated* the thing.
Classic is the depth. It's the guided AI tutor, the real data files, and — for hands-on courses — a live sandbox where you write and run real code. Classic owns the *judgment you discuss*: when does this break, what does the benchmark not tell you, here's the messy real dataset, here's the trade-off nobody mentions. It's the room you step into when "I feel how this works" turns into "okay, but what would I actually do?"
Here's the key: these aren't competing modes the learner toggles between and has to manage. Show is the directed spine. Classic depth comes _to_ the learner, on demand, one concept at a time.
| Show | Classic | |
|---|---|---|
| Owns | Mechanics you *feel* | Judgment you *discuss* |
| Form | Visual, interactive: Watch → Steer → Drive | Guided AI tutor + real data files + live sandbox |
| Example | Drag the temperature dial; watch the model go predictable → wild | Open the real dataset; work the messy edge case with the tutor |
| Role | The directed spine — you can't get lost | Depth that comes to you on demand |
Peek and Dive: Depth That Comes to You
The braid happens at the level of a single idea, through two affordances.
A Peek is reading depth that stays in your flow — a definition, the real number behind the visual, a one-paragraph "here's what's actually happening." You felt the temperature dial; the Peek tells you it's literally re-sampling the model's probability distribution, and that low temperature is how you get consistent classification. No context switch. You stay on the spine.
A Dive is a designed graduation. At a natural seam — right after you've *felt* something — a single button hands you into Classic at the exact relevant spot: the precise tutor step, the specific data file, already open. You just watched semantic search light up the nearest points on a meaning map; the Dive drops you into the real distance-metrics.json with the tutor, where you measure cosine similarity yourself and see why "the cat sat on the mat" and "a kitten rested on the rug" score nearly identical despite sharing no words. When you're done, one tap returns you to the exact beat you left.
The discipline matters: Peeks are everywhere; Dives are rare and earned — one or two per session, at the moments where "do it for real" is worth the trip. A Dive should feel like the same companion opening a deeper room, never like switching apps.
Why This Teaches *Anything*, Not Just AI
Here's the part that matters for where we're going.
The Show engine is built from a small set of interaction primitives that have nothing to do with AI. Strip away the subject and every Show beat is one of a handful of universal learning moves:
Those moves are how a person builds intuition about *any* system — a transformer, a thermal cycle, a balance sheet, a legal test, a supply chain. The visual grammar is domain-independent. So is the two-altitude braid: every subject has mechanics you should *feel* and judgment you should *discuss*, which is exactly the Show/Classic split.
That's not a thought experiment. The same engine — the same interactive Stage, the same kit of beats, the same Peek/Dive plumbing — already teaches five very different foundations:
| Course | A mechanic you *feel* in Show |
|---|---|
| AI Models Demystified | Type a sentence; watch it predict the next word token by token — then drag the temperature dial |
| Vector DBs & Embeddings | Drop a phrase on a "meaning map" and watch it pull toward its nearest neighbors |
| Data Science for AI | Grab a regression line and drag it until the errors shrink; watch a neural net turn pixels into "cat" |
| Prompt Engineering | Put a lazy prompt next to a crafted one and run both; roll a system prompt and watch it govern every reply |
| RAG in 60 Minutes | Slice a document into chunks, then ask your docs a question and get a cited answer |
When we built the Data Science course, the visuals were genuinely new — you're dragging regression lines and watching a neural network build features from pixels, not predicting tokens. Adding it cost a couple of new visual primitives and a lesson script. The engine — the spine, the two altitudes, the braid, completion, the certificate — came for free.
That's the whole bet. A new subject isn't a new platform. It's a couple of visuals and a script on top of an engine that already knows how to make someone _feel_ an idea and then _go deep_ on it. AI is where we started because it's what the market needs right now and what we know cold. It is not the ceiling.
What It Feels Like
A beginner opens "Vector Databases & Embeddings" — a topic that usually arrives as a wall of jargon about cosine distance and HNSW indexes.
Instead, they search a tiny store for "comfortable couch" and watch two engines disagree: keyword search finds nothing, meaning-search surfaces sofas that never use the word "couch." They watch products settle into clusters on a map — nobody programmed that. They drop their own phrase and see what it pulls toward. They run a real semantic search in their own words. Five minutes in, with zero math, they *get* it: meaning is a place, and search is finding the nearest dots.
Then, at the seam, a Peek tells them each dot is really a list of 768 numbers. And a Dive — if they want it — drops them into the real distance metrics with the tutor, to measure it themselves.
Intuition first, on a path they can't get lost on. Depth on demand, the moment they're ready for it. Never a wall of text, never a passive video.
The Bottom Line
Passive video doesn't stick because watching isn't doing. Open-ended depth doesn't stick because there's no spine. The answer isn't a better video or a smarter chatbot — it's an architecture that gives you both at once: a visual, interactive spine you can't get lost on, with real depth one tap away at every concept.
We built that architecture to be topic-agnostic on purpose. Today it teaches the AI skills teams actually need. The same engine is how we intend to teach everything else.
Five courses are live now. [Try one at academy.alset.app](https://academy.alset.app/enterprise) — your first is free.
Related articles
Why We Built an Open Platform for Hands-On AI Training
Video courses have a <10% completion rate. We built Alset so teams can create custom AI courses where employees learn by building real systems — not watching slides.
strategyWhy RAG Beats Fine-Tuning for Most Enterprise Use Cases
Fine-tuning sounds impressive, but retrieval-augmented generation solves 80% of enterprise knowledge problems with less cost, less risk, and faster iteration cycles.
engineeringThe Tool Use Pattern: How AI Agents Actually Work
AI agents aren't magic. They're a loop: the model decides which tool to call, your code executes it, and the result goes back to the model. Understanding this pattern is the key to building reliable AI systems.
Ready to build?
Explore our enterprise AI courses — build production systems with real enterprise data patterns.
Explore enterprise courses