The quiet case for a boring stack
A small app doesn’t need a small version of a big company’s infrastructure. Notes on choosing tools you can live with.
Notes on building software, learning by doing, and thinking beyond the code.
A small app doesn’t need a small version of a big company’s infrastructure. Notes on choosing tools you can live with.
An experiment in doing less: a local database, a little contention, and a much better question.
A small argument for publishing the useful middle — before every thought turns into a definitive guide.
The most useful comment I wrote today wasn’t about what the code does. It was about the alternative I tried, and why I walked away from it.
Before adding a background worker, I asked: does this actually need to happen in the background? Turns out, not yet.
Twenty minutes, one unfamiliar language, one tiny script. No course, no roadmap. Just enough friction to notice what I take for granted.