Journal
What we learned rewriting log retention
What changed when we stopped guessing and started measuring every step. Why the boring fix beat the clever one, and how we proved it.
Our approach to sandbox isolation
Our defaults, our reasoning, and what you can check yourself. Practical steps, not promises. How we make the safe path the easy path.
How we design our type scale
How we chose, tested and shipped the details. Good defaults, explained. What we kept, what we cut, and why. The small decisions that make the product feel quieter.
What a two-person agency taught us about speed
How one team went from a ticket queue to publishing in minutes. What changed for the people doing the work every day.
The details behind density settings
The small decisions that make the product feel quieter. What we kept, what we cut, and why. Good defaults, explained.
How a public radio newsroom ships every day
Lessons from a team that ships calmly. How one team went from a ticket queue to publishing in minutes. What changed for the people doing the work every day.
In praise of our type scale
How we chose, tested and shipped the details. The small decisions that make the product feel quieter. Good defaults, explained.
Our approach to credential handling
Our defaults, our reasoning, and what you can check yourself. How we make the safe path the easy path. Practical steps, not promises.
Now available: usage dashboards
Less waiting between done and live, for every team. Built for the person with five minutes between meetings. The thinking behind the release and what comes next.
Defaults matter: secrets rotation
Our defaults, our reasoning, and what you can check yourself. Practical steps, not promises. How we make the safe path the easy path.
A field guide to our build pipeline
The constraint, the fix, and the numbers before and after. What changed when we stopped guessing and started measuring every step.
A field guide to request tracing
Why the boring fix beat the clever one, and how we proved it. The constraint, the fix, and the numbers before and after.
How we rebuilt cold starts
A short tour of the decisions behind a faster, calmer system. What changed when we stopped guessing and started measuring every step.
Introducing the command bar
The thinking behind the release and what comes next. What it does, who it is for, and how to try it today. Less waiting between done and live, for every team.
Rethinking empty states
The small decisions that make the product feel quieter. Good defaults, explained. What we kept, what we cut, and why.
Hardening audit logs
Our defaults, our reasoning, and what you can check yourself. How we make the safe path the easy path. Practical steps, not promises.
Inside a 12-person studio
Lessons from a team that ships calmly. What changed for the people doing the work every day. How one team went from a ticket queue to publishing in minutes.
Notes on cold starts
What changed when we stopped guessing and started measuring every step. A short tour of the decisions behind a faster, calmer system.
Introducing role-based access
Less waiting between done and live, for every team. Built for the person with five minutes between meetings. The thinking behind the release and what comes next.
How we rebuilt edge caching
A short tour of the decisions behind a faster, calmer system. The constraint, the fix, and the numbers before and after.
Rethinking dark mode
What we kept, what we cut, and why. The small decisions that make the product feel quieter. Good defaults, explained.
The details behind color tokens
What we kept, what we cut, and why. Good defaults, explained. How we chose, tested and shipped the details. The small decisions that make the product feel quieter.
Notes on search indexing
What changed when we stopped guessing and started measuring every step. A short tour of the decisions behind a faster, calmer system.
Now available: version history
Built for the person with five minutes between meetings. What it does, who it is for, and how to try it today.