{
  "path": "/slop-in-slop-out",
  "site": "at://did:plc:xbrsz7emexclcsiqgg3do6ar/site.standard.publication/4jc0vnfuli7xc",
  "$type": "site.standard.document",
  "title": "Slop in, slop out",
  "content": {
    "text": {
      "markdown": "The slopcoding is still coming along. As the project is growing more complex, the clanker is screwing up or missing important details along the way. The ideal stage for slopcoding is always in the beginning.\n\nWhen I need to dive in, the code looks like ass. Functional, but made of shit. It is the kind of code you produce when you are in a hurry -- or in this case, running out of tokens. So manual changes I'm saving till the end, once all the meat is there and we only need to refine it.\n\nI'll keep dogfooding this as it develops to figure out what's missing."
    },
    "$type": "at.markpub.markdown"
  },
  "description": "The slopcoding is still coming along. As the project is growing more complex, the clanker is screwing up or missing important details along the way. The ideal stage for slopcoding is always in the beginning.",
  "publishedAt": "2026-04-07T19:52:37Z",
  "textContent": "The slopcoding is still coming along. As the project is growing more complex, the clanker is screwing up or missing important details along the way. The ideal stage for slopcoding is always in the beginning.\n\nWhen I need to dive in, the code looks like ass. Functional, but made of shit. It is the kind of code you produce when you are in a hurry -- or in this case, running out of tokens. So manual changes I'm saving till the end, once all the meat is there and we only need to refine it.\n\nI'll keep dogfooding this as it develops to figure out what's missing."
}