Richard P. Gabriel > Quotes

“Programmers are not mathematicians, no matter how much we wish and wish for it.”
― Richard P. Gabriel

“It is only when we forget the ideas behind building something wonderful that we can actually do the building that makes things wonderful.”
― Richard P. Gabriel

“reuse is properly a process issue, and individual organizations need to decide whether they believe in its long-term benefits.”
― Richard P. Gabriel, Patterns of Software: Tales from the Software Community

“The problem with traditional approaches to abstraction and encapsulation is that they aim at complete information hiding. This characteristic anticipates being able to eliminate programming from parts of the software development process, those parts contained within module boundaries. As we've seen, though, the need to program is never eliminated because customization, modification, and maintenance are always required-that is, piecemeal growth.”
― Richard P. Gabriel, Patterns of Software: Tales from the Software Community

“reuse is easiest within a project instead of between them. A manager's success depends on performance on a given project and not on performance over several projects. And preparing code for reuse requires additional work, not only by the reuse expert but also by developers. Therefore, preparing for reuse has a cost for any given project.”
― Richard P. Gabriel, Patterns of Software: Tales from the Software Community

“Habitability is the characteristic of source code that enables programmers, coders, bug-fixers, and people coming to the code later in its life to understand its construction and intentions and to change it comfortably and confidently.”
― Richard P. Gabriel, Patterns of Software: Tales from the Software Community

“One of the primary reasons that abstraction is overloved is that a completed program full of the right abstractions is perfectly beautiful. But there are very few completed programs, because programs are written, maintained, bugs are fixed, features are added, performance is tuned, and a whole variety of changes are made both by the original and new programming team members. Thus, the way a program looks in the end is not important because there is rarely an end, and if there is one it isn't planned.”
― Richard P. Gabriel, Patterns of Software: Tales from the Software Community

“The lesson to be learned from this is that it is often undesirable to go for the right thing first. It is better to get half of the right thing available so that it spreads like a virus. Once people are hooked on it, take the time to improve it to 90% of the right thing.”
― Richard P. Gabriel