The dashboard nobody looks at
Most dashboards are built during an incident and never opened again. A few are worth keeping, and they look different.
#craft
78 pieces tagged craft,
from March 7, 2025 to September 28, 2026.
Least privilege, actually applied
Everyone agrees with the principle. Almost nobody has checked what their service can actually reach.
Reading an RFC
Specifications look impenetrable and follow strict conventions. Knowing the conventions makes them the best documentation available.
The migration that never finished
Half-completed migrations are the most expensive state a system can be in, and the most common one.
Choosing an ID
Integers, UUIDs, ULIDs, or something with meaning. The decision is permanent and it leaks into everything.
Why your tests are slow
Six causes, ranked by how often they are the real problem, and the fix for each.
The graph nobody drew
Your service dependency graph exists whether or not anyone has written it down. Writing it down takes an afternoon.
Timeouts: every one of them
A request crosses a dozen components with a timeout each, and almost nobody has ever added them up.
The debugging notebook
Writing down what you tried is the cheapest debugging technique there is, and almost nobody does it.
The interface is the product
Users cannot see your architecture. They can see the six seconds it takes to do the thing they came for.
The API you ship to yourself
Internal interfaces get none of the care external ones do, and they are the ones you'll live with longest.
Shell scripts that outlive you
Six lines at the top of a bash script are the difference between a tool and a trap.
everything else tagged #craft 66
- The cost of a 500essay
- How to run a spikeessay
- Boring technology, revisitedessay
- The service you should not have writtenessay
- Reading a flame graphessay
- What "done" actually meansessay
- The load-bearing commentessay
- Two hundred pieces inessay
- Two years of agentic coding: what stuckessay
- Deleting code is the highest-value work nobody schedulesessay
- The performance budgetessay
- What I look for in a codebase in the first houressay
- The unreasonable effectiveness of a changelogessay
- Property-based testing deserves its momentessay
- The onboarding document that actually worksessay
- Secrets management, practicallyessay
- Code review comments that change thingsessay
- Configuration is the most under-designed part of your systemessay
- Randomness, and the bugs you cannot reproduceessay
- What a staff engineer does all dayessay
- Distributed tracing that people actually useessay
- Refactoring under an agentessay
- Static analysis is finally worth the false positivesessay
- Time zones, and why your calendar code is wrongessay
- Rewrites: when they actually workessay
- What a great bug report containsessay
- Model evaluation for people who shipessay
- Idempotency is the only distributed systems concept you needessay
- Compression is underratedessay
- Run the incident before the incidentessay
- Error messages are a user interfaceessay
- Naming things: the actual rulesessay
- Search is hard and you should probably not build itessay
- Migrations that don't wake anyone upessay
- The three kinds of technical debtessay
- Accessibility is a testing problemessay
- The API versioning decisionessay
- Observability costs more than the thing it observesessay
- The joke RFCs are the best documentationessay
- Why your build is slowessay
- Design docs people actually readessay
- The cost of a meeting, in engineering termsessay
- Schema design is the only design that lastsessay
- GDC and the engineering nobody outside games learns fromessay
- Feature flags and the state space nobody testsessay
- The engineer's guide to saying noessay
- On-call is a design problemessay
- Documentation is a product and you should staff it like oneessay
- Type systems and the cost of being rightessay
- The dependency budgetessay
- How to read a benchmarkessay
- Your monitoring is measuring the wrong ninesessay
- Reading code is a skill and nobody teaches itessay
- Verification is the whole job nowessay
- What I got wrong in 2025essay
- The postmortem that changes somethingessay
- Advent of Code and what a puzzle is foressay
- The technical interview is measuring the wrong thing, againessay
- Estimation is a communication problemessay
- The pull request is the wrong unit of reviewessay
- Caching is the only optimization that reliably worksessay
- Write the README firstessay
- Your logs are a product and you are shipping a bad oneessay
- The test suite is a design documentessay
- Vibe coding is real, and it is not what you thinkessay
- The eight git commands worth actually learningessay