Public APIs are infrastructure, not art projects. The best APIs are predictably boring: they use standard REST conventions, maintain consistency across all endpoints, and let developers build a mental model after using just one endpoint. When your API tries to be clever with novel patterns or inconsistent structures, integration goes from hours to days. Save your innovation for your product and let your API fade into the background where it belongs.

We’re in the jQuery age of AI agents, where every integration feels like duct tape, and standards are still a dream. Just like jQuery once smoothed over the chaos of incompatible browsers, MCP is doing the same for fragmented AI tools, making it finally possible to ship agents that actually work. It’s not perfect, but it’s the layer we need right now.

It’s October 2025 and it’s my first time vibe coding. I have mixed feelings.

Your agent can't check Slack, pull data from your Postgres database, read files from Google Drive, or update tickets in Linear. Every time you want to add a new integration, you're staring down weeks of custom API work, authentication headaches, and the inevitable "wait, their API changed again?" moments.