Users can tell when something is vibe coded.

Users can tell when something is vibe coded. I've been thinking about this a lot lately. This is a tweet from Dax, one of the co-founders of OpenCode. He says you can vibe code all of it. Who cares? Lie to yourself, pretend it's a clever strategy. But everyone will know. They can feel it in your work, how lazy you've become, how little you care. Because how you do one thing is how you do everything. Here's an example. There's this guy, Steve. He's completely vibe coded this. Like, uh, Jira for AI's, like ticket management for AI Agents. It's called Beads. It has 15,000 stars on GitHub, so really popular. I was kind of hooked by the concept. It made sense to me, I install it and I run BD help to see what the CLI commands are. Look at this. This is all CLI Arguments. That this seemingly simple like Jira for your AI Agent has at its disposal. I think this is more commands than the Google Cloud CLI. It's just so obviously slop. Like, yes, use the AI to vibe code, but you gotta clean it up because it's gonna slop all over the place. So I instantly uninstalled Beads because for all I know, it's probably spawning like multiple worker threads whenever I try to just query what tickets I have. But moral of the story, from what I'm seeing there, are so many devs who are just slopping their way to completion. Use the vibe coding: It's powerful. But clean it up. People can tell.