{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihingzz34d3d3ivf3cpzywypejbmkffb5z2oyxmbki6lnvmxcpf3m",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mgluus2nhdm2"
  },
  "path": "/t/haskell-vibes-jappie/13772#post_4",
  "publishedAt": "2026-03-09T00:58:29.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "I have very mixed feelings on AI use in programming (I detest the thief machine), but I will say this:\n\nOne of the few things that LLMs are actually well-designed for (as opposed to shoehorning things into one because business majors* have confused the ability to speak with that of intelligence), is syntax. So it makes some amount of sense that a rigorous language like Haskell would benefit quite strongly from machine learning supporting the disambiguation and rectification of syntactic errors.\n\nIndeed, this is my current approach to AI coding assist (aside from reformatting, which admittedly is also helpful); I find that it can be extremely helpful in remembering what particular brand of properties I need (gadts vs type families vs fundeps hmmmm), or exactly how many stars deep I am - mechanical, syntactic things.\n\nThe moment it goes from manipulating syntax to generating content, it tends to be less useful, so any actual prompts I write are rare, concise, targeted, and abstracted / stripped of non-essential context. Even then it fucks things up quite often, so I only let it suggest things, and do not let it make any changes itself. Half the time I solve my own problem without submitting.\n\n> * I remember the flood of “programmers” in the 2010s who copied other people’s repos, attended a single coding bootcamp, got a job, and immediately dropped out of coding to get promoted to manager; they are now by and large the very managers and executives pushing AI slop today.",
  "title": "Haskell 💜 Vibes / Jappie"
}