There's something magical about encapsulating complex information and processes into a single interaction. That's what drew me to APIs — and now that AI agents are calling them too, the stakes are even higher.

I'm a Product Manager at Postman, where I work on the platform and MCP Server that developers and AI agents use to build with APIs. I also run the API Athens meetup. This is where I write about what I'm learning — APIs, agentic systems, design, and how they all connect.

Let's chat RSS feed

Recent

Agents Are the New Microservices

1. Single responsibility works best People tend to model agents on people: a product owner agent, an engineer agent, a QA agent. That fails for the same reason UserService failed. A role is not a scope. It is a bundle of unrelated jobs that share a title. Single-task agents hold up better. A backlog grooming agent. A release notes agent. A migration risk review agent. One job you can describe in a sentence, with a small tool surface and a clear output.
read more

Productivity with AI Assistants

As a product manager, I have created several agents to delegate areas of my work. I have one for backlog grooming, one responsible for maintaining metrics and analytics and one for design reviews. The recent Claude Code upgrades have made this possible.
read more

More

Agent and Software Boundaries

Backlog Grooming Agent Insights

Agent inception

Thoughts on MCP Code Mode

All posts All notes