Two platforms went live this release, and they have nothing in common except everything that matters. One is a flight-planning desk for a Piper PA-46 turboprop that has to keep working at 26,000 feet with no signal. The other sells my mother's handmade letter-bead bracelets. The fleet my résumé keeps bragging about is twelve now.
JetDesk.AI: offline isn't a feature, it's the spec
The design constraint that shaped everything: at altitude there is no network, and a planning tool that dies without one is a paperweight with a loading spinner. So the entire FAA airport and runway database — every field, every runway, via NASR and OurAirports — ships inside the app. One file. Install it as a PWA, lose the signal, keep planning.
The live layer earns its keep when you have bars: METAR/TAF with flight-category badges, forecast winds aloft at cruise altitude correcting every leg's groundspeed, and a per-runway verdict that does the crosswind math so you don't do it in your head at the hold-short line. The fuel-stop optimizer weighs a detour's extra miles and burn against the cheaper gas — and the fuel prices themselves are crowd-shared, synced across every phone running the app behind a PIN, through three Cloudflare Pages Functions. When it's time to actually file, one tap hands the route to ForeFlight. I'm not rebuilding ForeFlight; I'm building the desk you sit at before it.
It is a planning aid, not an instrument, and it says so — loudly. Same philosophy as every review gate I've ever shipped: the tool drafts, the pilot verifies against official sources. Some interfaces should refuse to be trusted.
Show It With Words: inventory as code
My mother Audrey has been stringing letter-bead bracelets in Amesbury for eleven years — 4.9 stars on Etsy, ninety-one orders, and a product line that by definition cannot be photographed in advance, because the product is whatever word you need on your wrist.
So the storefront doesn't use photos where it matters. Every bracelet, tote and keyring is drawn live as procedural SVG — bead rings with the letters set along the bottom arc, stitched canvas totes, keyrings on split rings. The build-your-own wizard renders your exact word on the product as you type it: six steps, six colourways, three letter styles, per-letter pricing, flat lay or on the wrist. What you see is literally what gets strung, because the preview and the order are the same data.
Cart, bundle pricing (third bracelet half price — her rule, good rule), and a checkout that demonstrates the whole flow but hands off to a payment provider the day she flips the switch. Real Etsy reviews ride along in Store JSON-LD on a pre-rendered landing page, so the SEO works even though the app is a hand-rolled SPA in one file. No framework. Her bead tray doesn't have a build step; her website doesn't either.
The thread
A turboprop desk and a bracelet shop, and the discipline is identical: figure out the real constraint (no signal; no fixed inventory), put the data model first, draw the interface from the data, gate the risky step (official briefing sources; a payment provider), then put it on the status page with everything else and let the uptime checks keep me honest. Both are being monitored right now, next to the ERP and the SaaS suite, because a platform I won't monitor is a platform I don't ship.
Twelve platforms. One of them helps me land. One of them helps my mother sell. The résumé updates itself; the pride part doesn't need a deploy.