Question
You used an AI to draft a design doc for a new event-driven order-processing pipeline based on your bullet points and a few code sketches. The draft reads beautifully and confidently asserts the design 'guarantees exactly-once processing,' 'scales linearly to millions of events,' and 'has no single point of failure.' How do you review an AI-written design doc for overstatement before it goes to a design review, and what's the cost of letting these claims through?
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it — tests, edge cases, reading critically — and how you’d re-prompt or decompose to get it right.
Vibe coding: describe the solution in plain language (or narrate it) and the coach grades your approach. Generating runnable code from your description is coming next.