Quotes About Development

el principio más importante del crecimiento empresarial: la regla de la luz verde: prevender, prevender, prevender.

just remember, darling, it is pain that changes our lives.

I just believe that the interesting time in a career is pre-success, what shaped things, how did you get to this point?

their way to becoming

The most challenging part of programming is conceptualizing the problem, and many errors in programming are conceptual errors. Because

Levels of Design Design is needed at several different levels of detail in a software system. Some design techniques apply at all levels, and some apply at only one or two. Figure 5-2 illustrates the levels. Figure 5-2. The levels of design in a program. The system (1) is first organized into subsystems (2). The subsystems are further divided into classes (3), and the classes are

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.

Object-Oriented Design Heuristics (1996), Arthur Riel

There is no code so big, twisted, or complex that maintenance can't make it worse.

The process is called estimation, not exactimation. —Phillip Armour

Programmers who program into a language first decide what thoughts they want to express, and then they determine how to express those thoughts using the tools provided by their specific language.

If you can't figure out how to use a class based solely on its interface documentation, the right response is not to pull up the source code and look at the implementation. That's good initiative but bad judgment. The right response is to contact the author of the class and say I can't figure out how to use this class.

By far the most common project risks in software development are poor requirements and poor project planning, thus preparation tends to focus on improving requirements and project plans.

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

The picture of the software designer deriving his design in a rational, error-free way from a statement of requirements is quite unrealistic. No system has ever been developed in that way, and probably none ever will. Even the small program developments shown in textbooks and papers are unreal. They have been revised and polished until the author has shown us what he wishes he had done, not what actually did happen. — David Parnas Paul Clements

In software, consultants sometimes tell you to buy into certain software-development methods to the exclusion of other methods. That's unfortunate because if you buy into any single methodology 100 percent, you'll see the whole world in terms of that methodology. In some instances, you'll miss opportunities to use other methods better suited to your current problem.

One of the main differences between programs you develop in school and those you develop as a professional is that the design problems solved by school programs are rarely, if ever, wicked.

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

Dijkstra pointed out that no one's skull is really big enough to contain a modern computer program (Dijkstra 1972), which means that we as software developers shouldn't try to cram whole programs into our skulls at once; we should try to organize our programs in such a way that we can safely focus on one part of it at a time.

Quicksort a few times, but what are the odds that your custom version will be fully correct on the first try?