Building thoughtful software with AI.Notes from the systems behind the work.
Every endpoint in my ordering system wrote the order status its own way, and one would rewind a received order to draft. I put every legal move in one shared table, made every writer ask it, and added a history trail and a changed-only webhook for supplier writes. The race and the lost-message problems are still mine.
Read moreA new webhook receiver kept the exact bytes the sender signed and then checked the signature against re-encoded JSON instead. Review caught it and one line fixed it, but the branch that lets unsigned events through is still there.
New accounts could bounce between my home page and a session-refresh route while a webhook caught up. I gave the wait one owner, a half-minute budget and an error page with a reason, and the tests are thinner than I'd like.
The issue-tracker receiver verified a shared-secret body signature that an OAuth-connected sender could never produce. I switched it to the signed bearer token the tracker actually sends, then found the new error recording for failed registration misses the failures it was built to record.
Wiring two issue trackers into my dev-metrics app got the handshake signed and the tokens into a vault, but disconnect now has to delete webhooks before the token that removes them, and the inbound event handlers still trust whoever calls.
Three billing calls in my admin app built their duplicate-protection keys from the current time, so a retried request never matched the first try, and the one test that pinned an exact key had to freeze the clock to pass.
A signup webhook builds the workspace but can never reach the session cookie, so my home page now waits, asks the login provider, and refreshes the session itself, and I still have two doubts about whether that refresh works.
A sweep to keep email addresses out of my webhook logs also pulled the address out of an invitation insert a few lines below a log call. A one-line follow-up put it back, with no test, and I still can't tell whether any blank rows were stored.
The way my admin app links a code-host install to a tenant got a rewrite. It checks that an installation exists, not that it belongs to you, and when the webhook arrives first, nothing ever finishes the setup.
Workspace creation waited for a later webhook so invited people wouldn't get a spare one, and self-serve people could log in before it fired. Now the creation handler asks the identity provider for memberships on the spot, a later event repairs misses, and the session lookup retries, but the comment that justifies it contradicts the one it replaced and nothing tests which is right.