Writing
Notes on building software.
Essays and field notes on software engineering, systems, and the making of this site.
- Prepare Pull Request 🪄Agent guardrails are safety that makes high velocity workable. I encode mine as a single Cursor command that runs reviews, tests, lint, CI, and the feedback loop before a human ever sees the PR.
- Search Params are StateComponent-level hooks vs router-level schemas for URL state: what each offers, what each trades, and how to test both.
- Everything is a BlobHow I think about blob storage: one immutable primitive, a registry table, presigned URLs, and foreign keys as the garbage collector.
- Building mysayo.comHow I built this site. A static Astro front-end, a React island, and a Cloudflare-only stack managed entirely in Terraform, with secrets that never touch the repo.
- On Compilers, Compression and LLMsIf prompts produced truly reliable outputs, we wouldn't be writing code at all. We would simply have Virtual Machines executing English instead of JavaScript or Bytecode.
- The Vibe Coding Delusion: Why OpenAI Still Pays for SlackIn the last 30 days, I've overseen over 105,928 lines of agent-edited code.
- You’re Not Meta: Build Fast Teams with Fast TestsA tale of two internet giants and what it teaches us about release confidence and velocity.
- Pull Requests: Where Engineering Culture LivesShow me your PR workflow, and I'll tell you how your team collaborates.
- Forget Complexity: The Simplest Metric for High-Velocity TeamsHigh velocity is a strategic imperative, and as counterintuitive as it may seem, simply counting the number of pull requests (PRs) shipped over time — throughput — gives an excellent indicator of velocity.