@mcs@moderncoding.school / source / rss /
EN

One core. Two tracks.
Every exit is defended.

Every concept is published free, forever. We sell the with-you: the feedback, the lab, the gate, the credential you actually own.

Technical judgment,
without technical production.

Read, don’t write

Control flow, data flow, diffs, stack traces. Understand the code you didn’t type — and the autopsy of the one that died.

Specify

Turn a vague want into executable agent instructions a machine cannot misread.

Verify

Trust output you didn’t write — and prove it clears the bar before it ships anywhere near prod.

One core. Two tracks.
Every exit is defended.

The Core is four weeks. Pick a track and you add six (Track A) or eight (Track B) more. Every module exits through the gate — work is CONFERRED or it isn't.

CORE 4 weeks

Technical Judgment

The shared foundation: reading code you didn't write, specifying work for agents, verifying output, and clearing a production bar.

  • Read a diff and a stack trace
  • Spec work an agent can execute
  • Verify output against a source
  • Clear the production bar
TRACK A 6 weeks

Production & Self-Host

Deploy and operate a real system on your own metal: domains, TLS, secrets, backups, logs, rollback.

  • Own the deploy and the fire
  • Logs · monitoring · rollback
  • Secrets and TLS without a SaaS
  • Exam: find and fix a real bug
TRACK B 8 weeks

Agent Company

Orchestrate agents behind verification gates with real unit economics — and no platform or model lock-in.

  • Verification gates that actually gate
  • Token cost and model routing
  • Self-hosted defensible models
  • Exam: a business that ran 30 days

How the school runs.

Software does the first pass of everything; one human owns the judgment. Every mechanic is the school eating its own cooking.

Incident Days

We inject real failures into your workspace — a leaked secret, a runaway agent loop. You diagnose under time pressure.

Rubric-as-code

The gate: automated checks + agent first-review + human sign-off. First-pass feedback in minutes, not days.

The signed credential

Your diploma is a cryptographically signed artifact on your own domain — verifiable, federated, owned by you.

Run on your metal

The whole stack is FOSS and self-hostable. Learn to operate it without renting anyone's cloud or trusting anyone's model blindly.

Curriculum questions

Can I do just the Core?
Yes. The Core exit is a standalone gate. You receive a CONFERRED: Technical Judgment (Core) credential. It's a real credential and the prerequisite for both tracks.
What's the time commitment?
Plan for 10–15 hours per week. Core is 4 weeks; Track A adds 6; Track B adds 8. Incident Days are unscheduled — they happen during the lab and last 2–4 hours.

Ready to clear the bar?

18 seats in the founding cohort. The application is the first exercise.

Apply