writing ·
From lesson plans to evals
Placeholder essay. Replace with your first real post; this one exists so the layout has something to show.
This is a sample post. Delete it or rewrite it. Every essay is a Markdown file in
src/content/writing/.
A good lesson plan starts from the end: what should a student be able to do when the bell rings, and how will you know? You write the exit ticket first and work backward.
A good eval suite works the same way. Decide what “correct” looks like for the documents that matter, write those cases down, and only then start changing prompts or models.
What carries over
- Write the check before the lesson. Ground truth first, pipeline second.
- Watch the quiet kids. The failures that matter rarely show up in the aggregate metric.
- Reteach without blame. A regression is information about the system, not a verdict on the team.