The Small Model That Knows One Job
Tobi Lutke shared a tiny Shopify model beating a frontier model at one internal job. I wanted to know what that result really says, and whether the same idea is useful for PLAYGRND.
Practical notes from backend engineering and building products, plus occasional writing about business, family, and ambition.
6 notes for “PLAYGRND”
Tobi Lutke shared a tiny Shopify model beating a frontier model at one internal job. I wanted to know what that result really says, and whether the same idea is useful for PLAYGRND.
How I organized Codex into twelve bounded product workstreams without turning one shared repository into chaos.
A practical follow-up to the one-server setup: what I would do when a small app turns into a real business and the server starts running out of room.
How I moved stable PLAYGRND season aggregates from raw query paths into persisted derived tables and Redis snapshots, while keeping raw fallback intact.
For PLAYGRND, WhatsApp is not a gimmick. It is the channel users already trust, so login and profile claims should meet them there.
PLAYGRND is my practical example of how a small team can move faster with AI without letting AI replace product and engineering judgment.