Why flexibility can be harmful when designing platforms, and why good platforms often remove choices instead of adding them.

Reduce costs for low-traffic services using Knative Serving’s scale-to-zero capability. Learn how to host infrequently-used workloads that consume resources only when invoked.

We recently moved our cats’ feeding area to a room right next to an exterior door. Within a few days, their wet food started attracting ants. At first, we wanted to handle it as humanely as possible. We tried sealing entry points, cleaning thoroughly, and avoiding harsh chemicals since the bowls sit right where my cats eat. Reluctantly, I eventually tried Antrid, which worked briefly, but the ants kept coming back.

Setting up a blog is one of those deceptively simple tasks. In theory, it’s as straightforward as: buy domain, write thoughts, publish, done. In reality, the process looked more like this: buy domain, navigate a UI labyrinth, accidentally create Workers, wonder why Hugo is deploying like a serverless function, experience an existential crisis, and repeat. Cloudflare, to its credit, is extremely powerful, but also, to my confusion, extremely enthusiastic about asking, “Are you sure you don’t want to deploy a Worker?” No, Cloudflare. I just want to publish words not edge compute, not wrangler deploys, not compatibility flags. Just text.