{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifvnqovo7zwu3ar5f563xsalzk65mcl2rjba6hh63uz56fbcyffeu",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjastktusv52"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918#post_14",
  "publishedAt": "2026-04-11T18:38:36.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "I suspect a lot of the vibe coding is more work than people let on. But they wanna sell the magic.\n\nI tried to have Claude code up a tool that would use Claude API to fill typed holes. I did it twice and used `/plan`. It made pretty egregious errors both times (not feeding errors back into the context, not reacting to compilation failures at all, not parsing GHC diagnostic JSON correctly somehow)\n\nI could’ve just iterated with Claude. But now that’s already programming with extra steps to me. It’ll be easier just to program it myself.",
  "title": "How to filter out vibe-coded dependencies"
}