Notebook · Post-mortem

Lessons paid for twice

A post mortem from a product in the workshop, unnamed until it’s ready. Three lessons I learned the expensive way, twice.

· 1 min read · Izaias Cavalcanti

Draft for review

Before the current version of one product in my workshop, there were two earlier prototypes. Both taught me the same three things. I only listened the second time, so these are lessons paid for twice.

  1. Use real tool calls, not pattern matching. The first prototypes guessed intent from text with rules. They worked on the examples and broke on people. The current version lets the model call real, typed tools, and checks every call.
  2. Stubs must fail loudly. A placeholder that quietly returns success hides the gap until a person finds it. Every stub now throws, with a message that says what is missing.
  3. Never report a false success. If the system isn’t sure something happened, it says so. “Every claim here is one the product can keep today” became the copy rule for the whole product.

Keyboard shortcuts

Single keys never fire while you type in a field.

?
Open or close this sheet
W
Show the working on case files
R
Switch plain and institutional wording
N
Night edition on or off
0
Wire mode: zero all colour
[
Previous case file or entry
]
Next case file or entry
Esc
Close any sheet or popover
Motion