Practical, no-fluff writing on IT leadership, CRM & revenue plumbing, attribution, and AI automation — from someone who still ships the code.
30 posts · 4 categories · 23 tags
A mail guard that throws an exception when it blocks a message teaches the retry queue to keep attempting a send that will never be allowed to leave the process — the harder design keeps a policy block and a transport failure looking nothing alike, then proves a worker killed after the send is recorded but before acknowledgment leaves one copy, not two.
A factory-telemetry simulator that replays four hours in 15,000-millisecond steps and again in 150,000-millisecond steps must produce a byte-identical event list, or every calibrated OEE band is only true at the speed you happened to demo it — a discrete-event scheduler makes the tick size irrelevant by design, and a test proves it rather than assuming it.
A duplicate-customer scan ran right after its own transaction returned, but on the website path that transaction was only a savepoint inside the caller's. A read-only audit, not the 1,319 tests already passing, found that bug and three more like it.
PostgreSQL stores every timestamp with a time zone as UTC internally, but reads and writes naive timestamp text through the session's timezone setting, and Laravel sends naive text by default. In a non-UTC session, a training-academy system read instants back seven hours early with zero errors, invisible only because dev and CI containers already ran UTC.
Next.js 16 removed the 'eslint' key from its config type, and a key written into next.config.ts anyway didn't fail at runtime — it failed the type checker. The CI gate sat red for about a week before anyone acted on it, and the first to act was a baseline audit, not anyone watching the build.