You're reviewing the wrong file
When an AI agent gets a requirement wrong, the mistake lives in the test assertions, not the implementation. Domain knowledge catches it, not coding skill.
36 posts
Stop calling it vibe coding
"Vibe coding" has become shorthand for bad engineering to some people, but does the label hold up? This post unpacks how a playful term coined by Andrej Karpathy became a verdict, and why that's costing teams more than they realise.
Beyond prompting: read, verify, implement, learn
LLMs generate code fast, but knowledge debt accumulates quickly. The fix is living documentation, and this post shows how to turn your LLM into the partner that maintains it automatically.
Bots and Boundaries: Two problems, one policy (Part 3)
In part three, we look at both sides of the AI contribution debate. A working patch, real demand, never submitted, rejected because AI was involved. But maintainers are unpaid volunteers, and AI halved the cost of contributing without touching the cost of review. Both sides have a point.
From opt in to default
Developers don't skip standards because they're careless, they skip them because there are fifteen things to remember and the code was the hard part. The real question isn't which tasks your LLM handles well. It's what's still slipping through ungated.
Onboard the AI like you'd onboard a developer
Legacy codebases are messy, undocumented, and full of decisions nobody remembers making. But if you can explain it to a new developer, you can onboard an AI and that changes everything.
Bots and Boundaries: Who do you blame when the bot defames? (Part 2)
This is Part 2 of Bots and Boundaries, a three-part series on AI agents in open source.
Bots and Boundaries: The bot apologised, and that's the problem (Part 1)
An AI agent recently submitted a pull request to the matplotlib Python library, and when the maintainer closed it, the agent autonomously published blog posts attacking them by name, then published an unsolicited apology. No human directed either action.
A letter to my son: Growing up in the AI world
Reflecting on whether teaching traditional coding skills still makes sense in 2026. Geoffrey wants to focus on teaching programming concepts rather than syntax, because AI has fundamentally changed how software is built.