{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreig2wc6ajmustl4uevb4ol5kbhoaj44dcuhrwqpkfgwaprgyjkcoly",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjasvck7rh52"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918#post_10",
  "publishedAt": "2026-04-11T16:26:23.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "Then you should probably not use tower-hs then. Its been actively developed with claude code, interactively, but given the vague terms of vibe coding, its extreme hard to distinguish between the two types of development. In one hand with pure vibe coding, the developer (or the project “manager”) doesnt know ANYTHING about the code, hopefully just that it works for him. In my case and the other use of a AI, i actually read through everything claude suggests and try to understand it and if it makes sense. I dont blindly accept anything just to “get something working” because then it can work or not work in ways its not intended to.",
  "title": "How to filter out vibe-coded dependencies"
}