I audited 14 Shopify themes last quarter for speed. 11 of them blamed apps. None had touched Liquid loop count, capture-in-loop allocations, or image output. After optimizing 100+ Shopify stores over 12 years: the code-level patterns in your theme files account for 40-60% of total render time. Apps matter. Images matter. The template layer is where the compounding problems live. Here are the 5 Liq
This technical post walks through the design and implementation of Secure Playground: a local web app that simulates prompt-injection attacks against large language models and demonstrates simple defenses. Provide a minimal, reproducible environment to test payloads and defensive strategies. Make it easy to add new providers and run mutation-based red-team experiments. Offer a leaderboard and scor
So I made a bad trade in my fantasy baseball league. Dropped Kaz Okamoto because — according to my data — he’d been cold for two weeks. In reality, he’s been on a tear for the last 9 days. 😅 This was a bad decision made because of bad data — my stats cron job had hit a rate limit, exited with no errors, and my FastAPI backend kept serving a stale JSON snapshot. Well, I’d been meaning to fix that
Japanese subscription services have a problem with terms and conditions. Not the length — that's universal. The specific issue is that Japanese cancellation terms, automatic renewal clauses, and price change notifications are buried in dense legal Japanese that's difficult to parse even for native speakers. The phrasing is designed to be compliant, not readable. I've been surprised by charges I di
If you want the failure-mode and testing path through the catalog, start here. Recommended route: Service Worker Failure Modes in Offline-First PWAs Rollback Patterns in Offline-First PWAs Testing IndexedDB Schema Migrations in Offline-First PWAs Offline Queue Replay and Idempotency in Offline-First PWAs If you want privacy-first, offline health tech to exist without surveillance funding it: spons
I run a few side projects. The paperwork reality of running side projects is filling in the same company name, address, phone number, and tax ID into web forms, over and over, on vendor portals, invoice tools, e-commerce seller dashboards, and government registration pages. My password manager handles login credentials. It doesn't handle business info particularly well. So I built FormFill Vault.
I built a React form library 2 years ago. It got almost zero usage. Recently, I revisited the idea and realized the problem wasn’t the code — it was the approach. Most form libraries are powerful, but they come with complexity: too much setup too much wiring too much abstraction So I rebuilt it from scratch with one goal: Make forms stupidly simple. Every time I build a form in React, I repeat the
Say you built an AI agent and customers are starting to pay for it. Sooner or later you'll want to charge them by what they actually use, because some customers hammer the agent all day while others send a handful of messages a week. A single flat fee loses money on the heavy users and overcharges the light ones. The billing problem is the same whether your agent runs on your own model (self-hoste