DEEn Dictionary De - En
DeEs De - Es
DePt De - Pt
 Vocabulary trainer

Spec. subjects Grammar Abbreviations Random search Preferences
Search in Sprachauswahl
brooks
Search for:
Mini search box
 
Proverbs, aphorisms, quotations (English) by Linux fortune

Zero Mostel: That's it baby!  When you got it, flaunt it!  Flaunt it!
                -- Mel Brooks, "The Producers"
A little retrospection shows that although many fine, useful software systems
have been designed by committees and built as part of multipart projects,
those software systems that have excited passionate fans are those that are
the products of one or a few designing minds, great designers.  Consider Unix,
APL, Pascal, Modula, the Smalltalk interface, even Fortran; and contrast them
with Cobol, PL/I, Algol, MVS/370, and MS-DOS.
                -- Fred Brooks
Adding manpower to a late software project makes it later.
                -- F. Brooks, "The Mythical Man-Month"

Whenever one person is found adequate to the discharge of a duty by
close application thereto, it is worse execute by two persons and
scarcely done at all if three or more are employed therein.
                -- George Washington, 1732-1799
All programmers are optimists.  Perhaps this modern sorcery especially attracts
those who believe in happy endings and fairy godmothers.  Perhaps the hundreds
of nitty frustrations drive away all but those who habitually focus on the end
goal.  Perhaps it is merely that computers are young, programmers are younger,
and the young are always optimists.  But however the selection process works,
the result is indisputable:  "This time it will surely run," or "I just found
the last bug."
                -- Frederick Brooks, "The Mythical Man Month"
As the system comes up, the component builders will from time to time appear,
bearing hot new versions of their pieces -- faster, smaller, more complete,
or putatively less buggy.  The replacement of a working component by a new
version requires the same systematic testing procedure that adding a new
component does, although it should require less time, for more complete and
efficient test cases will usually be available.
                -- Frederick Brooks Jr., "The Mythical Man Month"
... computer hardware progress is so fast.  No other technology since
civilization began has seen six orders of magnitude in performance-price
gain in 30 years.
                -- Fred Brooks
Conceptual integrity in turn dictates that the design must proceed
from one mind, or from a very small number of agreeing resonant minds.
                -- Frederick Brooks Jr., "The Mythical Man Month"
Einstein argued that there must be simplified explanations of nature, because
God is not capricious or arbitrary.  No such faith comforts the software
engineer.
                -- Fred Brooks
It is a very humbling experience to make a multimillion-dollar mistake, but
it is also very memorable.  I vividly recall the night we decided how to
organize the actual writing of external specifications for OS/360.  The
manager of architecture, the manager of control program implementation, and
I were threshing out the plan, schedule, and division of responsibilities.
        The architecture manager had 10 good men.  He asserted that they
could write the specifications and do it right.  It would take ten months,
three more than the schedule allowed.
        The control program manager had 150 men.  He asserted that they
could prepare the specifications, with the architecture team coordinating;
it would be well-done and practical, and he could do it on schedule.
Furthermore, if the architecture team did it, his 150 men would sit twiddling
their thumbs for ten months.
        To this the architecture manager responded that if I gave the control
program team the responsibility, the result would not in fact be on time,
but would also be three months late, and of much lower quality.  I did, and
it was.  He was right on both counts.  Moreover, the lack of conceptual
integrity made the system far more costly to build and change, and I would
estimate that it added a year to debugging time.
                -- Frederick Brooks Jr., "The Mythical Man Month"
The flow chart is a most thoroughly oversold piece of program documentation.
                -- Frederick Brooks, "The Mythical Man Month"
The so-called "desktop metaphor" of today's workstations is instead an
"airplane-seat" metaphor.  Anyone who has shuffled a lap full of papers
while seated between two portly passengers will recognize the difference --
one can see only a very few things at once.
                -- Fred Brooks
... when fits of creativity run strong, more than one programmer or writer
has been known to abandon the desktop for the more spacious floor.
                -- Fred Brooks
In the pitiful, multipage, connection-boxed form to which the flowchart has
today been elaborated, it has proved to be useless as a design tool --
programmers draw flowcharts after, not before, writing the programs they
describe.
- Fred Brooks, Jr.
The so-called "desktop metaphor" of today's workstations is instead an
"airplane-seat" metaphor.  Anyone who has shuffled a lap full of papers while
seated between two portly passengers will recognize the difference -- one can
see only a very few things at once.
- Fred Brooks, Jr.
...when fits of creativity run strong, more than one programmer or writer has
been known to abandon the desktop for the more spacious floor.
- Fred Brooks, Jr.
A little retrospection shows that although many fine, useful software systems
have been designed by committees and built as part of multipart projects,
those software systems that have excited passionate fans are those that are
the products of one or a few designing minds, great designers.  Consider Unix,
APL, Pascal, Modula, the Smalltalk interface, even Fortran; and contrast them
with Cobol, PL/I, Algol, MVS/370, and MS-DOS.
- Fred Brooks, Jr.
...computer hardware progress is so fast.  No other technology since
civilization began has seen six orders of magnitude in performance-price
gain in 30 years.
- Fred Brooks, Jr.
Software entities are more complex for their size than perhaps any other human
construct because no two parts are alike.  If they are, we make the two
similar parts into a subroutine -- open or closed.  In this respect, software
systems differ profoundly from computers, buildings, or automobiles, where
repeated elements abound.
- Fred Brooks, Jr.
Digital computers are themselves more complex than most things people build:
They hyave very large numbers of states.  This makes conceiving, describing,
and testing them hard.  Software systems have orders-of-magnitude more states
than computers do.
- Fred Brooks, Jr.
The complexity of software is an essential property, not an accidental one.
Hence, descriptions of a software entity that abstract away its complexity
often abstract away its essence.
- Fred Brooks, Jr.
Einstein argued that there must be simplified explanations of nature, because
God is not capricious or arbitrary.  No such faith comforts the software
engineer.
- Fred Brooks, Jr.
As the system comes up, the component builders will from time to time appear,
bearing hot new versions of their pieces -- faster, smaller, more complete,
or putatively less buggy.  The replacement of a working component by a new
version requires the same systematic testing procedure that adding a new
component does, although it should require less time, for more complete and
efficient test cases will usually be available.
- Frederick Brooks Jr., "The Mythical Man Month"
Each team building another component has been using the most recent tested
version of the integrated system as a test bed for debugging its piece.  Their
work will be set back by having that test bed change under them.  Of course it
must.  But the changes need to be quantized.  Then each user has periods of
productive stability, interrupted by bursts of test-bed change.  This seems
to be much less disruptive than a constant rippling and trembling.
- Frederick Brooks Jr., "The Mythical Man Month"
Conceptual integrity in turn dictates that the design must proceed from one
mind, or from a very small number of agreeing resonant minds.
- Frederick Brooks Jr., "The Mythical Man Month"
It is a very humbling experience to make a multimillion-dollar mistake, but it
is also very memorable.  I vividly recall the night we decided how to organize
the actual writing of external specifications for OS/360.  The manager of
architecture, the manager of control program implementation, and I were
threshing out the plan, schedule, and division of responsibilities.

The architecture manager had 10 good men.  He asserted that they could write
the specifications and do it right.  It would take ten months, three more
than the schedule allowed.

The control program manager had 150 men.  He asserted that they could prepare
the specifications, with the architecture team coordinating; it would be
well-done and practical, and he could do it on schedule.  Futhermore, if
the architecture team did it, his 150 men would sit twiddling their thumbs
for ten months.

To this the architecture manager responded that if I gave the control program
team the responsibility, the result would not in fact be on time, but would
also be three months late, and of much lower quality.  I did, and it was.  He
was right on both counts.  Moreover, the lack of conceptual integrity made
the system far more costly to build and change, and I would estimate that it
added a year to debugging time.
- Frederick Brooks Jr., "The Mythical Man Month"
"Plan to throw one away.  You will anyway."
- Fred Brooks, "The Mythical Man Month"
"(The Chief Programmer) personally defines the functional and performance
specifications, designs the program, codes it, tests it, and writes its
documentation... He needs great talent, ten years experience and
considerable systems and applications knowledge, whether in applied
mathematics, business data handling, or whatever."
-- Fred P. Brooks, _The Mythical Man Month_
"More software projects have gone awry for lack of calendar time than for all
other causes combined."
-- Fred Brooks, Jr., _The Mythical Man Month_
Usually, when a lot of men get together, it's called a war.
                -- Mel Brooks, "The Listener"
The egg cream is psychologically the opposite of circumcision -- it
*pleasurably* reaffirms your Jewishness.
                -- Mel Brooks
        An architect's first work is apt to be spare and clean.  He knows
he doesn't know what he's doing, so he does it carefully and with great
restraint.
        As he designs the first work, frill after frill and embellishment
after embellishment occur to him.  These get stored away to be used "next
time." Sooner or later the first system is finished, and the architect,
with firm confidence and a demonstrated mastery of that class of systems,
is ready to build a second system.
        This second is the most dangerous system a man ever designs.
When he does his third and later ones, his prior experiences will
confirm each other as to the general characteristics of such systems,
and their differences will identify those parts of his experience that
are particular and not generalizable.
        The general tendency is to over-design the second system, using
all the ideas and frills that were cautiously sidetracked on the first
one.  The result, as Ovid says, is a "big pile."
                -- Frederick Brooks, "The Mythical Man Month"
Come live with me and be my love,
And we will some new pleasures prove
Of golden sands and crystal brooks
With silken lines, and silver hooks.
There's nothing that I wouldn't do
If you would be my POSSLQ.

You live with me, and I with you,
And you will be my POSSLQ.
I'll be your friend and so much more;
That's what a POSSLQ is for.

And everything we will confess;
Yes, even to the IRS.
Some day on what we both may earn,
Perhaps we'll file a joint return.
You'll share my pad, my taxes, joint;
You'll share my life - up to a point!
And that you'll be so glad to do,
Because you'll be my POSSLQ.
Come live with me, and be my love,
And we will some new pleasures prove
Of golden sands, and crystal brooks,
With silken lines, and silver hooks.
                -- John Donne
Fortune's Real-Life Courtroom Quote #3:

Q:  When he went, had you gone and had she, if she wanted to and were
    able, for the time being excluding all the restraints on her not to
    go, gone also, would he have brought you, meaning you and she, with
    him to the station?
MR. BROOKS:  Objection.  That question should be taken out and shot.
There is a good deal of solemn cant about the common interests of capital
and labour.  As matters stand, their only common interest is that of cutting
each other's throat.
                -- Brooks Atkinson, "Once Around the Sun"
No guarantee of accuracy or completeness!
©TU Chemnitz, 2006-2024
Your feedback:
Ad partners