Code Review Is Hard. For People, and for AI Too
Code review is still hard
Code review is still hard
What should come before choosing a performance technique? This post follows the order used in practice: settling the support range and dependencies, measuring, deciding priorities, responding when the cause lives in someone else's code or infrastructure, guarding against regressions, and reporting results.
As code review and interviews stop reading code closely, there are fewer chances to build the judgment that matters more in the AI era. This essay checks the evidence from studies such as METR and GitClear, and considers why the need to learn judgment went away.
If the spec is satisfied and the bugs get fixed, do you still need to be able to read the code? This essay weighs the argument that you do not and the weak points in its premises, then lays out what you need to understand when you stop reading code directly and what juniors should aim for.
With AI tools, people can now produce the deliverables of other roles, and so we hear that the boundaries between job titles are collapsing. Separate the ability to make something from the ability to know whether it is right, and where do the boundaries get redrawn?
Bun moved roughly 960,000 lines from Zig to Rust in six days using Claude Code. This post works through what that means for 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
How does the work of a frontend developer change once AI coding tools arrive? Thoughts centered on writing specs, code review, cognitive debt, decision speed, and the role of senior engineers.