> If it stays at arm's length, and if it can "read only", then I am OK with it and actually somewhat pleased with it.
This isn't actually about AI. it's just classic human psychology.
You’ve had a rock-solid workflow for 25 years, so it makes total sense to be cautious and reject features you don't need.
Right now, keeping it at "arm's length" and "read-only" feels safe. But that's usually just phase one. Once that initial trust is established, those boundaries naturally start to melt away. Give it a couple of tax seasons, and you’ll probably find yourself wanting it to take on more of the heavy lifting.
What a time. I am back here genuinely wishing for OpenAI to release a great model, because without stiff competition, it feels like Anthropic has completely lost its mind.
I've used Kimi K2.5 when I run out of Codex quota. It does small and medium things OK. But if I work on complex things, I'll later have to spend two days cleaning up the mess with Codex. Hopefully 2.6 does better.
I’m struggling to understand the recent wave of backlash against MCP. As a standard, it elegantly solves a very real set of integration problems without forcing you to buy into a massive framework.
It provides a unified way to connect tools (whether local via stdio or remote via HTTP), handles bidirectional JSON-RPC communication natively, and forces tools to be explicit about their capabilities, which is exactly what you want for managing LLM context and agentic workflows.
This current anti-MCP hype train feels highly reminiscent of the recent phase where people started badmouthing JSON in favor of the latest niche markup language. It’s just hype driven contrarianism trying to reinvent the wheel.
I don't even fully understand what people are suggesting instead. That we use CLI tools for everything? There are lots of things I do and tools I use that cli would be very inefficient for interacting with.
This isn't actually about AI. it's just classic human psychology.
You’ve had a rock-solid workflow for 25 years, so it makes total sense to be cautious and reject features you don't need.
Right now, keeping it at "arm's length" and "read-only" feels safe. But that's usually just phase one. Once that initial trust is established, those boundaries naturally start to melt away. Give it a couple of tax seasons, and you’ll probably find yourself wanting it to take on more of the heavy lifting.
reply