{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigzcqxh533dvqq2gclrbcwxx7ndoal5hwj5k3e2xoxnscbxlms374",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjbnqholhlt2"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918?page=2#post_22",
  "publishedAt": "2026-04-12T05:26:11.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "It’s the same as StackOverflow copy-paste programming, just scaled to an entire different level.\n\nAll the same caveats apply.\n\nSure, there are some nuances (e.g. someone could vibecode an entire app and then read every single line of code with the intent of understanding it or someone could just use it for certain parts, etc. etc.). But this was also the case before.\n\nI don’t think there’s much point in having a discussion about an exact definition. That’s why I said it’s an indicator. Most of the time it’s instant legacy code. There’s a large spectrum in between, but LLMs have turned out to be less useful for that spectrum anyway.\n\nIt’s fine if a blocklist has false-positives. I’m not looking for an exact solution.",
  "title": "How to filter out vibe-coded dependencies"
}