Code review comments that change things
Most review comments are noise or nitpicks. A small taxonomy of the ones that are worth writing.
tech, developers, and the code underneath
older dispatches from the README archive.
Most review comments are noise or nitpicks. A small taxonomy of the ones that are worth writing.
When a fast producer meets a slow consumer, something has to give. Deciding what, in advance, is the whole discipline.
Default blocking and pay-per-crawl changed who can read the web. An assessment of what actually happened.
Write once, run anywhere, debug everywhere. The honest accounting of what each approach actually costs.
The most common way a small incident becomes a large one is a retry policy written without thinking about aggregate behavior.
Six months of regulation, agent tooling that mostly did not fix the bottleneck, and a web platform that quietly finished.
It has no type system, no tests, no review, and it causes a disproportionate share of outages.
The bug that happens once a week and never in staging. A systematic approach to the class of problem everyone handles badly.
The role is genuinely ambiguous and that ambiguity is load-bearing. An attempt at a concrete description.
Not legal advice. A working engineer's map of what the common licenses actually require you to do.
Most tracing deployments produce beautiful waterfalls nobody opens. The difference is three implementation details.
Large mechanical refactors are the clearest win available from coding agents. Here is the process that keeps them safe.
A month of synchronized global demand across three countries, sixteen cities, and every streaming platform at once.
New OS versions, more on-device model surface, and a developer relationship that remains complicated.
The tools got dramatically better while everyone was ignoring them because of a bad experience in 2015.
An instant is not a time. A time is not a date. The rules change by government decree with a few weeks' notice.
The received wisdom is never rewrite. The received wisdom is mostly right and has three real exceptions.
Six fields. Most reports have two. The difference is measured in days of engineering time.
Running code close to users is a real win for a narrow set of workloads and a complication for everything else.
Not research benchmarks. A practical harness you can build in a day that makes every future model decision an hour instead of a week.