Quotes About Efficiency

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 majority of the cost of a software project is in long-term maintenance.

Recall that the goal of an architect is to minimize the human resources required to build and maintain the required system.

A stitch in time saves nine. The early bird catches the worm. Don't put off until tomorrow what you can do

The only way to make the deadline—the only way to go fast—is to keep the code as clean as possible at all times.

Duplication and expressiveness take me a very long way into what I consider clean code, and improving dirty code with just these two things in mind can make a huge difference. There is, however, one other thing that I'm aware of doing, which is a bit harder to explain.

A stitch in time saves nine. The early bird catches the worm. Don't put off until tomorrow what you can do today.

The team is working along at a certain productivity. Then new staff is added. Productivity plummets for a few weeks as the new people suck the life out of the old people. Then, hopefully, the new people start to get smart enough to actually contribute.

There is no such thing as quick and dirty. Anything dirty is slow. The only way to go fast, is to go well.

You should be able to run all the unit tests with just one command.

The most efficient and effective way to review code is to collaborate in writing it.

QA and Acceptance Tests If QA has not already begun to write the automated acceptance tests, they should start as soon as the IPM ends. The tests for stories that are scheduled for early completion should be done early. We don't want completed stories waiting for acceptance tests to be written.

The tests fit the production code like an antibody fits an antigen.

refactored)    /**

Duplication may be the root of all evil in software. Many principles and practices have been created for the purpose of controlling or eliminating it.

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.

software has two types of value: the value of its behavior and the value of its structure.

O objetivo da arquitetura de software é minimizar os recursos humanos necessários para construir e manter um determinado sistema.

It doesn't take a huge amount of knowledge and skill to get a program working. Kids in high school do it all the time. Getting it right is another matter entirely. When software is done right, it requires a fraction of the human resources to create and maintain.

Duplication may be the root of all evil in software.

The fact is that making messes is always slower than staying clean, no matter which time scale you are using.

Any comment that forces you to look in another module for the meaning of that comment has failed to communicate to you and is not worth the bits it consumes.

To build a system with a design and an architecture that minimize effort and maximize productivity, you need to know which attributes of system architecture lead to that end.