Practical, no-fluff writing on IT leadership, CRM & revenue plumbing, attribution, and AI automation — from someone who still ships the code.
15 posts · 4 categories · 23 tags
AIDA's outbound email job derives References and In-Reply-To by querying every prior email-bearing message on the ticket. On a retry, the message being sent already has its own Message-ID persisted from the failed first attempt — without an explicit exclusion, it would show up in its own References chain.
Every webhook integration works in the demo. Production loses events in the silence after you reply 200 — so I built OmniSync around one guarantee: once an event is acknowledged, it is never silently lost. At-least-once delivery, idempotent everything.
AIDA's public intake route checks content length, per-file size, a running total, and byte-sniffed MIME type before saving an attachment. None of that mattered once Next.js's own proxy layer silently truncated the request body first, with no error back to the client.
An AI agent blamed a failing Playwright test on Next.js response caching. I traced the code and blamed middleware. We were both wrong about the observation: the test's "anonymous" context was quietly authenticated. Two stacked bugs, two confident stories, and the re-run as the only reviewer that counted.
Why I started this blog, what I plan to write about, and a quick tour of the formatting it supports.