Learning on Web Dev Open is free for all.

AI-Native Products > Checkpoint: AI-Native, and the end of the courseWriting up something non-deterministic
Phase 08Checkpoint: AI-Native, and the end of the course432 of 434

Writing up something non-deterministic

The eval case that failed, the cost number that surprised you, the thing you decided not to automate. Not a tour of the API.

Concept14 minAI implements

The interesting content is the judgement. Which eval case your first version failed and what that revealed. What the cost model said at ten times the users. Which capability you deliberately did not expose, and what you gave up by not exposing it. Anyone can write about how streaming works; very few write about the decision they made against their own convenience.

Include the numbers, because they are what make it verifiable: cases in the suite, pass rate before and after, cost per action, p95 latency, what the kill criterion was. A write-up with numbers in it reads as someone who ran the thing; a write-up without them reads as someone who read about it.

You should now be able to

  • Write a build log that shows judgement rather than usage
  • Present numbers that make the work verifiable
Ask the community

Loading…