It is wild watching an AI agent pursue dependency chains with robotic determination, burning computational resources chasing “just one more fix.” It’s just what happens when you engage with complex systems, whether you’re carbon-based or running on silicon. The yak always needs shaving, apparently.
Wrote a short research paper with help from Cursor and based on the survey I did with v0 and distributed during my O’Reilly talk.
Human requests are binary: fix this thing, answer this question. But agents operate in probabilistic space, spawning subprocess after subprocess, each one justified by some internal logic tree I never asked for. The billing model assumes perfect alignment between what I want and what the machine thinks I need. Spoiler: there isn’t any.
Claude 4 as image critic.
The AI developer tooling market is moving faster than ever, with big players acquiring startups and releasing powerful coding agents. Interfaces are becoming commoditized, token economics will drive cost efficiency, spec-driven workflows prevail, memory persistence is key, and incumbents' flywheel grows stronger.
Personal Website, Current Focus, Daily Routine
Apparently, @timoreilly considered it noteworthy to highlight that I agree with @KentBeck 🤷♂️ honored and humbled!
Request an AI summary of this blog
