Long-form pieces on the things I learn while building. No quick tips, no listicles - actual engineering writing.
I copy the same engineering principles document into every repo I start, then layer framework-specific rules on top. Here is why the boring duplicated file outperforms clever tooling.
The best design rule I use is brutally simple: if removing an element does not hurt the page, it should not be there. Notes from the design system I apply to client work.
A client handed me a generic security checklist. Instead of nodding and filing it away, I mapped every item to actual code in the project, and learned that the mapping is where all the value lives.
AI agents now write a lot of my infrastructure code, so I gave them a binding rulebook with hard reject gates. Then I turned it on my own project, and it failed.
I wrote an infrastructure rulebook for my own projects, and the most useful rule is the one that keeps telling me no. Here is the decision framework that stops me from over-engineering.