Code Review Is Hard. For People, and for AI Too
Code review is still hard
Code review is still hard
I compared number-flow as fixed by five coding agents against my fork v0.2.1 once more. Performance reports changed with the font, the code went through a review with the authors hidden, and a follow-up experiment ended with keeping the mask default.
Looking back on 1,164 runs and the process of building an internal benchmark. Cost per task, the Claude Code run environment, what I had hoped for from open-weight models, and the conditions I would change next time
I solved 36 internal tasks three times each with Claude Sonnet 5.5 and GLM 5.3. Comparing resolved rate, limit stops, cost, and patch defects across 216 runs, looking at how the conditions differ from public benchmarks, and deciding whether to swap the model
Turning merged PRs from an internal WebSocket package into coding-agent evaluation tasks, validating the grader, and isolating personal instructions from the Claude Code run environment
How do you measure the model performance of a coding agent?
Why did the frontend stack pile up in layers, and why did rendering move back to the server? This essay weighs whether the same stack survives once agents write the code, and asks whether, if it does, the value of the developers who know it survives too.
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.
I'm definitely coding faster, but why are my codebase and skills staying the same? Examining the gap between perceived and proven benefits.
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.
Complete overview of core coding agent concepts: Rules, Commands, MCP, Sub-agents, Hooks, Skills, and Plugins
In July 2025, the browser GPU API changed generations for the first time in 14 years
I don't know what the future holds, but shouldn't we just keep developing diligently?