{
  "video_id": "reddit_1vq8ahg",
  "channel_slug": "ClaudeAI",
  "channel_handle": "r/ClaudeAI",
  "title": "Curious, what does vibe-coded code read like to original coders?",
  "url": "https://www.reddit.com/r/ClaudeAI/comments/1vq8ahg/curious_what_does_vibecoded_code_read_like_to/",
  "external_url": null,
  "upload_date": "20260816",
  "published_at": "2026-08-16T20:51:37+00:00",
  "transcript": "I love vibe-coding. It's brought some of my educational dreams to life. I'm curious though, AI writing has a distinctly inhuman feel with errors that range from awkward vernacular to metaphors that miss the target by a country mile. What's it like for original coders to read vibe-coded code? Is it odd in similar ways to reading AI generated language? Or less odd because code has incorporated machine logic from the outset? Or...?\n\n\n\n--- Top Comments ---\n\n\n[1 upvotes] **TL;DR of the discussion generated automatically after 100 comments.**\n\nThe consensus from the devs in this thread is pretty clear, OP.\n\n**AI-generated code is immediately recognizable by its insane number of comments.** While a human might leave a single, cryptic comment like \"when I wrote this only God and I knew how it worked... now only God does,\" Claude will write a five-paragraph essay for a function that just adds two numbers.\n\nOther dead giveaways include:\n\n*   **It's verbose and over-engineered.** The AI loves creating complex abstractions and using way more code than necessary, like it was trained exclusively on programming tutorials. Pros call this ignoring the \"YAGNI\" (You Aren't Gonna Need It) principle.\n*   **The architecture is a \"tin shack.\"** This is the biggest red flag for experienced coders. While individual functions might work, the overall structure of a vibe-coded app is often brittle and liable to collapse if you look at it wrong.\n*   **It's great for prototypes, bad for production.** It's amazing for quickly spinning up a proof-of-concept, but you're creating a mountain of tech debt if you try to build a serious, scalable application this way.\n\nThe general\n\n[139 upvotes] It’s weird when it has comments. The only comments I used to see were things like “when I wrote this only God and I knew how it worked. Now only God does. Abandon all hope Yee who enter here”.\n\n[70 upvotes] Very verbose. I.e lots of code to do what could be shorter. The occasional glaring bug. Depends a lot on the model being used. \n\n[67 upvotes] It’s very organized and well structured. Which is good but most of the time it is also very verbose and big. Sometimes also a bit overengineered. The quality is good though (given that you use a frontier model codex 5.6 or Opus/ Fable5)\n\nI’m coding for 15+ years, bot nowadays I am more of a reviewer I guess. Sometimes I nudge it in a different direction.  \n   \nMost importantly it’s the context you give it. Shit in, is shit out. But clear defined acceptance criteria go a very long way. That with repo contextual support files and some related skills and you’re golden.  \n    \nDon’t wing it all at once too, take it feature by feature.",
  "transcript_chars": 2674,
  "ingested_at": "2026-08-17T01:30:09.581182+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 61,
    "upvote_ratio": 0.81,
    "num_comments": 111,
    "author": "ComposerNo8415",
    "is_self": true
  }
}