I think order matters more than technique in performance work. This post lays out the practical flow: settle the support range and dependencies first, measure before picking a technique, decide what to fix first, choose a response when the cause lives in someone else's code or infrastructure, prove nothing broke and keep it guarded, and report numbers by grade.
The friction that made judgment expensive is the same friction that taught it. Why the skill growing most valuable in the AI era is the one being cultivated least
If the spec is satisfied and the bugs get fixed, do you still need to be able to read the code? Understanding doesn't disappear: this essay traces where it moves.
The claim that job boundaries are collapsing is only half true. What collapses is production; judgment and responsibility remain.
Bun moved roughly 960,000 lines from Zig to Rust in six days using Claude Code. The meaning here is not code quality but OSS governance and resource asymmetry.
A good package has to be user-friendly not just in features, but in dependencies, version bumps, compatibility, and release policy.
The bundle costs that code review misses, and how to surface them in the PR.
The questions React Foundation must answer
AI coding tools aren't changing developers—they're changing the nature of what developers do.
