Practical writing on shipping software that lasts — infrastructure, backends, interfaces, and the unglamorous work between a prototype and a product people actually run.
A vibe-coded prototype gets you to “it works on my machine.” The last stretch — auth, observability, deploys, the failure modes nobody demos — is where real products are won. Here is the checklist I run every time.
You do not need a Vault cluster to stop leaking credentials. A pragmatic setup for solo builders and small teams that scales when you do.
Naming, versioning, and error shapes are cheap to get right on day one and brutally expensive to fix later. A field guide.
How a 1.2 MB ONNX model and a few hundred lines of glue replaced a recurring cloud cost — and made the product faster and more private.
Less hype, more discipline: how I keep a codebase clean, tested, and fast to extend when an agent is writing half the diffs.
Skip the dashboard sprawl. Track latency, error rate, and saturation well and you will catch almost everything before your users do.
One schema, validated at every boundary. How end-to-end types turn a class of runtime bugs into compile-time errors.