I don’t think it has anything to do with vibe coding, the problem with MCP is just it needed to be done fast (because otherwise another protocol would appear and get all the hype) and needed to be very easy to use for hobbyists (again: to get hype, Enterprise software is boring)
There’s an old joke. Uh, two elderly women are at a Catskills mountain resort, and one of 'em says: “Boy, the food at this place is really terrible.” The other one says, “Yeah, I know, and such small portions.” Well, that’s essentially how I feel about life. Full of loneliness and misery and suffering and unhappiness, and it’s all over much too quickly.
Yeah the principal engineer at my company is just smashing his keyboard every day to implement MCP services and shit and in the meantime is fucking up our repo and I’m trying to clean up the mess but all upper management cares about is “when AI?”
He’s not vibe coding it, but as with all the MCP specs, it’s ignoring many things about type safety and the like pointed out in this article
I don’t think it has anything to do with vibe coding, the problem with MCP is just it needed to be done fast (because otherwise another protocol would appear and get all the hype) and needed to be very easy to use for hobbyists (again: to get hype, Enterprise software is boring)
Sounds like JavaScript
What you’re describing is definitely the AI vibe: full speed at the cost of quality, logic, and all else.
To (quite badly) paraphrase Woody Allen:
“The quality of this code is so bad.”
“Well, at least there’s a lot of it.”
What’s the original quote?
https://www.youtube.com/watch?v=lDxE4r5ixD0
Yeah the principal engineer at my company is just smashing his keyboard every day to implement MCP services and shit and in the meantime is fucking up our repo and I’m trying to clean up the mess but all upper management cares about is “when AI?”
He’s not vibe coding it, but as with all the MCP specs, it’s ignoring many things about type safety and the like pointed out in this article