More often, then, we will be doing evaluation of programs not with respect to one another but with respect to a situation — a total situation — in wh… - Gerald M. Weinberg

"Denise: "So your present project is ready to pass to the testing people?" Ralph: "Absolutely." Denise: "Okay, since you're so sure it's adequately tested, I'm going to make you the following generous offer: If fewer than three bugs turn up in your component during testing, I will give you a raise. But if three or more bugs turn up during testing, you won't earn a raise this year." Ralph: "Um . . ." Denise: "Um what?" "Could I just have the component back for a few little tests I want to do?

In the seed model, Leadership is the process of creating an environment in which people become empowered.

Programs, like any other human-made objects, are designed — or should be designed — with a definite lifespan and scope of application in mind. Like the “Deacon’s Masterpiece,” which was “built in such a logical way it ran a hundred years to the day,” a program should have neither over-designed or under-designed parts. Yet it is an occupational disease of programmers to spend more time on those program parts that present, for some reason, the most intellectual challenge rather than on those that require the most work.