{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicnpqsl2dk4fdovtirmnbk6mqtshrfp5onyjxkffsfksv6dasuqvm",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mh6syhksu772"
  },
  "path": "/t/yet-another-opinion-on-llms-hasufells-blog/13775?page=3#post_43",
  "publishedAt": "2026-03-16T09:58:48.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "The one thing that sticks with me is how well I think the LLM performs always seems to correlate with my knowledge of the problem space. The better I understand the domain and technology that is being used the worse the LLM is. Maybe the things I understand well are things LLMs are bad at? I find that hard to believe though.\n\nI also can’t figure out if I am more productive, I can certainly do more things, but am I more productive because of that? Does me churning out a new feature or developer tool fast bring a net gain? I have the firm belief that anything we create also introduces some debt that must be paid at some point and our job is to reduce that debt as much as possible. AI makes it very easy to just create and not think about technical debt.\n\nI have always thought software engineering to be a crazy profession as we have no professional standards, and this AI train we are on makes it seem like that was very much by design. We can vibecode and sell software, and as long as it appears to do what the client wanted that’s good enough. I wish I could sell bridges built with the cardboard in my shed, well maybe I don’t.",
  "title": "Yet another opinion on LLMs · Hasufell's blog"
}