Quotes About Readability

Readability of code is now my first priority. It's more important than being fast, almost as important as being correct, but I think being readable is actually the most likely way of making it correct.

So your first sentence should be very compelling by virtue of its short length and ease of reading. No long multisyllabic words. Keep it short, sweet and almost incomplete so that the reader has to read the next sentence.

When used to best advantage, exceptions can improve a program's readability, reliability, and maintainability. When used improperly, they can have the opposite effect.

A good writer is one you can read without breaking a sweat.

A trap screenwriters can fall into is making scripts that are good reads, which doesn't necessarily mean it will make a good film.

14. Song and Schwarz, "If It's Hard to Read, It's Hard to Do.

[Perl] combines all the worst aspects of C and Lisp: a billion different sublanguages in one monolithic executable. It combines the power of C with the readability of PostScript.

Clean code is simple and direct. Clean code reads like well-written prose. Clean code never obscures the designer's intent but rather is full of crisp abstractions and straightforward lines of control. - Grady Booch author of Object Oriented Analysis and Design with Applications

No matter how elegant it is, no matter how readable and accessible, if it hath not tests, it be unclean. Dave

Code, without tests, is not clean. No matter how elegant it is, no matter how readable and accessible, if it hath not tests, it be unclean. Dave

Clean code can be read, and enhanced by a developer other than its original author. It has unit and acceptance tests. It has meaningful names. It provides one way rather than many ways for doing one thing. It has minimal dependencies, which are explicitly defined, and provides a clear and minimal API. Code should be literate since depending on the language, not all necessary information can be expressed clearly in code alone. -Dave Thomas, founder of OTI, godfather of the Eclipse strategy

We want our code to be a quick skim, not an intense study.

Because this ratio is so high, we want the reading of code to be easy, even if it makes the writing harder. Of course there's no way to write code without reading it, so making it easy to read actually makes it easier to write.

Making the code read like a top-down set of TO paragraphs is an effective technique for keeping the abstraction level consistent.

So if you want to go fast, if you want to get done quickly, if you want your code to be easy to write, make it easy to read.

Perhaps you thought that "getting it working" was the first order of business for a professional developer. I hope by now, however, that this book has disabused you of that idea. The functionality that you create today has a good chance of changing in the next release, but the readability of your code will have a profound effect on all the changes that will ever be made.

As far as he can achieve it, readability is as important for the scientific writer as it is for the novelist.

existen creencias colectivas por así decir asintomáticas: brotan y se propagan utilizando la conciencia individual como incubadora inconsciente y permanecen sustancialmente ilegibles hasta el momento en que emergen con la rapidez de una pandemia

It seems certain that much of the success of Unix follows from the readability, modifiability, and portability of its software.

There is a difference between art and life and that difference is readability.

Of all the needs a book has, the chief need is that it be readable.

Of all needs a book has, the chief need is to be readable.

The argument that a serif font is too fussy doesn't cut it anymore. You want a font where the letter forms are not ambiguous.

I don't want my readers slowed down by long passages of narrative.