Notes on owning the product.
Working through Rails, AI, and what changes when the code writes itself. The full archive and a weekly newsletter live at rubyonai.
What a product engineer actually owns
If the agent writes the code, the title stops meaning implementation. It starts meaning judgment. Here is the line I draw between the two.
The harness is the hard part, not the model
Teams keep waiting for a better model. The leverage was never there. It sits in the context, the tools, and the review gates you build around the agent.
Why your AI rollout stalls after the demo
The demo always works. Then nothing ships. The gap is a workflow problem, and it is fixable once you stop treating the tool as the whole answer.
Reviewing code you didn't write, at ten times the volume
Agentic coding turns every developer into a reviewer. That is a skill, and most teams have not trained for it. A few habits that make the load survivable.
Rails conventions are a feature for coding agents
The opinions that make Rails fast for people make it fast for agents too. Convention is shared context, and shared context is what an agent runs on.
Specs over tickets: telling an agent what "done" means
A ticket describes a task. A spec describes the result. Agents do their best work when you write the second one, so the effort moves to intent.
More writing, every week, at rubyonai ↗