The Elements of Programming Style

I have happened to notice our school library provides this book, written by [Kernighan](http://cm.bell-labs.com/cm/cs/who/bwk/) and [Plauger](http://www.plauger.com/).

I found the guidelines not as surprising as the fact that our library has a copy---the book is a classic, after all,
and often quoted. Although some of the guidelines are Fortran-specific, most of them are still valid; it was
useful to read them all in one place.

I found other aspects of the book much more interesting, though:

You can't please everyone

[Include Mono](https://www.redhat.com/archives/fedora-extras-list/2005-March/msg00279.html)
or [not](https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177604),
somebody will always want the opposite.

Ugly design tends to imply bugs

Quoting the `tcsh` manual page:

>

>

break

>

Causes execution to resume after the end of the nearest enclosing
> foreach or while.
> The remaining commands on the current line are executed. Multi-level breaks are thus possible by writing
> them all on one line.

>

"The remaining commands on the current line are executed".