{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaoqkyy4dplvnhgoiw74uuy6z6w46cyadvtxxfbgm2xdanbhchx6u",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjbnq74elz32"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918?page=2#post_24",
  "publishedAt": "2026-04-12T05:36:55.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "ocharles:\n\n> “The same as X but scaled to another level” is entirely meaningless.\n\nQuite the contrary.\n\nStackOverflow copy-paste programming is characterized by people…\n\n  * re-using code snippets they have not written\n  * that they don’t understand\n  * and have no intention of understanding\n\n\n\nThat means they created three types of debts:\n\n  * intent debt (the code may not be intended for what they actually wanted to do, but there’s an accidential overlap of functionality that seems it is what they need/want)\n  * cognitive debt (lack of understanding, no agency and responsibility)\n  * technical debt (code quality, lack of abstraction, etc.)\n\n\n\nLLMs indeed scale this to another level, because you can now compose code snippets you haven’t written, don’t understand and don’t know the intention of.\n\nocharles:\n\n> Are you trying to make a constructive point, or just trying to bait a flame war?\n\nMy topic has a very specific question. If you don’t want to contribute to solving the problem, then you don’t have to engage in this discussion.",
  "title": "How to filter out vibe-coded dependencies"
}