{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihra4gueerdenxdxa64qtkq4ggwzv2zff3drzr4frurfbuk7hkq7y",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mkwiwexjqkj2"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918?page=4#post_71",
  "publishedAt": "2026-05-03T04:54:19.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "[1]"
  ],
  "textContent": "lol i gave you evidence though. all the non-haskell AI code being deeply garbage making the news lately. you have fintechs releasing excel clones that exfiltrate user data. that’s a whole program in prod [1] that passed a whole company’s release process and made it to prod lol.\n\nit’s pretty clear that AI written code is problematic. it has been measured to have more bugs and - worse - more vulns\n\njust because haskell doesn’t have a rich zoo of examples doesn’t mean it’s immune\n\nit just means that haskell is teeny tiny and doesn’t have a glut of AI activity going on\n\n_maaaaybe_ it also means haskell has a slight inborn immunity to AI cancer. whether that is from its niche nature (less training data) or its type system or its culture ..idk",
  "title": "How to filter out vibe-coded dependencies"
}