Essays, playbooks, and the occasional post-mortem. Engineering, design, SEO, and what it takes to ship real software in 2026 — written by the people doing the work.
A practical guide to migrating a live product from Bubble, Framer, or Webflow into a real codebase — without the big-bang rewrite that kills momentum. The playbook we use on every rebuild we take on.
[ FIG. 001 ] · Featured
01
EngineeringHow a single OpenZeppelin v5 _update override enforces "only verified addresses can ever hold this token" on an ERC-20 — the pattern, the mint/burn exemptions, and when to graduate to ERC-3643.
Read essay
EngineeringA goal-based raise only ends three ways. How deriving that state instead of storing it, splitting settlement into three narrow functions, and rounding whole-unit shares on purpose became the real engineering in a crowdfunding escrow.
Read essay
EngineeringHow we shipped a native-feeling Mac analytics app with no backend server: a universal Electron binary bundling a compiled native module, local SQLite in WAL mode as the entire data layer, defensive import of a user's own data export, and provider-agnostic LLM calls made straight from the desktop client.
Read essay
EngineeringInside an AEO monitor from a product we built: it asks ChatGPT, Claude, and Perplexity the questions your buyers actually type, logs whether they name you, and pairs that with Search Console rank deltas — plus the honest limits of a method with no official citation-rank API.
Read essay
EngineeringSix feeds had real APIs, two didn't, and none of the eight agreed on team IDs or match state. How a provider-adapter layer and a canonical identity table turned that into one clean table per match.
Read essay
EngineeringA rich push feed preferred when fresh, a fallback poller that never stops running, and the lease-based cleanup that stops a system from calling frozen matches "live."
Read essay
EngineeringHow to tell a client-rendered page from a server-rendered one in under a minute, and why routing each to the cheapest reliable extraction path — fetch-and-parse or headless browser — is the single biggest cost lever in a scraping pipeline.
Read essay
EngineeringA practical playbook for matching product records across catalogs: exact-key matching first, pg_trgm fuzzy similarity for the messy middle, a confidence-banded human review queue, and normalizing units and package sizes so comparisons are actually valid.
Read essay
EngineeringA technical walkthrough of matryoshka retrieval: how Matryoshka-trained embeddings let a single vector serve as both a cheap ANN prefix and an exact rerank target, why the full-dimension vector should live on disk with no HNSW graph, and how RRF layers a sparse signal on top without a second collection.
Read essay
EngineeringSparse retrieval computes term-frequency statistics across the whole corpus. Share one Qdrant collection between RAG tenants and their IDF weights silently blend — a retrieval-correctness leak with no stack trace. The trap, and the four-part isolation checklist that avoids it.
Read essay
EngineeringHow we normalized ingredients, mapped tags, and extracted structured data across 8,000 product records with a small vision+text model — total AI spend under $30, failure modes reported honestly.
Read essay
EngineeringA bulk dump-on-connect flooded a WebSocket relay with 436,000 messages, triggered a 1006 disconnect storm, and buried live data under a 3.4M-message backlog — here's the diff-based fix.
Read essay
EngineeringInside the provider-agnostic LLM layer from an applied-AI product we built: one interface, three adapters, two cost tiers, typed outputs — and the benchmark that showed a free model beating a frontier one on quality.
Read essay
ShopifyShipping UI onto a Shopify store you don't control means giving up nearly every assumption a normal frontend gets to make — one IIFE bundle, prefixed CSS, an app embed block, and the store's own cart API.
Read essay
ShopifyThe anatomy of a full Shopify app — a merchant-configurable theme extension, an embedded Polaris admin, an App Proxy backend, and the compliance webhooks reviewers actually check.
Read essay
SecurityEvery scanner finds a different class of flaw; none, on its own, tells you what to fix first. How the tools actually work in 2026 — and why buying more rarely makes an app more secure.
Read analysis
SecurityA fair comparison of managed ASPM and open-source vulnerability triage — native scanning, dedup, false positives, the real cost of "free", and who should pick which.
Read analysis
SecurityThe free SAST, DAST, SCA, secrets and IaC scanners worth running — and the honest point where a DIY open-source stack starts costing more than it saves.
Read analysis
MarketIn the Gulf, modernization is set by the regulator's calendar, not the CFO's budget. The 201–1,000 mid-market is legally in scope, and too lean to build in-house.
Read analysis
MarketInvestors killed growth-at-all-costs while DORA and PSD3 imposed bank-grade compliance regardless of size. The mid-band is caught in a buying window.
Read analysis
MarketNot the megabanks (they build in-house), not the seed neobanks (no budget). The 201–1,000-employee tier can't hire or fundraise its way to modernization — it has to buy.
Read analysis
MarketEveryone studies Nubank's 123M customers. If you sell into LatAm fintech, that's the wrong company to study. The reachable buyers are the 200–1,000-person tier below it.
Read analysis
EngineeringTypes aren't about purity — they're about shipping faster with fewer nights on call. What we use, what we skip, and the two rules we enforce on every project.
Read essay
ProcessFive days, four artefacts, one honest number. The shape of our discovery engagement and why we never send a multi-page proposal.
Read essay
SEOEngineering-grade SEO for 2026 — Core Web Vitals, structured data, content architecture. No content farming, no link swaps.
Read essay
ShopifyWhat the new extensibility surface gets right, what it still gets wrong, and the patterns we've arrived at after shipping twelve of them.
Read essay
DesignTokens, primitives, composition — how we structure design systems so they survive a handoff, a team change, and three years of product drift.
Read essay
EngineeringWe audited fourteen greenfield stacks we've shipped since 2023. In every one of them, Postgres plus a decent ORM was the right default. Here's why.
Read essay
ProcessNo hour-by-hour invoicing, no scope creep, no mystery. The cadence we've used on forty-plus engagements and why clients renew on it.
Read essay
DesignWhat magazines do better than product designers, and how to borrow from them without your dashboard turning into a zine.
Read essay
EngineeringYou don't need a platform team to know what your app is doing. A minimal observability stack that costs less than one senior engineer's monthly coffee.
Read essayOne essay every other Tuesday. Engineering, design, and the craft of shipping software. No tracking pixels, unsubscribe in one click.