So, I think I interpreted the blog post differently than Lifehacker did. Their idea was "The good news, if you're learning to code, is you don't have to worry (too much) if your code is bad." The impression I get is that you just can't write good code unless you're also doing good writing. That means you're simultaneously writing for an audience with perfect comprehension and no consciousness (computers, that is) and for human beings with plenty of consciousness but far from perfect comprehension. That doesn't sound fun at all. The solution most programmers use is to not even bother.
A few choice quotes from the post echo these sentiments:
Not a single living person knows how everything in your five-year-old MacBook actually works. Why do we tell you to turn it off and on again? Because we don't have the slightest clue what's wrong with it, and it's really easy to induce coma in computers and have their built-in team of automatic doctors try to figure it out for us. The only reason coders' computers work better than non-coders' computers is coders know computers are schizophrenic little children with auto-immune diseases and we don't beat them when they're bad.
The human brain isn't particularly good at basic logic and now there's a whole career in doing nothing but really, really complex logic. Vast chains of abstract conditions and requirements have to be picked through to discover things like missing commas. Doing this all day leaves you in a state of mild aphasia as you look at people's faces while they're speaking and you don't know they've finished because there's no semicolon. You immerse yourself in a world of total meaninglessness where all that matters is a little series of numbers went into a giant labyrinth of symbols and a different series of numbers or a picture of a kitten came out the other end.
It's a good post. It's very cathartic.