AI writes more of your code every year. Nobody told the job. It still expects you to debug the deadlock, rebase the branch, read the query plan, and know exactly why the test went green.
Reading the call stack/printf and scanf/Commits done well/A test runner that scales/Finding the leak WSL on Windows/Object files and translation units/The doubly linked list/Pipes/Debugging in containers/Reading the call stack/Control flow/Commits done well/Fixtures and lifecycle/First inserts/Request data/The RabbitMQ listener/Debugging in containers/Reading the call stack/Control flow/Good commits/Parametrize/Inserting rows/Query parameters/Scheduled jobs/Debugging in containers/Stepping through code/Functions and arrows/Commits done well/Testing hooks/The box model/Error states/State/Vite/Reading the call stack/Arrays: list and map in one/Commits done well/The RefreshDatabase trait/Semver constraints/Controllers/Models/First inserts/Resource collections/XSS in Blade: escaped vs raw/Two corpses, one killer/Build it for real/The changelog that cannot lie/No pushing to debug/Make it real/Who wins/Apply the plan, not the config/SCCs versus pod security/The dev environment/
Reading the call stack/printf and scanf/Commits done well/A test runner that scales/Finding the leak WSL on Windows/Object files and translation units/The doubly linked list/Pipes/Debugging in containers/Reading the call stack/Control flow/Commits done well/Fixtures and lifecycle/First inserts/Request data/The RabbitMQ listener/Debugging in containers/Reading the call stack/Control flow/Good commits/Parametrize/Inserting rows/Query parameters/Scheduled jobs/Debugging in containers/Stepping through code/Functions and arrows/Commits done well/Testing hooks/The box model/Error states/State/Vite/Reading the call stack/Arrays: list and map in one/Commits done well/The RefreshDatabase trait/Semver constraints/Controllers/Models/First inserts/Resource collections/XSS in Blade: escaped vs raw/Two corpses, one killer/Build it for real/The changelog that cannot lie/No pushing to debug/Make it real/Who wins/Apply the plan, not the config/SCCs versus pod security/The dev environment/
01 / what this is
Expected Learning builds hands-on developer training that lives inside
VS Code. No videos. No sandboxes pretending to be computers. You work in
your own editor and the real tools grade you.
A real debugger watches your breakpoints. A real
database checks your queries. Real git reads the history you leave behind.
When it says you can do it, you can do it.
5 products, 857 lessons
02 / how grading works
03
Three steps, and only one of them is ours
step 01
Do the work
Open the lesson in VS Code and write the fix, the query, or the test - in your own editor, with your own tools.
step 02
The real tool checks it
The debugger, the test runner, or the real service your code talks to decides pass or fail - not a string match on your keystrokes.
step 03
Hints, then the solution
Stuck lessons escalate through hints before the reference solution unlocks - spoilers are earned, not browsable.
03 / the products
Expected Learning for C
C / Debugging with GDB / Your first breakpoint
app.c
#include <stdio.h>
staticintapply_discount(int total, int percent) {
return total - (total * percent) / 100;
}
staticintcheckout(int subtotal) {
int total = apply_discount(subtotal, 10);
total = apply_discount(total, 10);
return total;
}
intmain(void) {
printf("total: %d\n", checkout(100));
return0;
}
mainPaused on breakpoint - line 10C
a real ExpectedC lesson, dramatized and sped up - the debugger, the goals, and the pass/fail here are the same mechanism the shipped VS Code extension runs. Built for VS Code today; see the JetBrains design study for what this looks like sketched inside IntelliJ.
Expected Learning for C
TESTED
Memory, the debugger and the build - graded by real gdb, valgrind and ASan.
No account. No card.. the free tier makes zero network calls, answers ship encoded and are released one failed attempt at a time, and your progress is a local file you can read and delete. no accounts, no telemetry, no subscription.
Every product ships its free lessons inside the extension. Nothing to
activate, nothing to cancel, nothing sent anywhere.
Watchpoints: break when memory changes Linux/Windows only/Functions properly/Two kinds of merge/Testing the failure paths/Uninitialized memory WSL on Windows + macOS/make: the first Makefile WSL on Windows/A hash table/stat, directories, the filesystem/Kubernetes deploy/Conditional breakpoints/Encapsulation/Two kinds of merge/Black-box vs white-box/Aggregates/Validation/Consumer groups/Kubernetes deploy/Watch expressions/Dunder methods/Fast-forward merge/Mock objects/GROUP BY and aggregates/Validation with Field/Concurrent tasks with gather/Kubernetes deploy/Conditional breakpoints/Destructuring/Two kinds of merge/Mock Service Worker/Positioning/Storage: cookies, localStorage, and when/Lists and keys/Bundling/Watch expressions/Named arguments/Two kinds of merge/Asserting JSON structure/The PSR standards that matter/Blade basics/Eloquent basics/Aggregates/Rate limiting/Gates/It is always DNS/Leave the toolchain behind/If it is red, it does not leave/One red leg must not hide the others/Declare three of them/One label truth/The graph does the ordering/Enterprise topology forensics/Into the cluster/
Watchpoints: break when memory changes Linux/Windows only/Functions properly/Two kinds of merge/Testing the failure paths/Uninitialized memory WSL on Windows + macOS/make: the first Makefile WSL on Windows/A hash table/stat, directories, the filesystem/Kubernetes deploy/Conditional breakpoints/Encapsulation/Two kinds of merge/Black-box vs white-box/Aggregates/Validation/Consumer groups/Kubernetes deploy/Watch expressions/Dunder methods/Fast-forward merge/Mock objects/GROUP BY and aggregates/Validation with Field/Concurrent tasks with gather/Kubernetes deploy/Conditional breakpoints/Destructuring/Two kinds of merge/Mock Service Worker/Positioning/Storage: cookies, localStorage, and when/Lists and keys/Bundling/Watch expressions/Named arguments/Two kinds of merge/Asserting JSON structure/The PSR standards that matter/Blade basics/Eloquent basics/Aggregates/Rate limiting/Gates/It is always DNS/Leave the toolchain behind/If it is red, it does not leave/One red leg must not hide the others/Declare three of them/One label truth/The graph does the ordering/Enterprise topology forensics/Into the cluster/
05 / where it stands today
Receipts
PASS the paid edition is encrypted, and the whole encrypted path is CI-proventhe full curriculum ships as an encrypted pack that only unlocks under your licence; CI walks every paid lesson the way a buyer would - decrypt, grade, done - on Windows, macOS and Linux, all 158, so it is ready the day the store opens
PASS every gradeable lesson carries a CI solvability proof148 lessons verified stub-fails-solution-passes, 0 failures; the other 17 are guided browser and observation lessons, skipped by design, not by accident