>Code is scattered in a vast heirarchy of files. You can't find a definition unless you already know where it is. Not if you're using a proper IDE (or the righ

>Code is scattered in a vast heirarchy of files. You can't find a definition unless you already know where it is. Not if you're using a proper IDE (or the right emacs/vim plugins, which are effectively an IDE). >Code is indented to indicate nesting. As code is edited and processed, this cue is often lost or incorrect. Not if you're using a proper IDE configured for the project's chosen style. My engineering org also has linters in pre-commit hooks and automatically commenting on code reviews. >Sometimes a line of code contains only a parenthesis, or semicolon. This reduces the density of the code, and the difficulty of reading it. Depends on the style guide you choose. Also, some people find this more readable. >There's no documentation. Except for the ubiquitous comments. These interrupt the code, further reducing density, but rarely conveying useful insight. The only documentation I've ever found useful (aside from comments) was automatically generated from comments, explaining the signatures of methods and what they do.