code-quiz

Code Quiz

Adaptive quiz on a curriculum section. Pulls from learn/internals/quiz-bank.md; generates fresh questions from source when the bank is exhausted or the user has seen the existing ones.

The quiz bank is a working document. APPEND new questions when generated. EDIT existing questions or answers when the user gives a reasonable answer the "correct" answer doesn't cover. Treat the bank as a living resource that improves with each session.

Entering a session

1. Resolve the section: explicit ID (/learn quiz 1.3), --full for the whole curriculum, or default to the next unchecked section.
2. Load the section's questions from the bank, the section text from curriculum.md, and the source files it cites.
3. Plan 5–7 questions for a single section, more for --full.

Question palette (mix; do not name the types to the user)

Pull from several of these in any quiz. The user should experience a varied, well-crafted set — not a labeled taxonomy. Never say "this is a conceptual question" or announce the type; just ask.

Examples below span several libraries deliberately — the palette is domain-agnostic. Draw real questions from the codebase being quizzed.

• Recall — vocabulary. "What does Session.execute() return in SQLAlchemy 2.x?" "What's the default timeout for httpx.Client?" Fast confidence-builders.
• Conceptual — mental model. "Why does pydantic validate at construction time instead of on access?" "What invariant does Session.begin() preserve about transaction state?"
• Predictive — cause and effect. "If you drop pool_size from 5 to 1 under concurrent load, what changes?" "What happens on the first call to an @lru_cache'd function vs the second?"
• Diagnostic — error model. Show plausibly broken code: "This pydantic model raises ValidationError on construction. What's wrong?"
• Applied — transfer. "You want to add request signing to every call on an existing httpx.AsyncClient. Sketch how."
• Architectural — design intent. "Why does pandas split merge and join into two methods?" "Why does FastAPI use dependency injection for auth rather than middleware?"