# Teaching Method

Canonical page: https://antern.co/teaching-method/

## Summary

Antern teaches participants to feel the problem before learning the solution, reconstruct why ideas were invented, build systems, challenge AI output, explain decisions, and verify work under ambiguity.

The core principle is: output is not understanding.

A participant understands an idea only when they can explain it, modify it, defend it, rebuild it, and know when it fails.

## Teaching Philosophy

Participants learn the reason an idea exists before they learn the name of the idea.

Most AI courses compress knowledge into lists of tools. Antern teaches the chain of reasoning: problem, constraint, invention, implementation, evaluation, and consequence.

### Problem before vocabulary

Participants do not begin with names of algorithms or frameworks. They begin with the problem that forced an idea to exist, then reconstruct why the method became necessary.

### Intuition before notation

The sequence is problem, intuition, mental model, mathematics, implementation. The goal is for participants to feel that they could have invented the idea themselves.

### Projects are the curriculum

Builds are not practice after the lesson. The build is where the lesson becomes real: data issues, missing context, unclear requirements, bad evaluation, and product tradeoffs appear immediately.

### Systems over isolated tricks

AI and ML are taught as systems: data, context, retrieval, models, tools, evals, deployment, monitoring, cost, user behavior, and business consequence.

## Session Architecture

Every serious topic is taught through friction. Participants encounter the failure, reconstruct the invention, build the system, and then defend their choices.

The loop is:

1. Feel the failure
2. Recover the history
3. Build the mental model
4. Make it mathematical
5. Implement under constraints
6. Explain and defend

## Human-AI Verification

AI should amplify thinking, not replace thinking.

The teaching method trains participants to use AI aggressively while still owning the reasoning. AI can propose, code, summarize, or critique, but the participant must frame the problem, challenge the output, verify evidence, and decide what ships.

The verification flow is:

1. Human frames the problem
2. AI proposes or builds
3. Participant challenges the output
4. Evidence is checked
5. Failure modes are named
6. The work is revised or rejected

## Competence Ladder

The target is operator-level judgment.

- Order Taker: accepts AI output because it sounds confident.
- Mechanic: can catch local technical mistakes and make the artifact work.
- Operator: understands consequences across users, systems, money, time, risk, and maintainability.

## Learning Mechanics

The experience is built around repeated loops that make thinking observable: challenge, build, test, explain, publish, and revise.

Learning mechanics include root-cause sessions, productive failure drills, self-explanation checkpoints, AI challenge reviews, live system builds, and proof-of-work publishing.