46 Seconds Inside a 30-Second Webhook
A render call could take 46 seconds inside a webhook with a 30 second budget. The second finding turned out to be worse than the first one.
9 posts on this topic.
A render call could take 46 seconds inside a webhook with a 30 second budget. The second finding turned out to be worse than the first one.
One week after HACK_002: a real bug in the court deadline is fixed. New are a deadline calculator without AI, advice centres with contacts, and Turkish.
A script found the same work under eleven job titles. It turned into BewerbungsGenie, open as a public beta for Austria since 1 October 2026.
A family photo album made with coding agents: from a dictated prompt on Thursday evening to the first production deploy on Friday, and what is still missing.
HACK_002 recap from Vienna: the Pflegegeld-Prüfer, a care allowance checker, wins Track A1 but misses my advance target of 12 of 14 court cases. It gets 10.
Kleinunternehmer spans three laws in Austria. Why V2 kept exactly one column and reads the threshold from a date-gated value table.
A bakeoff across 16 real receipts exposed a systematic factor-1000 error. Why a deterministic guard sits above the model, not inside it.
About 20 people paid for my product, not one of them twice. What the numbers actually say and why the gap sits in activation, not in acquisition.
What sits between an AI prototype and daily use: data, failure handling, ownership, and deciding when an experiment has answered its question.