Written from builds, not from a content calendar.
Every piece here comes from something we own or ran, which means we can publish the architecture, the numbers and the parts that went wrong. That is the difference between a technical breakdown and a blog post.
Migrating 13,000 customers off Wix without locking anyone out
What actually has to move when a digital-product store changes platform — accounts, order history and the entitlements linking a customer to files they already paid for — and why passwords are the constraint that shapes the whole plan.
Driving a 45-second cinematic from scroll position
Why we rendered the Spoormaker hero to video rather than building it in WebGL, and the three traps in scrubbing a clip from scroll — each of which fails silently, and only on hardware you do not have on your desk.
Where the manual work actually hides
A method for finding the joins where a person is acting as glue between two systems — the four shapes those joins take, how to spot them by observation rather than workshop, and which ones you should refuse to automate.
Anatomy of a WordPress compromise
How these infections actually get in, what they change, how they persist through a cleanup — and why the honest recovery is a rebuild rather than a disinfection, because you can prove what you found but never what you missed.
Putting approval gates around an agent
The architecture behind our own sales runtime — narrow named agents, autonomy declared per action rather than per agent, a compliance pass that cannot edit what it reviews, and a kill switch held by one person. Publishable in full because we own it.
Shipping a two-sided marketplace on Supabase
Row-level security when there is no service layer to hide behind, why credits must be a ledger rather than a balance, and the testing mistake that let three defects reach QA — from a marine crew platform we own.
Roughly six in ten searches now end without a click. Being found increasingly means being quoted — and answer engines quote first-hand material with real numbers, not restated best practice. Nobody else can publish what happened inside our builds.