Linux Computers

There are two ways of constructing a software design.  One way is to make
it so simple that there are obviously no deficiencies and the other is to
make it so complicated that there are no obvious deficiencies.
                -- C.A.R. Hoare

There are two ways to write error-free programs; only the third one works.

There has also been some work to allow the interesting use of macro names.
For example, if you wanted all of your "creat()" calls to include read
permissions for everyone, you could say

        #define creat(file, mode)      creat(file, mode | 0444)

        I would recommend against this kind of thing in general, since it
hides the changed semantics of "creat()" in a macro, potentially far away
from its uses.
        To allow this use of macros, the preprocessor uses a process that
is worth describing, if for no other reason than that we get to use one of
the more amusing terms introduced into the C lexicon.  While a macro is
being expanded, it is temporarily undefined, and any recurrence of the macro
name is "painted blue" -- I kid you not, this is the official terminology
-- so that in future scans of the text the macro will not be expanded
recursively.  (I do not know why the color blue was chosen; I'm sure it
was the result of a long debate, spread over several meetings.)
                -- From Ken Arnold's "C Advisor" column in Unix Review

There is is no reason for any individual to have a computer in their home.
                -- Ken Olsen (President of Digital Equipment Corporation),
                   Convention of the World Future Society, in Boston, 1977

There is no distinction between any AI program and some existent game.

        There once was a man who went to a computer trade show.  Each day as
he entered, the man told the guard at the door:
        "I am a great thief, renowned for my feats of shoplifting.  Be
forewarned, for this trade show shall not escape unplundered."
        This speech disturbed the guard greatly, because there were millions
of dollars of computer equipment inside, so he watched the man carefully.
But the man merely wandered from booth to booth, humming quietly to himself.
        When the man left, the guard took him aside and searched his clothes,
but nothing was to be found.
        On the next day of the trade show, the man returned and chided the
guard saying: "I escaped with a vast booty yesterday, but today will be even
better."  So the guard watched him ever more closely, but to no avail.
        On the final day of the trade show, the guard could restrain his
curiosity no longer. "Sir Thief," he said, "I am so perplexed, I cannot live
in peace.  Please enlighten me.  What is it that you are stealing?"
        The man smiled.  "I am stealing ideas," he said.
                -- Geoffrey James, "The Tao of Programming"

        There once was a master programmer who wrote unstructured programs.
A novice programmer, seeking to imitate him, also began to write unstructured
programs.  When the novice asked the master to evaluate his progress, the
master criticized him for writing unstructured programs, saying: "What is
appropriate for the master is not appropriate for the novice.  You must
understand the Tao before transcending structure."
                -- Geoffrey James, "The Tao of Programming"

        There was once a programmer who was attached to the court of the
warlord of Wu.  The warlord asked the programmer: "Which is easier to design:
an accounting package or an operating system?"
        "An operating system," replied the programmer.
        The warlord uttered an exclamation of disbelief.  "Surely an
accounting package is trivial next to the complexity of an operating
system," he said.
        "Not so," said the programmer, "when designing an accounting package,
the programmer operates as a mediator between people having different ideas:
how it must operate, how its reports must appear, and how it must conform to
the tax laws.  By contrast, an operating system is not limited my outside
appearances.  When designing an operating system, the programmer seeks the
simplest harmony between machine and ideas.  This is why an operating system
is easier to design."
        The warlord of Wu nodded and smiled.  "That is all good and well, but
which is easier to debug?"
        The programmer made no reply.
                -- Geoffrey James, "The Tao of Programming"

        There was once a programmer who worked upon microprocessors.  "Look at
how well off I am here," he said to a mainframe programmer who came to visit,
"I have my own operating system and file storage device.  I do not have to
share my resources with anyone.  The software is self-consistent and
easy-to-use.  Why do you not quit your present job and join me here?"
        The mainframe programmer then began to describe his system to his
friend, saying: "The mainframe sits like an ancient sage meditating in the
midst of the data center.  Its disk drives lie end-to-end like a great ocean
of machinery.  The software is a multi-faceted as a diamond and as convoluted
as a primeval jungle.  The programs, each unique, move through the system
like a swift-flowing river.  That is why I am happy where I am."
        The microcomputer programmer, upon hearing this, fell silent.  But the
two programmers remained friends until the end of their days.
                -- Geoffrey James, "The Tao of Programming"

There was, it appeared, a mysterious rite of initiation through which,
in one way or another, almost every member of the team passed.  The term
that the old hands used for this rite -- West invented the term, not the
practice -- was `signing up.'  By signing up for the project you agreed
to do whatever was necessary for success.  You agreed to forsake, if
necessary, family, hobbies, and friends -- if you had any of these left
(and you might not, if you had signed up too many times before).
                -- Tracy Kidder, "The Soul of a New Machine"