{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibu5pjg27jjx2i7daumqfriksykbwzxov4qfmykd4icsfkfclqfym",
    "uri": "at://did:plc:hwpfviglvxef74s5w4fhywt7/app.bsky.feed.post/3mdtesjhnxax3"
  },
  "contributors": [
    {
      "did": "did:plc:dqehxkfb3kv6bx7tfkvyzdt4",
      "role": "author"
    }
  ],
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreih6cueeviw6ckjtbb2m3cfpozpvnera5jp3g24whgjcuoqf4rjk3y"
    },
    "mimeType": "image/png",
    "size": 44664
  },
  "description": "Most programming — and sysadmin — problems can be debugged in a fairly straight forward manner using logs, print statements, educated guesses, or an actual debugger. Sometimes, though, the problem is more elusive. There’s a wider box of tricks that can be employed in these cases but I’ve not managed to find a nice overview of them, so here’s mine. I’m mainly foc...",
  "path": "/debugging-beyond-the-debugger/",
  "publishedAt": "2019-05-08T00:00:00Z",
  "site": "at://did:plc:hwpfviglvxef74s5w4fhywt7/site.standard.publication/3mnmr7tmggs2e",
  "title": "Debugging beyond the debugger"
}