GoKawiilAn essay on the delectable pleasure of trusting your tools to help you do the work at hand.
Listen
Your browser does not support the audio element. Space play · ← → seek · ↑ ↓ volume · M mute
Essay
On my phone, I tap a button and a car arrives. I tap another and I have an apartment for the night. We've turned buttons on our screens into levers that move the real world. These buttons are as intuitive and easy to use as turning on a faucet in your home. Just like the faucet, there's a lot of plumbing behind the scenes to make them work.
But what if, every time you turned on your faucet, you had to crawl under the sink, stare at a mess of pipes, and reconnect things until the water came back?
Falling Into Trap Doors
That's what it feels like to build software on the web in the year 2026. Web development is riddled with trap doors between the act of creating and sharing a functional application. Here's what those trap doors tend to look like in practice:
State sync: the UI works locally, but the moment you add a server, you're managing two sources of truth that can drift apart, conflict, or silently overwrite each other. Even on the front end alone, the moment you introduce a separate state object, you have two representations of the same data — the DOM and the model — that can fall out of sync in subtle, hard-to-debug ways.
the UI works locally, but the moment you add a server, you're managing two sources of truth that can drift apart, conflict, or silently overwrite each other. Even on the front end alone, the moment you introduce a separate state object, you have two representations of the same data — the DOM and the model — that can fall out of sync in subtle, hard-to-debug ways. Schema lock-in: you're forced to commit to a data model while the interface is still evolving.
... continue reading