Every pillar, one tag. The range, not a skills list.
A fleet of thirteen small servers that give agents real hands. What they wrap, the two house styles I build them in, and why they all start read-only.
In NutriM8 you can mumble your whole day into your phone once. A background worker untangles it into sleep, weight, exercise, hydration and food, and resolves "a snack after lunch" to a real timestamp.
A marketing API exposes 115 operations; my server hands the agent six tools. The boundary is set by token budget and model focus, not REST purity.
A catalogue of the guards I actually ship: typed confirmations, blast-radius escalation, pay-to-play gating, ordered workflows, and read-only by default.
The backend everyone wrote off years ago is the one I keep reaching for, because boring infrastructure is the kind that ships products.
Diarization is three questions wearing one coat. Split them into specialists, never merge across a turn, and the failures stop hiding inside each other.
Lumen8 scores a student's mastery from 0 to 400 and then lets it decay every night. Here is why decaying toward a floor beats resetting to zero.
Why I run everything as Dockerized TypeScript in one repo, and how that lets a single person ship more surface area than a small team.
Stumble is a real two-sided marketplace for court coverage: ten packages, five services, Stripe payouts, offline mobile sync. Here is what one developer building all of that actually looks like.
Most software fails politely. Some of it does not, and that changes how you build.
A recording goes in, a speaker-labelled transcript comes out.
Search food by meaning, not by exact product name.
A model drafts maths questions against the component library, a verifier throws out the junk, and a clean one renders. Forever.
Drag two points and watch the distance formula build itself out of a right triangle.
whisper_schedule