{
  "path": "/what-am-i-plagiarizing-anyway",
  "site": "at://did:plc:xbrsz7emexclcsiqgg3do6ar/site.standard.publication/4jc0vnfuli7xc",
  "$type": "site.standard.document",
  "title": "What am I plagiarizing, anyway?",
  "content": {
    "text": {
      "markdown": "The fun thing about slopcoding is that you have absolutely no idea where the clanker has gotten the building blocks of the slop it excretes. \n\nSo this site's design is a great tangible example, because it's entirely slop-gen'd. So _which site or app did it rip off?_ I can never know, and that's why it'd be a little embarrassing to release this app in any serious manner. Because there might come a day when someone recognizes its origin, and then, like a kid called on in class when I cheated on the test, I'd have no idea how I arrived at the answer. (But this time I'm trying to build a business off this slop, or whatever.)\n\nCodeslop in particular is a _little_ palatable only because it's less **obvious**. The slop bubbles up from the sewer in the form of insidious bugs, dumb verbosity, tech debt, and security gaps, instead of immediately assaulting the ears and eyeballs, as audio/visual slop does.\n\nBut even if the slop is evacuated as CSS instead of pixels, whatever food the clanker initially ate is inscrutable to prompt jockeys like me. And so the slop stench infects every inch of the slop product. "
    },
    "$type": "at.markpub.markdown"
  },
  "description": "The fun thing about slopcoding is that you have absolutely no idea where the clanker has gotten the building blocks of the slop it excretes. ",
  "publishedAt": "2026-04-29T23:26:58Z",
  "textContent": "The fun thing about slopcoding is that you have absolutely no idea where the clanker has gotten the building blocks of the slop it excretes. \n\nSo this site's design is a great tangible example, because it's entirely slop-gen'd. So which site or app did it rip off? I can never know, and that's why it'd be a little embarrassing to release this app in any serious manner. Because there might come a day when someone recognizes its origin, and then, like a kid called on in class when I cheated on the test, I'd have no idea how I arrived at the answer. (But this time I'm trying to build a business off this slop, or whatever.)\n\nCodeslop in particular is a little palatable only because it's less obvious. The slop bubbles up from the sewer in the form of insidious bugs, dumb verbosity, tech debt, and security gaps, instead of immediately assaulting the ears and eyeballs, as audio/visual slop does.\n\nBut even if the slop is evacuated as CSS instead of pixels, whatever food the clanker initially ate is inscrutable to prompt jockeys like me. And so the slop stench infects every inch of the slop product. "
}