colocatedeventsna2025.sched.com/event/28D4h/...

Sure, if you are trying to one-shot a feature, overall intelligence is everything. But I think most developers working in larger codebases pair-program with their LLM, and iteration speed is the most important factor for productivity.

Also, I still need to experiment more with `grok-4-fast-reasoning` in Cursor, but it's so crazy fast. I'm coming to believe that very fast + medium intelligence is way more important than slow + smart intelligence for working with these models as a day-to-day pair programmer.

Full write-up is here → blog.devcycle.com/devcycle-mcp...

5/ The real magic of MCP is when it deeply integrates into your actual coding flow. You can now ask your AI something like ‘wrap this in a feature flag’, it writes the code, it auto-creates or fetches the flag, and self-targets you into the flag for testing.

4/ Cloudflare Workers AI + Durable Objects made auth easy and handled all of the OAuth state for us. Remote MCP servers seem like the much easier install path, getting everyone to "npx -y" install some random script with full computer access is a security nightmare in waiting.

3/ Giving the agent too many tools is a problem. Exposing every single API was easy, but all it did was overload the context. Merging related calls into fewer, more powerful tools gave the agent just enough without eating all the AI’s context window.

2/ Descriptive errors makes up for a lot of other issues. This made the MCP go from “meh, it works” to “oh wow, this matters.” At first, our errors were vague and unhelpful, which made the agent hallucinate. Once we made errors specific, the AI Agent + MCP could actually recover.

1/ Good input schemas are critical. The input schemas (and descriptions) are your AI agent's primary context when deciding which tool to call. In certain places, .describe() statements on your schema parameters will help push the AI agent in the right direction.

There is more hope that less resource-intensive models will soon match the performance of state-of-the-art models. But users expect that they can use the leading models all day for next to nothing, breaking that habit will be hard...

The signup flow needs some work, literally didn’t know there were paid plans that could be scrolled horizontally. This needs to be a vertical scroll, or something more compact that makes it obvious there are multiple plans.