Abstract

There is a common failure among both novice and experienced programmers to recognize the importance of the human reader when writing software. The following guidelines are based upon the professional experience of 15 years reading over 2 million lines of other people's software in a variety of languages. Their brevity is a consequence of the desire to avoid language-specific issues.

You do not currently have access to this article.