Building in Public, Honestly
Building in public is not posting wins. It is showing the work (the false starts, the trade-offs, and the small decisions), and letting the process be the content.
Writing
Long-form engineering writing on maintainable systems, developer tools, open source, and the practice of building software that lasts.
Building in public is not posting wins. It is showing the work (the false starts, the trade-offs, and the small decisions), and letting the process be the content.
We are taught to write code, rarely to read it. But reading is most of the job, and it is a skill that improves like any other.
Every auth mistake is invisible at the moment it's made and expensive the moment it's found. That's why it has to be done right the first time.
Developers do not adopt tools because they are powerful. They adopt tools that let them stay in flow. Everything else is a tax.
Big changes are hard to review, hard to roll back, and hard to reason about. The small change is the unit of safe engineering.
A refactor is a letter to the next engineer. Every rename, every extracted function, every deleted comment is a sentence in it.
The architecture that survives is the one that anticipates change, not by predicting the future, but by making change cheap.
Open source taught me more about engineering than any course did, not because the code is better, but because the process is real.
Documentation is not a chore that follows the real work. It is the real work, done in a form that other people can use.
The longer I build software, the less I believe writing code is the difficult part. Keeping software understandable, maintainable, and adaptable is.