Thirty Days of Working by Prompt: How Attention Disappears
I counted 30 days of my own records, and there was no day when I stayed on one thing for 60 minutes
I counted 30 days of my own records, and there was no day when I stayed on one thing for 60 minutes
Code review is still hard
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?
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.
I don't know what the future holds, but shouldn't we just keep developing diligently?