“Most people are using MCP wrong,” said MCP’s co-creator, David Soria Parra. I agree. Because I made the same mistake. Engineers would do the obvious thing: wrap each REST endpoint as an MCP tool and shove them into a custom registry. The result? Zero value over just calling the APIs directly. Worse than zero, honestly. […]

Read More →

Claude Code can show a status line at the bottom of the terminal: a thin bar that updates as you work. It is easy to ignore until you start hitting context limits or wondering what a session actually cost. The bar keeps that kind of signal in peripheral vision so the main transcript stays focused on the […]

Read More →

If you’ve used Claude Code for more than five minutes, you’ve seen it. That single word that cycles above the blinking cursor while Claude is off doing its thing. Pondering… then Orchestrating… then, if you’re lucky, Flibbertigibbeting… Those are spinner verbs. Table of contents What even is a spinner verb? A spinner verb is the gerund (the -ing word) that […]

Read More →

If you’ve ever typed npm run dev, refreshed a browser tab, and found yourself staring at the wrong project — you already know why Portless exists. Table of Contents Local development has a dirty little secret: port numbers are terrible identifiers. They collide, they’re impossible to memorize across a microservices stack, and they silently break things […]

Read More →

I’ve spent the last few months living in Claude Code. If you’re wondering if it’s worth the hype, the answer is yes—but probably not for the reasons you think. It isn’t just a better autocomplete. It’s more like a competent pair programmer that actually reads your whole codebase, runs your terminal commands, and never needs […]

Read More →