> 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’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.
The "Junior Trap" is real: if you offload your thinking to Claude or GPT-4, you’re hitting "Done" for the day, but you’re accruing massive Learning Debt. You aren't building the failure-pattern recognition that actually makes an engineer valuable.
In a world where "Code is no longer a skill," the only way to survive is to stop being a "Prompt Operator" and start being a "System Auditor." If you can’t explain the trade-offs of the architectural pattern the AI just gave you, you aren't an engineer, you're just the person holding the screwdriver while the machine builds the house.
Amazing work! I'd love to hear more details about your workflow with Claude Code.
As a side note and this isn't a knock on your project specifically. I think the community needs to normalize disclaimers for "vibe-coded" packages. Consumers really need to understand the potential risks of relying on agent-generated code upfront.