Quotes About Efficiency

Clear, well-thought-out navigation is one of the best opportunities a site has to create a good impression.

A person of average (or even below average) ability and experience can figure out how to use the thing to accomplish something without it being more trouble than it's worth. Take my word for it: It's really that simple.

A person of average (or even below average) ability and experience can figure out how to use the thing to accomplish something without it being more trouble than it's worth.

Get rid of half the words on each page, then get rid of half of what's left. —KRUG'S THIRD LAW OF USABILITY Of

FOCUS RUTHLESSLY ON FIXING THE MOST SERIOUS PROBLEMS FIRST

Nothing important should ever be more than two clicks away.

Even if you do a few things right, such as making high use of modern programming practices, you might still make a mistake that nullifies your productivity gains.

Classes and routines are first and foremost intellectual tools for reducing complexity. If they're not making your job simpler, they're not doing their jobs.

in the vast majority of systems, efficiency isn't critical.

You save time when you don't need to have an awards ceremony every time a C statement does what it's supposed to. Moreover

Hurrying to solve a problem is one of the most time-ineffective things you can do.

One key to successful programming is avoiding arbitrary variations so that your brain can be free to focus on the variations that are really needed.

The gap between the best software engineering practice and the average practice is very wide—perhaps wider than in any other engineering discipline. A tool that disseminates good practice would be important. — Fred Brooks

developer testing should probably take 8 to 25 percent of the total project time.

Immature testing organizations tend to have about five clean tests for every dirty test.

Mature testing organizations tend to have five dirty tests for every clean test.

it's done by creating 25 times as many dirty tests

Eighty percent of the errors are found in 20 percent of a project's classes or routines

It's better to wait for a productive programmer to become available than it is to wait for the first available programmer to become productive.

code reading detected about 80 percent more faults per hour than testing

Be sure that the names you choose favor read-time convenience over write-time convenience.

you shouldn't be uneasy about any parts of the architecture. It shouldn't contain anything just to please the boss. It shouldn't contain anything that's hard for you to understand. You're the one who'll implement it; if it doesn't make sense to you, how can you implement it?

Don't run the camera nonstop. Even if you're going to edit later, it's a bad habit that will only cost you time when you have to watch tons of thoughtless, unusable footage.

the Internet is brilliantly efficient at shifting information from the hands of those who have it into the hands of those who do not.