1. I wasn&#x27;t claiming to justify the bullet points, just pointing out that teaching rules without justification causes &quot;bundling&quot; and might have implications beyond the narrow thing you&#x27;re trying to teach.<p>2. Notice that I said I indent my code. I deliberately chose the phrase &quot;not very important&quot; rather than &quot;not useful&quot;. Your links seem to back me up there. The fact that those studies on line length yield equivocal results, might it not suggest that the <i>content</i> of the lines has a larger impact on comprehension? I can agree with you that a few scattered islands in the ocean have land, and still consider you wildly misguided for choosing to explore them rather than the huge continental landmass beyond the ocean.<p>3. I think most code is utterly illegible gibberish to everyone but the author[1][2]. This isn&#x27;t directly the fault of code-style rules, but it <i>is</i> caused by the pernicious idea that the code style rules are all you need. Now, nobody actually thinks that, but spending a lot of time talking about superficial details gives the mind a powerful subconscious cue.<p>[1] <a href="http:&#x2F;&#x2F;akkartik.name&#x2F;about" rel="nofollow">http:&#x2F;&#x2F;akkartik.name&#x2F;about</a><p>[2] <a href="http:&#x2F;&#x2F;akkartik.name&#x2F;post&#x2F;readable-bad" rel="nofollow">http:&#x2F;&#x2F;akkartik.name&#x2F;post&#x2F;readable-bad</a>