Quotes About Simplicity

In general, it is harmful to depend on modules that contain more than you need. This is obviously true for source code dependencies that can force unnecessary recompilation and redeployment—but it is also true at a much higher, architectural level.

The problem isn't the simplicity of the code but the implicity of the code (to coin a phrase): the degree to which the context is not explicit in the code itself.

is not the language that makes programs appear simple. It is the programmer that make the language appear simple!

Professionals use their powers for good and write code that others can understand.

Resisting premature abstraction is as important as abstraction itself.

That these acts are simple doesn't mean that they are simplistic, and it hardly means that they are easy.

A good architect maximizes the number of decisions not made.

THE COMMON REUSE PRINCIPLE Don't force users of a component to depend on things they don't need.

Clean code is focused. Each function, each class, each module exposes a single-minded attitude that remains entirely undistracted, and unpolluted, by the surrounding details.

Whether you are designing systems or individual modules, never forget to use the simplest thing that can possibly work.

Ward's principle: "You know you are working on clean code when each routine turns out to be pretty much what you expected.

When software is done right, it requires a fraction of the human resources to create and maintain. Changes are simple and rapid. Defects are few and far between. Effort is minimized, and functionality and flexibility are maximized.

The measure of design quality is simply the measure of the effort required to meet the needs of the customer. If that effort is low, and stays low throughout the lifetime of the system, the design is good. If that effort grows with each new release, the design is bad. It's as simple as that.

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.

It is not the language that makes programs appear simple. It is the programmer that make the language appear simple!

One difference between a smart programmer and a professional programmer is that the professional understands that clarity is king. Professionals use their powers for good and write code that others can understand.

Programmers must avoid leaving false clues that obscure the meaning of code.

A chrysanthemum by any other name would be a lot easier to spell.

la importancia de mantener las relaciones más estrechas posible con los clientes; la necesidad de conservar las ideas en el nivel más simple y realista posible; el valor de crear un producto superior y de ganar por habilidad, en oposición a hacer que todo apunte a ganar dinero.

To think that by doing more you are doing better is a common blunder. It is never good to seem to be trying too hard—it is as if you were covering up some deficiency.

An excess of simplicity, after all, was just another form of ostentation, and pride in one's humility a sin.

like interviewing a new cleaner. Do you want someone who can give you the history of cleaning and the theory of cleaning, or do you want someone who'll just get down and clean your fucking house? They chose you because they think you'll clean their fucking house.

His theory of oratory, the exact opposite of the Asiatics', was simple: don't move about too much, hold your head straight, stick to the point, make 'em laugh, make 'em cry, and when you've won their sympathy, sit down quickly –

He had learned well from Cicero the tricks of political campaigning: keep your speeches short, remember names, tell jokes, put on a show; above all, render an issue, however complex, into a story anyone can grasp.