{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib2m2mbspizgkz5knfrqrf4hgpirkre5qtlmll5as7mars2if7ixe",
    "uri": "at://did:plc:vyjlfm46mfv6u4vjp6qtrfx2/app.bsky.feed.post/3mhqo2rxlequ2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreidg2k33tiuupnstmiowh7hyyvtsbe3gyhfygiytrzynysnhoctrxi"
    },
    "mimeType": "image/jpeg",
    "size": 81260
  },
  "path": "/articles/completely-readable",
  "publishedAt": "2026-03-23T06:30:00.000Z",
  "site": "https://thedailywtf.com",
  "tags": [
    "CodeSOD",
    "Learn more."
  ],
  "textContent": "It is eminitently reasonable for companies to have \"readability standards\" for their code. You're writing this code _for humans_ to read, after all, at least in theory. You need to communicate to future inheritors of your code.\n\nBut that doesn't mean readability standards are _good_. **Tony** 's company, for example, has rules about returning boolean values from functions, and those rules mean you are _expected_ to write code like this:\n\n\n    public bool Completed ()\n    {\n       if (completed == true)\n       {\n       return true;\n       }\n       else\n       {\n       return false;\n       }\n    }\n\n\nIt's more \"explicit\" this way. Which I certainly would have explicit things to say if I were told I needed to write code this way. Also, what's with the non-indented `return` statements? Is that also part of their coding standards?\n\n[Advertisement] ProGet’s got you covered with security and access controls on your NuGet feeds. Learn more.",
  "title": "CodeSOD: Completely Readable"
}