Reframing rounding as remainder allocation
You ask an AI to write a JS function that splits a restaurant bill three ways and rounds to cents. It returns `total / 3` rounded with `.toFixed(2)` per person. You notice $100.00 / 3 gives three people paying $33.33 = $99.99, a penny short. You say 'the totals don't add up' and it switches to `Math.round`, same penny gap. The model treats this as a rounding-style problem, not a remainder-allocation problem. How do you re-steer?
split_bill_cents(total_cents: int, people: int) → list[int][10000,3]out[3334,3333,3333][10000,4]out[2500,2500,2500,2500][5,3]out[2,2,1]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 & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.