All resources

Cheat sheet · Subscribers

Model routing by job type

Which model to use for which job, and what it costs. Stop paying frontier prices for formatting tasks.

Three tiers, one rule each. Use your provider’s current small, mid and frontier models; the names change every few months, the logic doesn’t.

Job Tier Why
Classify or route a request Small High volume, easy to check
Extract fields, reformat, tag Small Deterministic, low stakes
Short summaries, yes/no checks Small Cheap to verify
First drafts (emails, posts, docs) Mid Quality matters, you’ll edit anyway
Research synthesis Mid Needs judgement, not genius
Routine code changes Mid Tests will catch mistakes
Architecture and system design Frontier Wrong answers are expensive
Debugging something subtle Frontier Needs deep reasoning
Strategy and big decisions Frontier Low volume, high stakes
Final review before anything ships Frontier Last line of defence

Newsletter · weekly

The Build Log

One system teardown a week. What I built, what it cost, what broke, and the exact prompts that did the heavy lifting. No tool listicles.

  • A full build teardown with architecture
  • The prompt or config that unlocked it
  • The failures, with root causes

Weekly. Unsubscribe in one click. Read past issues.