Every post, in order
The full posts collection rendered as a timeline. Each entry carries its tag keys — follow one to jump into the inverse relation.
The archive
Designing with constraints, on purpose
Every strong interface we have shipped started with a constraint we refused to negotiate away. Here is how we pick them.
The boring stack is a feature
We rebuilt our pipeline on tools nobody tweets about. Deploys got faster and the on-call channel went quiet.
Write the README first
If you cannot explain the tool before building it, you are about to build the wrong tool. A practice we stole from technical writers.
Tokens, not pixels
The day we deleted every hardcoded hex value was the day dark mode became a data change instead of a rewrite.
Yes, we ship on Fridays
The no-Friday-deploy rule treats the symptom. We fixed the disease instead, and the weekend stayed quiet anyway.
Code review is a writing exercise
The best reviewers on our team are not the fastest readers of code. They are the most careful writers of comments.
The second draft is the real one
Everything on this journal is published twice: once to find out what we think, once to say it properly.
Good tools disappear
The highest compliment for a tool is that nobody remembers using it. On interfaces that get out of the way.
Say hello
Questions about the writing, or about how this demo wires its collections together? We read every message.