The Vibe Coding Ick

The app didn't change when you learned it was vibe coded. Your opinion of it did. A look at what that reflex is actually measuring.

#ai#vibe-coding#software#culture

Hi frens,

There’s a specific kind of whiplash happening in tech right now. Someone shows you an app. It’s clean, it works, it solves a real problem you had. You’re impressed. You ask the obvious follow-up — “wait, how’d you build this?” — and the answer arrives: “Oh, I vibe coded it.”

Something shifts. Not always consciously, not always fairly, but it shifts. The app hasn’t changed. Not a single line of it is different than it was thirty seconds ago. But your opinion of it just took a hit. That’s the ick.

Why the reveal changes the reaction

The ick, in its original dating-app sense, isn’t really about the thing itself — it’s about what the thing reveals. Someone doesn’t become less attractive because they mispronounced a word; they become less attractive because the mispronunciation punctured an illusion of effortless competence you’d built around them. Vibe coding produces the same puncture. The polish suggested mastery, and the reveal suggests the polish was borrowed.

A few things seem to be doing the work here:

Craftsmanship signaling collapses. Software has always carried an implicit story: someone understood this problem deeply enough to solve it. When you learn an app was mostly prompted into existence, that story rewrites itself as “someone described a problem well enough that a model solved it.” Both are real achievements, but they’re not the same achievement, and people’s respect was calibrated to the first one.

Trust becomes retroactively uncertain. If the builder didn’t write the auth logic, do they know if it’s solid? If they didn’t design the database schema, do they know what happens at 10,000 users instead of 100? The ick isn’t really aesthetic — it’s a fast, informal risk assessment. Sometimes it’s an accurate one.

It reopens the gatekeeping instinct. Programming has spent decades building status hierarchies around who “really” knows how to code. Vibe coding is a fairly direct threat to that hierarchy, and icks are an efficient way status hierarchies defend themselves — much faster than an argument, much harder to counter, because it doesn’t present itself as an argument at all.

The case that the ick is unfair

None of this means the reaction is correct. A few counterpoints worth sitting with:

  • Plenty of “real” engineers ship code copied from Stack Overflow, generated by autocomplete, or written by a junior they never fully reviewed. The line between “coded it” and “orchestrated it being coded” was never as clean as the ick pretends.
  • An app that works, that people use, that solves the problem — worked. The method is interesting, but it isn’t the product.
  • Every democratizing tool in software history has triggered this exact reflex. Visual Basic, no-code website builders, WordPress, drag-and-drop app makers — all were treated as lesser, all let more people build things, and the ick attached to each one faded roughly in proportion to how many good things got built with it.

The case that it’s earned, sometimes

The ick isn’t always just status anxiety in disguise. Vibe-coded apps do fail in characteristic ways: quietly broken edge cases, security holes nobody thought to check for, a founder who genuinely can’t answer “what happens if this API goes down” because they never had to think about it. When the ick shows up after a data breach rather than before one, it’s not snobbery — it’s a correction that arrived too late.

What’s actually being negotiated

Underneath the discourse, this is a fight over what “building something” is allowed to mean. For a while yet, that definition is going to be genuinely unsettled, and the ick is just one of the more visible symptoms of the unsettling. It’ll probably fade the way it always has — not because anyone wins the argument, but because enough vibe-coded things work well enough, for long enough, that “how” stops feeling like the load-bearing question and “does it work” quietly takes its place again.

Until then: build the thing, ship the thing, and expect a little bit of side-eye at the dinner table when someone asks how you did it.

-IH