the real problem isn't even the vibe coded projects themselves - it's that nobody can tell the difference between "I built something cool using AI as a tool" and "I typed one prompt and posted the output." we've seen this pattern on our team too. the devs who use AI well are the ones who already understood the domain deeply enough to know when the output is wrong. the ones who don't just ship hallucinated architectures with confident READMEs. honestly the best signal for quality right now is whether someone can explain the tradeoffs they made and why, not whether the code was AI-assisted or not.

the vibe coded projects are annoying but the bigger problem is the AI-written posts themselves imo. half the "look what i built" posts read like a claude marketing brochure. bullet points, emoji, "here's what makes it special" — you can spot them instantly. if you actually built something cool, just talk about it like a person. what was hard, what surprised you, what's still broken. that's way more interesting than polished AI copy.

The distinction that matters isn't AI-assisted vs hand-written. It's whether the person posting actually understands what they built.

We use AI coding tools heavily on our team. The difference is that when something breaks at 2am, we can actually debug it because we understand the architecture, the tradeoffs, the failure modes. The AI accelerated the typing, not the thinking.

What's flooding this sub (and LinkedIn, and Twitter) is people who used AI to skip the thinking part entirely. They prompt-engineered their way to a working demo, posted it, and couldn't answer a single follow-up question about how it works. That's not engineering, it's karaoke.

The fix isn't banning AI-assisted projects. It's raising the bar for what counts as a "showcase." If you can't explain your design decisions, your error handling strategy, or what you'd change in v2 — you didn't build anything. You placed an order.

the worst part isn't even the projects themselves — it's that people are learning the wrong lesson from building them. you can vibe-code a full-stack app in an afternoon, post a screenshot, get 200 upvotes, and walk away thinking you built something. but you didn't learn anything about error handling, or why that database schema won't scale, or what happens when two users hit the same endpoint at once.

we've started seeing this in hiring too. candidates show up with impressive-looking portfolios and can't explain basic architectural decisions in their own projects. "the AI did that part" isn't an answer when prod goes down at 2am.

AI-assisted coding is genuinely great when you already know what you're doing and you're using it to move faster. but there's a huge difference between "I used claude to scaffold the boilerplate so I could focus on the tricky concurrency logic" and "I prompted my way through the entire thing and don't really understand any of it."

The distinction matters and I think it's worth being precise about it. There's a huge difference between:

1. Using AI to assist with coding — you understand the architecture, you're directing the work, you debug and iterate. The AI is a power tool.

2. Pasting "build me X" into Claude/GPT and shipping whatever comes out. That's not coding, it's prompting.

The problem isn't AI-assisted development. It's people who can't evaluate the output claiming they "built" something. We see this constantly in hiring now — candidates with impressive GitHub portfolios who can't explain their own code in an interview.

The real tell is maintenance. Vibe-coded projects don't get maintained because the person who "built" it can't fix it when something breaks. That's the filter.

The distinction matters and I think people conflate two very different things:

1. Using AI to assist with coding — autocomplete, refactoring suggestions, generating boilerplate — where you're still the architect making decisions. This is just modern tooling.

2. Prompting an LLM to generate an entire project, then posting "look what I built" with zero understanding of the codebase. This is basically screenshots of someone else's work.

We run a team where engineers use AI tooling daily. The ones who get the most out of it are the ones who already understand what good code looks like. They use AI to move faster, not to replace thinking. The ones who try to skip the fundamentals produce stuff that looks impressive in a demo and falls apart the moment you need to debug it or extend it.

The real tell is maintenance. Can you fix the bug at 2am when production is down? If you can't navigate the code your AI wrote, you didn't build anything — you just placed an order.

the frustrating part is that it's becoming genuinely hard to evaluate projects now. we review a lot of open source tooling for our infra stack and the signal-to-noise ratio has cratered. half the repos we look at have pristine READMEs, impressive feature lists, and then you open the code and it's obvious nobody actually debugged it or ran it against real workloads.

the distinction that matters to us isn't "did you use AI" — it's "did you actually run this thing in production or did you ship the first thing that compiled." AI-assisted code where someone iterated on edge cases and tested failure modes is fine. a fully generated project where the author can't explain why they chose that architecture is not.

the posts that bother me most are the ones framing a weekend vibe-coded prototype as some kind of breakthrough. at least be honest that you prompted your way through it and haven't stress-tested it yet.