"Testing gathers information about a product; it does not fix things it finds that are wrong. Testing does not improve a product; the improving is do… - Gerald M. Weinberg

Testing gathers information about a product; it does not fix things it finds that are wrong.

Testing does not improve a product; the improving is done by people fixing the bugs that testing has uncovered.

why is it so hard for developers to submit their work for review by others or to try to improve their own skills by reviewing the work of others? Curiously, superior developers tend to find value with walkthrough and inspection processes while the merely clever do not. So, as always, the good get better and the bad get worse.

In the army — old-fashioned style — every foot-soldier was considered interchangeable with every other. The hierarchical organization, then, was conceived as the structure that could give the fastest and most direct coordination between these interchangeable parts. But a programming project is not a battle, regardless of appearances. There is no need for quite the speed of communication which is necessary under field conditions, nor are the things to be communicated so simple that they can be barked over a two-way radio with shells bursting in the background. What is needed in a programming project is slow, careful communication among teams of people doing very different, highly specialized tasks.

If you are a leader, the people are your work.