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

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

A language that doesn't affect the way you think about programming is
not worth knowing.
        A manager asked a programmer how long it would take him to finish the
program on which he was working.  "I will be finished tomorrow," the programmer
promptly replied.
        "I think you are being unrealistic," said the manager. "Truthfully,
how long will it take?"
        The programmer thought for a moment.  "I have some features that I wish
to add.  This will take at least two weeks," he finally said.
        "Even that is too much to expect," insisted the manager, "I will be
satisfied if you simply tell me when the program is complete."
        The programmer agreed to this.
        Several years later, the manager retired.  On the way to his
retirement lunch, he discovered the programmer asleep at his terminal.
He had been programming all night.
                -- Geoffrey James, "The Tao of Programming"
        A manager was about to be fired, but a programmer who worked for him
invented a new program that became popular and sold well.  As a result, the
manager retained his job.
        The manager tried to give the programmer a bonus, but the programmer
refused it, saying, "I wrote the program because I though it was an interesting
concept, and thus I expect no reward."
        The manager, upon hearing this, remarked, "This programmer, though he
holds a position of small esteem, understands well the proper duty of an
employee.  Lets promote him to the exalted position of management consultant!"
        But when told this, the programmer once more refused, saying, "I exist
so that I can program.  If I were promoted, I would do nothing but waste
everyone's time.  Can I go now?  I have a program that I'm working on."
                -- Geoffrey James, "The Tao of Programming"
        A manager went to his programmers and told them: "As regards to your
work hours: you are going to have to come in at nine in the morning and leave
at five in the afternoon."  At this, all of them became angry and several
resigned on the spot.
        So the manager said: "All right, in that case you may set your own
working hours, as long as you finish your projects on schedule."  The
programmers, now satisfied, began to come in a noon and work to the wee
hours of the morning.
                -- Geoffrey James, "The Tao of Programming"
        A manager went to the master programmer and showed him the requirements
document for a new application.  The manager asked the master: "How long will
it take to design this system if I assign five programmers to it?"
        "It will take one year," said the master promptly.
        "But we need this system immediately or even sooner!  How long will it
take it I assign ten programmers to it?"
        The master programmer frowned.  "In that case, it will take two years."
        "And what if I assign a hundred programmers to it?"
        The master programmer shrugged.  "Then the design will never be
completed," he said.
                -- Geoffrey James, "The Tao of Programming"
        A master programmer passed a novice programmer one day.  The master
noted the novice's preoccupation with a hand-held computer game.  "Excuse me",
he said, "may I examine it?"
        The novice bolted to attention and handed the device to the master.
"I see that the device claims to have three levels of play: Easy, Medium,
and Hard", said the master.  "Yet every such device has another level of play,
where the device seeks not to conquer the human, nor to be conquered by the
human."
        "Pray, great master," implored the novice, "how does one find this
mysterious setting?"
        The master dropped the device to the ground and crushed it under foot.
And suddenly the novice was enlightened.
                -- Geoffrey James, "The Tao of Programming"
        A master was explaining the nature of Tao to one of his novices.
"The Tao is embodied in all software -- regardless of how insignificant,"
said the master.
        "Is Tao in a hand-held calculator?" asked the novice.
        "It is," came the reply.
        "Is the Tao in a video game?" continued the novice.
        "It is even in a video game," said the master.
        "And is the Tao in the DOS for a personal computer?"
        The master coughed and shifted his position slightly.  "The lesson
is over for today," he said.
                -- Geoffrey James, "The Tao of Programming"
        *** A NEW KIND OF PROGRAMMING ***

Do you want the instant respect that comes from being able to use technical
terms that nobody understands?  Do you want to strike fear and loathing into
the hearts of DP managers everywhere?  If so, then let the Famous Programmers'
School lead you on... into the world of professional computer programming.
They say a good programmer can write 20 lines of effective program per day.
With our unique training course, we'll show you how to write 20 lines of code
and lots more besides.  Our training course covers every programming language
in existence, and some that aren't.  You'll learn why the on/off switch for a
computer is so important, what the words *fatal error* mean, and who and what
you should blame when you make a mistake.

        Yes, I want the brochure describing this incredible offer.
        I enclose $1000 is small unmarked bills to cover the cost of
        postage and handling. (No live poultry, please.)

*** Our Slogan:  Top down programming for the masses. ***
        A novice asked the Master: "Here is a programmer that never designs,
documents, or tests his programs.  Yet all who know him consider him one of
the best programmers in the world.  Why is this?"
        The Master replies: "That programmer has mastered the Tao.  He has
gone beyond the need for design; he does not become angry when the system
crashes, but accepts the universe without concern.  He has gone beyond the
need for documentation; he no longer cares if anyone else sees his code.  He
has gone beyond the need for testing; each of his programs are perfect within
themselves, serene and elegant, their purpose self-evident.  Truly, he has
entered the mystery of the Tao."
                -- Geoffrey James, "The Tao of Programming"
        A novice asked the master: "I have a program that sometimes runs and
sometimes aborts.  I have followed the rules of programming, yet I am totally
baffled. What is the reason for this?"
        The master replied: "You are confused because you do not understand
the Tao.  Only a fool expects rational behavior from his fellow humans.  Why
do you expect it from a machine that humans have constructed?  Computers
simulate determinism; only the Tao is perfect.
        The rules of programming are transitory; only the Tao is eternal.
Therefore you must contemplate the Tao before you receive enlightenment."
        "But how will I know when I have received enlightenment?" asked the
novice.
        "Your program will then run correctly," replied the master.
                -- Geoffrey James, "The Tao of Programming"
        A novice asked the master: "I perceive that one computer company is
much larger than all others.  It towers above its competition like a giant
among dwarfs.  Any one of its divisions could comprise an entire business.
Why is this so?"
        The master replied, "Why do you ask such foolish questions?  That
company is large because it is so large.  If it only made hardware, nobody
would buy it.  If it only maintained systems, people would treat it like a
servant.  But because it combines all of these things, people think it one
of the gods!  By not seeking to strive, it conquers without effort."
                -- Geoffrey James, "The Tao of Programming"
        A novice asked the master: "In the east there is a great tree-structure
that men call 'Corporate Headquarters'.  It is bloated out of shape with
vice-presidents and accountants.  It issues a multitude of memos, each saying
'Go, Hence!' or 'Go, Hither!' and nobody knows what is meant.  Every year new
names are put onto the branches, but all to no avail.  How can such an
unnatural entity exist?"
        The master replies: "You perceive this immense structure and are
disturbed that it has no rational purpose.  Can you not take amusement from
its endless gyrations?  Do you not enjoy the untroubled ease of programming
beneath its sheltering branches?  Why are you bothered by its uselessness?"
                -- Geoffrey James, "The Tao of Programming"
        A novice programmer was once assigned to code a simple financial
package.
        The novice worked furiously for many days, but when his master
reviewed his program, he discovered that it contained a screen editor, a set
of generalized graphics routines, and artificial intelligence interface,
but not the slightest mention of anything financial.
        When the master asked about this, the novice became indignant.
"Don't be so impatient," he said, "I'll put the financial stuff in eventually."
                -- Geoffrey James, "The Tao of Programming"
        A program should be light and agile, its subroutines connected like a
strings of pearls.  The spirit and intent of the program should be retained
throughout.  There should be neither too little nor too much, neither needless
loops nor useless variables, neither lack of structure nor overwhelming
rigidity.
        A program should follow the 'Law of Least Astonishment'.  What is this
law?  It is simply that the program should always respond to the user in the
way that astonishes him least.
        A program, no matter how complex, should act as a single unit.  The
program should be directed by the logic within rather than by outward
appearances.
        If the program fails in these requirements, it will be in a state of
disorder and confusion.  The only way to correct this is to rewrite the
program.
                -- Geoffrey James, "The Tao of Programming"
        A programmer from a very large computer company went to a software
conference and then returned to report to his manager, saying: "What sort
of programmers work for other companies?  They behaved badly and were
unconcerned with appearances. Their hair was long and unkempt and their
clothes were wrinkled and old. They crashed out hospitality suites and they
made rude noises during my presentation."
        The manager said: "I should have never sent you to the conference.
Those programmers live beyond the physical world.  They consider life absurd,
an accidental coincidence.  They come and go without knowing limitations.
Without a care, they live only for their programs.  Why should they bother
with social conventions?"
        "They are alive within the Tao."
                -- Geoffrey James, "The Tao of Programming"
A programming language is low level when its programs require attention
to the irrelevant.
A well-used door needs no oil on its hinges.
A swift-flowing steam does not grow stagnant.
Neither sound nor thoughts can travel through a vacuum.
Software rots if not used.

These are great mysteries.
                -- Geoffrey James, "The Tao of Programming"
Algol-60 surely must be regarded as the most important programming language
yet developed.
                -- T. Cheatham
... an anecdote from IBM's Yorktown Heights Research Center.  When a
programmer used his new computer terminal, all was fine when he was sitting
down, but he couldn't log in to the system when he was standing up.  That
behavior was 100 percent repeatable: he could always log in when sitting and
never when standing.

Most of us just sit back and marvel at such a story; how could that terminal
know whether the poor guy was sitting or standing?  Good debuggers, though,
know that there has to be a reason.  Electrical theories are the easiest to
hypothesize: was there a loose with under the carpet, or problems with static
electricity?  But electrical problems are rarely consistently reproducible.
An alert IBMer finally noticed that the problem was in the terminal's keyboard:
the tops of two keys were switched.  When the programmer was seated he was a
touch typist and the problem went unnoticed, but when he stood he was led
astray by hunting and pecking.
        -- "Programming Pearls" column, by Jon Bentley in CACM February 1985
Any programming language is at its best before it is implemented and used.
APL is a mistake, carried through to perfection.  It is the language of the
future for the programming techniques of the past: it creates a new generation
of coding bums.
                -- Edsger W. Dijkstra, SIGPLAN Notices, Volume 17, Number 5
APL is a natural extension of assembler language programming;
...and is best for educational purposes.
                -- A. Perlis
Around computers it is difficult to find the correct unit of time to
measure progress.  Some cathedrals took a century to complete.  Can you
imagine the grandeur and scope of a program that would take as long?
                -- Epigrams in Programming, ACM SIGPLAN Sept. 1982
As soon as we started programming, we found to our surprise that it wasn't
as easy to get programs right as we had thought.  Debugging had to be
discovered.  I can remember the exact instant when I realized that a large
part of my life from then on was going to be spent in finding mistakes in
my own programs.
                -- Maurice Wilkes, designer of EDSAC, on programming, 1949
BASIC is to computer programming as QWERTY is to typing.
                -- Seymour Papert
        *** DO YOU HAVE A RESTLESS URGE TO PROGRAM? ***
Do you want the instant respect that comes from being able to use technical
terms that nobody understands?  Do you want to strike fear and loathing into
the hearts of DP managers everywhere?  If so, then let the Famous Programmers'
School lead you on... into the world of professional computer programming.

        *** IS PROGRAMMING FOR YOU? ***
Programming is not for everyone.  But, if you have the desire to learn, we can
help you get started.  All you need is the Famous Programmers' Course and
enough money to keep those lessons coming month after month.

        *** TAKE OUR FREE APTITUDE TEST ***
To help determine if you are qualified to be a programmer, take a moment to
try this simple test:
        (1) Write down the numbers from zero to nine and the first six letters
                of the alphabet (Hint: 0123456789ABCDEF).
        (2) Whose picture is on the back of a twenty-dollar bill?
        (3) What is the state capital of Idaho?
If you managed to read all three questions without wondering why we asked
them, you may have a future as a computer programmer.
Do you suffer painful elimination?
                -- Don Knuth, "Structured Programming with Gotos"

Do you suffer painful recrimination?
                -- Nancy Boxer, "Structured Programming with Come-froms"

Do you suffer painful illumination?
                -- Isaac Newton, "Optics"

Do you suffer painful hallucination?
                -- Don Juan, cited by Carlos Casteneda
Documentation is the castor oil of programming.
Managers know it must be good because the programmers hate it so much.
Does a good farmer neglect a crop he has planted?
Does a good teacher overlook even the most humble student?
Does a good father allow a single child to starve?
Does a good programmer refuse to maintain his code?
                -- Geoffrey James, "The Tao of Programming"
Giving up on assembly language was the apple in our Garden of Eden:  Languages
whose use squanders machine cycles are sinful.  The LISP machine now permits
LISP programmers to abandon bra and fig-leaf.
                -- Epigrams in Programming, ACM SIGPLAN Sept. 1982
Grand Master Turing once dreamed that he was a machine.  When he awoke
he exclaimed:
        "I don't know whether I am Turing dreaming that I am a machine,
        or a machine dreaming that I am Turing!"
                -- Geoffrey James, "The Tao of Programming"
        Hardware met Software on the road to Changtse.  Software said: "You
are the Yin and I am the Yang.  If we travel together we will become famous
and earn vast sums of money."  And so the pair set forth together, thinking
to conquer the world.
        Presently, they met Firmware, who was dressed in tattered rags, and
hobbled along propped on a thorny stick.  Firmware said to them: "The Tao
lies beyond Yin and Yang.  It is silent and still as a pool of water.  It does
not seek fame, therefore nobody knows its presence.  It does not seeks fortune,
for it is complete within itself.  It exists beyond space and time."
        Software and Hardware, ashamed, returned to their homes.
                -- Geoffrey James, "The Tao of Programming"
If a 6600 used paper tape instead of core memory, it would use up tape
at about 30 miles/second.
                -- Grishman, Assembly Language Programming
If the designers of X-window built cars, there would be no fewer than five
steering wheels hidden about the cockpit, none of which followed the same
principles -- but you'd be able to shift gears with your car stereo.  Useful
feature, that.
                -- From the programming notebooks of a heretic, 1990.
        If the Tao is great, then the operating system is great.  If the
operating system is great, then the compiler is great.  If the compiler
is great, then the application is great.  If the application is great, then
the user is pleased and there is harmony in the world.
        The Tao gave birth to machine language.  Machine language gave birth
to the assembler.
        The assembler gave birth to the compiler.  Now there are ten thousand
languages.
        Each language has its purpose, however humble.  Each language
expresses the Yin and Yang of software.  Each language has its place within
the Tao.
        But do not program in COBOL if you can avoid it.
                -- Geoffrey James, "The Tao of Programming"
If you ever want to have a lot of fun, I recommend that you go off and program
an imbedded system.  The salient characteristic of an imbedded system is that
it cannot be allowed to get into a state from which only direct intervention
will suffice to remove it.  An imbedded system can't permanently trust anything
it hears from the outside world.  It must sniff around, adapt, consider, sniff
around, and adapt again.  I'm not talking about ordinary modular programming
carefulness here.  No.  Programming an imbedded system calls for undiluted
raging maniacal paranoia.  For example, our ethernet front ends need to know
what network number they are on so that they can address and route PUPs
properly.  How do you find out what your network number is?  Easy, you ask a
gateway.  Gateways are required by definition to know their correct network
numbers.  Once you've got your network number, you start using it and before
you can blink you've got it wired into fifteen different sockets spread all
over creation.  Now what happens when the panic-stricken operator realizes he
was running the wrong version of the gateway which was giving out the wrong
network number?  Never supposed to happen.  Tough.  Supposing that your
software discovers that the gateway is now giving out a different network
number than before, what's it supposed to do about it?  This is not discussed
in the protocol document.  Never supposed to happen.  Tough.  I think you
get my drift.
In a five year period we can get one superb programming language.  Only
we can't control when the five year period will begin.
In English, every word can be verbed.  Would that it were so in our
programming languages.
In seeking the unattainable, simplicity only gets in the way.
                -- Epigrams in Programming, ACM SIGPLAN Sept. 1982
        In the beginning was the Tao.  The Tao gave birth to Space and Time.
Therefore, Space and Time are the Yin and Yang of programming.

        Programmers that do not comprehend the Tao are always running out of
time and space for their programs.  Programmers that comprehend the Tao always
have enough time and space to accomplish their goals.
        How could it be otherwise?
                -- Geoffrey James, "The Tao of Programming"
        In the east there is a shark which is larger than all other fish.  It
changes into a bird whose winds are like clouds filling the sky.  When this
bird moves across the land, it brings a message from Corporate Headquarters.
This message it drops into the midst of the programmers, like a seagull
making its mark upon the beach.  Then the bird mounts on the wind and, with
the blue sky at its back, returns home.
        The novice programmer stares in wonder at the bird, for he understands
it not.  The average programmer dreads the coming of the bird, for he fears
its message.  The master programmer continues to work at his terminal, for he
does not know that the bird has come and gone.
                -- Geoffrey James, "The Tao of Programming"
It appears that PL/I (and its dialects) is, or will be, the most widely
used higher level language for systems programming.
                -- J. Sammet
It is practically impossible to teach good programming style to students
that have had prior exposure to BASIC: as potential programmers they are
mentally mutilated beyond hope of regeneration.
                -- Edsger W. Dijkstra, SIGPLAN Notices, Volume 17, Number 5
Let the machine do the dirty work.
                -- "Elements of Programming Style", Kernighan and Ritchie
Like punning, programming is a play on words.
Nearly every complex solution to a programming problem that I
have looked at carefully has turned out to be wrong.
                -- Brent Welch
        Now she speaks rapidly.  "Do you know *why* you want to program?"
        He shakes his head.  He hasn't the faintest idea.
        "For the sheer *joy* of programming!" she cries triumphantly.  
"The joy of the parent, the artist, the craftsman.  "You take a program,
born weak and impotent as a dimly-realized solution.  You nurture the
program and guide it down the right path, building, watching it grow ever
stronger.  Sometimes you paint with tiny strokes, a keystroke added here,
a keystroke changed there."  She sweeps her arm in a wide arc.  "And other
times you savage whole *blocks* of code, ripping out the program's very
*essence*, then beginning anew.  But always building, creating, filling the
program with your own personal stamp, your own quirks and nuances.  Watching
the program grow stronger, patching it when it crashes, until finally it can
stand alone -- proud, powerful, and perfect.  This is the programmer's finest
hour!"  Softly at first, then louder, he hears the strains of a Sousa march.
"This ... this is your canvas! your clay!  Go forth and create a masterwork!"
        One of the questions that comes up all the time is: How enthusiastic
is our support for UNIX?
        Unix was written on our machines and for our machines many years ago.
Today, much of UNIX being done is done on our machines. Ten percent of our
VAXs are going for UNIX use.  UNIX is a simple language, easy to understand,
easy to get started with. It's great for students, great for somewhat casual
users, and it's great for interchanging programs between different machines.
And so, because of its popularity in these markets, we support it.  We have
good UNIX on VAX and good UNIX on PDP-11s.
        It is our belief, however, that serious professional users will run
out of things they can do with UNIX. They'll want a real system and will end
up doing VMS when they get to be serious about programming.
        With UNIX, if you're looking for something, you can easily and quickly
check that small manual and find out that it's not there.  With VMS, no matter
what you look for -- it's literally a five-foot shelf of documentation -- if
you look long enough it's there.  That's the difference -- the beauty of UNIX
is it's simple; and the beauty of VMS is that it's all there.
                -- Ken Olsen, president of DEC, DECWORLD Vol. 8 No. 5, 1984
[It's been argued that the beauty of UNIX is the same as the beauty of Ken
Olsen's brain.  Ed.]
Over the shoulder supervision is more a need of the manager than the
programming task.
        Price Wang's programmer was coding software.  His fingers danced upon
the keyboard.  The program compiled without an error message, and the program
ran like a gentle wind.
        Excellent!" the Price exclaimed, "Your technique is faultless!"
        "Technique?" said the programmer, turning from his terminal, "What I
follow is the Tao -- beyond all technique.  When I first began to program I
would see before me the whole program in one mass.  After three years I no
longer saw this mass.  Instead, I used subroutines.  But now I see nothing.
My whole being exists in a formless void.  My senses are idle.  My spirit,
free to work without a plan, follows its own instinct.  In short, my program
writes itself.  True, sometimes there are difficult problems.  I see them
coming, I slow down, I watch silently.  Then I change a single line of code
and the difficulties vanish like puffs of idle smoke.  I then compile the
program.  I sit still and let the joy of the work fill my being.  I close my
eyes for a moment and then log off."
        Price Wang said, "Would that all of my programmers were as wise!"
                -- Geoffrey James, "The Tao of Programming"
Programming is an unnatural act.
Proposed Additions to the PDP-11 Instruction Set:

BBW        Branch Both Ways
BEW        Branch Either Way
BBBF        Branch on Bit Bucket Full
BH        Branch and Hang
BMR        Branch Multiple Registers
BOB        Branch On Bug
BPO        Branch on Power Off
BST        Backspace and Stretch Tape
CDS        Condense and Destroy System
CLBR        Clobber Register
CLBRI        Clobber Register Immediately
CM        Circulate Memory
CMFRM        Come From -- essential for truly structured programming
CPPR        Crumple Printer Paper and Rip
CRN        Convert to Roman Numerals
Real computer scientists don't write code.  They occasionally tinker with
`programming systems', but those are so high level that they hardly count
(and rarely count accurately; precision is for applications).
Real programmers disdain structured programming.  Structured programming is
for compulsive neurotics who were prematurely toilet- trained.  They wear
neckties and carefully line up pencils on otherwise clear desks.
Some programming languages manage to absorb change, but withstand progress.
                -- Epigrams in Programming, ACM SIGPLAN Sept. 1982
        Something mysterious is formed, born in the silent void.  Waiting
alone and unmoving, it is at once still and yet in constant motion.  It is
the source of all programs.  I do not know its name, so I will call it the
Tao of Programming.
        If the Tao is great, then the operating system is great.  If the
operating system is great, then the compiler is great.  If the compiler is
greater, then the applications is great.  The user is pleased and there is
harmony in the world.
        The Tao of Programming flows far away and returns on the wind of
morning.
                -- Geoffrey James, "The Tao of Programming"
        *** STUDENT SUCCESSES ***

Many of our students have gone on to achieve great success in all fields of
programming.  One former student developed the concept of the personalized
form letter.  Does the phrase, "Dear Mr.(insert name), You may already be a
winner!," sound familiar?  Another student writes "After only five lessons I
sold a "My Most Unforgettable Program" article to Corrosive Computing magazine.
Another of our graduates writes, "I recently completed a database-management
program for my department manager.  My program touched him so deeply that he
was speechless.  He told me later that he had never seen such a program in
his entire career.  Thank you, Famous Programmers' school; only you could
have made this possible."  Send for our introductory brochure which explains
in vague detail the operation of the Famous Programmers' School, and you'll
be eligible to win a possible chance to enter a drawing, the winner of which
can vie for a set of free steak knives.  If you don't do it now, you'll hate
yourself in the morning.
Syntactic sugar causes cancer of the semicolon.
                -- Epigrams in Programming, ACM SIGPLAN Sept. 1982
Systems have sub-systems and sub-systems have sub-systems and so on ad
infinitum -- which is why we're always starting over.
                -- Epigrams in Programming, ACM SIGPLAN Sept. 1982
The best book on programming for the layman is "Alice in Wonderland";
but that's because it's the best book on anything for the layman.
"The C Programming Language -- A language which combines the flexibility of
assembly language with the power of assembly language."
"The eleventh commandment was `Thou Shalt Compute' or `Thou Shalt Not
Compute' -- I forget which."
                -- Epigrams in Programming, ACM SIGPLAN Sept. 1982
The less time planning, the more time programming.
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #10: SIMPLE

SIMPLE is an acronym for Sheer Idiot's Monopurpose Programming Language
Environment.  This language, developed at the Hanover College for
Technological Misfits, was designed to make it impossible to write code
with errors in it.  The statements are, therefore, confined to BEGIN,
END and STOP.  No matter how you arrange the statements, you can't make
a syntax error.  Programs written in SIMPLE do nothing useful.  Thus
they achieve the results of programs written in other languages without
the tedious, frustrating process of testing and debugging.
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #12: LITHP

This otherwise unremarkable language is distinguished by the absence of
an "S" in its character set; users must substitute "TH".  LITHP is said
to be useful in protheththing lithtth.
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #13: SLOBOL

SLOBOL is best known for the speed, or lack of it, of its compiler.
Although many compilers allow you to take a coffee break while they
compile, SLOBOL compilers allow you to travel to Bolivia to pick the
coffee.  Forty-three programmers are known to have died of boredom
sitting at their terminals while waiting for a SLOBOL program to
compile.  Weary SLOBOL programmers often turn to a related (but
infinitely faster) language, COCAINE.
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #14 -- VALGOL

        VALGOL is enjoying a dramatic surge of popularity across the
industry.  VALGOL commands include REALLY, LIKE, WELL, and Y*KNOW.
Variables are assigned with the =LIKE and =TOTALLY operators.  Other
operators include the "California booleans", AX and NOWAY.  Loops are
accomplished with the FOR SURE construct.  A simple example:

        LIKE, Y*KNOW(I MEAN)START
        IF PIZZA        =LIKE BITCHEN AND
        GUY                =LIKE TUBULAR AND
        VALLEY GIRL        =LIKE GRODY**MAX(FERSURE)**2
        THEN
                FOR I =LIKE 1 TO OH*MAYBE 100
                        DO*WAH - (DITTY**2); BARF(I)=TOTALLY GROSS(OUT)
                SURE
        LIKE, BAG THIS PROGRAM; REALLY; LIKE TOTALLY(Y*KNOW); IM*SURE
        GOTO THE MALL

        VALGOL is also characterized by its unfriendly error messages.  For
example, when the user makes a syntax error, the interpreter displays the
message GAG ME WITH A SPOON!  A successful compile may be termed MAXIMALLY
AWESOME!
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #15 -- DOGO

        Developed at the Massachusetts Institute of Obedience Training, DOGO
DOGO heralds a new era of computer-literate pets.  DOGO commands include
SIT, STAY, HEEL, and ROLL OVER.  An innovative feature of DOGO is "puppy
graphics", a small cocker spaniel that occasionally leaves a deposit as
it travels across the screen.
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #16: C-

This language was named for the grade received by its creator when he
submitted it as a class project in a graduate programming class.  C- is best
described as a "low-level" programming language.  In fact, the language
generally requires more C- statements than machine-code statements to
execute a given task.  In this respect, it is very similar to COBOL.
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #17: SARTRE

Named after the late existential philosopher, SARTRE is an extremely
unstructured language.  Statements in SARTRE have no purpose; they just are.
Thus SARTRE programs are left to define their own functions. SARTRE
programmers tend to be boring and depressed, and are no fun at parties.
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #18: FIFTH

FIFTH is a precision mathematical language in which the data types
refer to quantity.  The data types range from CC, OUNCE, SHOT, and
JIGGER to FIFTH (hence the name of the language), LITER, MAGNUM and
BLOTTO.  Commands refer to ingredients such as CHABLIS, CHARDONNAY,
CABERNET, GIN, VERMOUTH, VODKA, SCOTCH, and WHATEVERSAROUND.

The many versions of the FIFTH language reflect the sophistication and
financial status of its users.  Commands in the ELITE dialect include
VSOP and LAFITE, while commands in the GUTTER dialect include HOOTCH
and RIPPLE. The latter is a favorite of frustrated FORTH programmers
who end up using this language.
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #2: RENE

Named after the famous French philosopher and mathematician Rene DesCartes,
RENE is a language used for artificial intelligence.  The language is being
developed at the Chicago Center of Machine Politics and Programming under a
grant from the Jane Byrne Victory Fund.  A spokesman described the language
as "Just as great as dis [sic] city of ours."

The center is very pleased with progress to date.  They say they have almost
succeeded in getting a VAX to think. However, sources inside the
organization say that each time the machine fails to think it ceases to exist.
        THE LESSER-KNOWN PROGRAMMING LANGUAGES #8: LAIDBACK

This language was developed at the Marin County Center for T'ai Chi,
Mellowness and Computer Programming (now defunct), as an alternative to
the more intense atmosphere in nearby Silicon Valley.

The center was ideal for programmers who liked to soak in hot tubs while
they worked.  Unfortunately few programmers could survive there because the
center outlawed Pizza and Coca-Cola in favor of Tofu and Perrier.

Many mourn the demise of LAIDBACK because of its reputation as a gentle and
non-threatening language since all error messages are in lower case.  For
example, LAIDBACK responded to syntax errors with the message:

        "i hate to bother you, but i just can't relate to that.  can
        you find the time to try it again?"
        The Magician of the Ivory Tower brought his latest invention for the
master programmer to examine.  The magician wheeled a large black box into the
master's office while the master waited in silence.
        "This is an integrated, distributed, general-purpose workstation,"
began the magician, "ergonomically designed with a proprietary operating
system, sixth generation languages, and multiple state of the art user
interfaces.  It took my assistants several hundred man years to construct.
Is it not amazing?"
        The master raised his eyebrows slightly. "It is indeed amazing," he
said.
        "Corporate Headquarters has commanded," continued the magician, "that
everyone use this workstation as a platform for new programs.  Do you agree
to this?"
        "Certainly," replied the master, "I will have it transported to the
data center immediately!"  And the magician returned to his tower, well
pleased.
        Several days later, a novice wandered into the office of the master
programmer and said, "I cannot find the listing for my new program.  Do
you know where it might be?"
        "Yes," replied the master, "the listings are stacked on the platform
in the data center."
                -- Geoffrey James, "The Tao of Programming"
        The master programmer moves from program to program without fear.  No
change in management can harm him.  He will not be fired, even if the project
is canceled. Why is this?  He is filled with the Tao.
                -- Geoffrey James, "The Tao of Programming"
        The programmers of old were mysterious and profound.  We cannot fathom
their thoughts, so all we do is describe their appearance.
        Aware, like a fox crossing the water.  Alert, like a general on the
battlefield.  Kind, like a hostess greeting her guests. Simple, like uncarved
blocks of wood.  Opaque, like black pools in darkened caves.
        Who can tell the secrets of their hearts and minds?
        The answer exists only in the Tao.
                -- Geoffrey James, "The Tao of Programming"
        The wise programmer is told about the Tao and follows it.  The average
programmer is told about the Tao and searches for it.  The foolish programmer
is told about the Tao and laughs at it.  If it were not for laughter, there
would be no Tao.
        The highest sounds are the hardest to hear.  Going forward is a way to
retreat.  Greater talent shows itself late in life.  Even a perfect program
still has bugs.
                -- Geoffrey James, "The Tao of Programming"
        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"
Thus spake the master programmer:
        "A well-written program is its own heaven; a poorly-written program
is its own hell."
                -- Geoffrey James, "The Tao of Programming"
Thus spake the master programmer:
        "After three days without programming, life becomes meaningless."
                -- Geoffrey James, "The Tao of Programming"
Thus spake the master programmer:
        "Let the programmers be many and the managers few -- then all will
        be productive."
                -- Geoffrey James, "The Tao of Programming"
Thus spake the master programmer:
        "Though a program be but three lines long, someday it will have to
        be maintained."
                -- Geoffrey James, "The Tao of Programming"
Thus spake the master programmer:
        "Time for you to leave."
                -- Geoffrey James, "The Tao of Programming"
Thus spake the master programmer:
        "When a program is being tested, it is too late to make design changes."
                -- Geoffrey James, "The Tao of Programming"
Thus spake the master programmer:
        "When you have learned to snatch the error code from
        the trap frame, it will be time for you to leave."
                -- Geoffrey James, "The Tao of Programming"
Thus spake the master programmer:
        "Without the wind, the grass does not move.  Without software,
        hardware is useless."
                -- Geoffrey James, "The Tao of Programming"
Thus spake the master programmer:
        "You can demonstrate a program for a corporate executive, but you
        can't make him computer literate."
                -- Geoffrey James, "The Tao of Programming"
"We are on the verge: Today our program proved Fermat's next-to-last theorem."
                -- Epigrams in Programming, ACM SIGPLAN Sept. 1982
        When managers hold endless meetings, the programmers write games.
When accountants talk of quarterly profits, the development budget is about
to be cut.  When senior scientists talk blue sky, the clouds are about to
roll in.
        Truly, this is not the Tao of Programming.
        When managers make commitments, game programs are ignored.  When
accountants make long-range plans, harmony and order are about to be restored.
When senior scientists address the problems at hand, the problems will soon
be solved.
        Truly, this is the Tao of Programming.
                -- Geoffrey James, "The Tao of Programming"
When someone says "I want a programming language in which I need only
say what I wish done," give him a lollipop.
When we understand knowledge-based systems, it will be as before --
except our fingertips will have been singed.
                -- Epigrams in Programming, ACM SIGPLAN Sept. 1982
Why are programmers non-productive?
Because their time is wasted in meetings.

Why are programmers rebellious?
Because the management interferes too much.

Why are the programmers resigning one by one?
Because they are burnt out.

Having worked for poor management, they no longer value their jobs.
                -- Geoffrey James, "The Tao of Programming"
Do not allow this language (Ada) in its present state to be used in
applications where reliability is critical, i.e., nuclear power stations,
cruise missiles, early warning systems, anti-ballistic missle defense
systems.  The next rocket to go astray as a result of a programming language
error may not be an exploratory space rocket on a harmless trip to Venus:
It may be a nuclear warhead exploding over one of our cities.  An unreliable
programming language generating unreliable programs constitutes a far
greater risk to our environment and to our society than unsafe cars, toxic
pesticides, or accidents at nuclear power stations.
- C. A. R. Hoare
The connection between the language in which we think/program and the problems
and solutions we can imagine is very close.  For this reason restricting
language features with the intent of eliminating programmer errors is at best
dangerous.
- Bjarne Stroustrup in "The C++ Programming Language"
The only way to learn a new programming language is by writing programs in it.
- Brian Kernighan
If it's working, the diagnostics say it's fine.
If it's not working, the diagnostics say it's fine.
- A proposed addition to rules for realtime programming
Weekends were made for programming.
- Karl Lehenbauer
The language provides a programmer with a set of conceptual tools; if these are
inadequate for the task, they will simply be ignored.  For example, seriously
restricting the concept of a pointer simply forces the programmer to use a
vector plus integer arithmetic to implement structures, pointer, etc.  Good
design and the absence of errors cannot be guaranteed by mere language
features.
-- Bjarne Stroustrup, "The C++ Programming Language"
A good USENET motto would be:
a. "Together, a strong community."
b. "Computers R Us."
c. "I'm sick of programming, I think I'll just screw around for a while on
     company time."
-- A Sane Man
Voodoo Programming:  Things programmers do that they know shouldn't work but
they try anyway, and which sometimes actually work, such as recompiling
everything.
-- Karl Lehenbauer
"When in doubt, print 'em out."
-- Karl's Programming Proverb 0x7
Fools ignore complexity.  Pragmatists suffer it.
Some can avoid it.  Geniuses remove it.
-- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept.  1982
    UNIX Shell is the Best Fourth Generation Programming Language

    It is the UNIX shell that makes it possible to do applications in a small
    fraction of the code and time it takes in third generation languages.  In
    the shell you process whole files at a time, instead of only a line at a
    time.  And, a line of code in the UNIX shell is one or more programs,
    which do more than pages of instructions in a 3GL.  Applications can be
    developed in hours and days, rather than months and years with traditional
    systems.  Most of the other 4GLs available today look more like COBOL or
    RPG, the most tedious of the third generation lanaguages.

"UNIX Relational Database Management:  Application Development in the UNIX
Environment" by Rod Manis, Evan Schaffer, and Robert Jorgensen.  Prentice
Hall Software Series.  Brian Kerrighan, Advisor.  1988.
"Life begins when you can spend your spare time programming instead of
watching television."
-- Cal Keegan
"Though a program be but three lines long,
someday it will have to be maintained."
-- The Tao of Programming
A Law of Computer Programming:
        Make it possible for programmers to write in English
        and you will find that programmers cannot write in English.
BASIC, n.:
        A programming language.  Related to certain social diseases in
        that those who have it will not admit it in polite company.
C, n:
        A programming language that is sort of like Pascal except more like
        assembly except that it isn't very much like either one, or anything
        else.  It is either the best language available to the art today, or
        it isn't.
                -- Ray Simard
Goto, n.:
        A programming tool that exists to allow structured programmers
        to complain about unstructured programmers.
                -- Ray Simard
Gray's Law of Programming:
        `_n+1' trivial tasks are expected to be accomplished in the same
        time as `_n' tasks.

Logg's Rebuttal to Gray's Law:
        `_n+1' trivial tasks take twice as long as `_n' trivial tasks.
Laws of Computer Programming:
        (1) Any given program, when running, is obsolete.
        (2) Any given program costs more and takes longer.
        (3) If a program is useful, it will have to be changed.
        (4) If a program is useless, it will have to be documented.
        (5) Any given program will expand to fill all available memory.
        (6) The value of a program is proportional the weight of its output.
        (7) Program complexity grows until it exceeds the capability of
                the programmer who must maintain it.
Pascal:
        A programming language named after a man who would turn over
        in his grave if he knew about it.
                -- Datamation, January 15, 1984
Programming Department:
        Mistakes made while you wait.
Real World, The, n.:
        1. In programming, those institutions at which programming may
be used in the same sentence as FORTRAN, COBOL, RPG, IBM, etc.  2. To
programmers, the location of non-programmers and activities not related
to programming.  3. A universe in which the standard dress is shirt and
tie and in which a person's working hours are defined as 9 to 5.  4.
The location of the status quo.  5. Anywhere outside a university.
"Poor fellow, he's left MIT and gone into the real world."  Used
pejoratively by those not in residence there.  In conversation, talking
of someone who has entered the real world is not unlike talking about a
deceased person.
Steinbach's Guideline for Systems Programming:
        Never test for an error condition you don't know how to handle.
"The major difference between a thing that might go wrong
and a thing that cannot possibly go wrong is that when a
thing that cannot possibly go wrong goes wrong it usually
turns out to be impossible to get at or repair."

- One of the laws of computers and programming revealed.
"The straightforward and easy path was to join the proprietary software world, signing nondisclosure agreements and promising not to help my fellow hacker....I could have made money this way, and perhaps had fun programming (if I closed my eyes to how I was treating other people).  But I knew that when my career was over, I would look back on years of building walls to divide people, and feel I had made the world ugly."

  -- Richard Stallman (Open Sources, 1999 O'Reilly and Associates)
"I am not convinced that they can write solid stable software. Proprietary software is already hobbled by it's secretive cathedral nature, but Microsoft seems to have a corner on incompetent programming as well."

  -- Chris DiBona from the introduction. (Open Sources, 1999 O'Reilly and Associates)
'Kitchen Sink' OS Announced

Coding has begun on a new operating system code named 'Kitchen Sink'. The new
OS will be based entirely on GNU Emacs. One programmer explained, "Since many
hackers spend a vast amount of their time in Emacs, why not just make it the
operating system?" When asked about the name, he responded, "Well, it has been
often said that Emacs has everything except a kitchen sink. Now it will."

One vi advocate said, "What the hell?!?! Those Emacs people are nuts. It seems
that even with a programming language, a web browser, and God only knows what
else built into their text editor, they're still not satisfied. Now they want
it to be an operating system. Hell, even Windows ain't that bloated!"
Could You Get Fired for Visiting Slashdot?

PADUCAH, KY -- Matt Johnson, an employee at Paradigm Shift Consulting, Inc.,
was fired from his programming job because of his addiction to Slashdot.
Johnson typically visited Slashdot several times a day during working hours.
Citing productivity problems, Johnson's boss gave him the pink slip and
instituted a 'NoDot' policy -- no visiting Slashdot or related sites from the
office, ever.  Now Johnson has filed a lawsuit, claiming that his Slashdot
addiction is protected by the Americans With Disabilities Act.

Matt Johnson explained, "They discriminated against me because I'm a Dothead.
Drug abuse and alcoholism are often considered handicaps.  Why not Slashdot
addiction?"  Johnson's boss sees the situation differently.   "Matt never got
any work done.  He was always visiting Slashdot, Freshmeat, or some other
nerd website.  And when he wasn't, he suffered withdrawl symptoms and
couldn't think straight.  A few months ago he spent eight consecutive hours
posting comments in a KDE vs. GNOME flame war.  I tried to offer assistance
to overcome his addiction, but he refused. Enough is enough."

The company's 'NoDot' policy has been under fire as well.  One anonymous
employee said, "We can't visit Slashdot because of Matt's addiction.  This
just sucks.  I really don't see anything wrong with visiting Slashdot during
breaks or after hours."
Programming for money sucks... you have to deal with PHBs, 16 hour days,
and spending the night in your cubicle half of the time to avoid the
Commute From Hell...

I minored in Journalism, so I tried to switch into a job as an IT pundit.
You'd think they'd welcome a geek like me with open arms, but they
didn't.  Ziff-Davis wouldn't even give me an interview. I was "too
qualified" they said. Apparently my technical acumen was too much for
their organization, which employs Jesse Berst and the ilk.

It gets worse. I tried to get an entry-level reporting job for a
local-yokel paper. After the interview they gave me a "skills test": I had
to compose an article using Microsoft Word 97. Since I've never touched a
Windows box, I had no clue how to use it. When I botched the test, the
personnel manager spouted, "Your resume said you were a computer
programmer. Obviously you're a liar. Get out of my office now!"

  -- Excerpt from a horror story about geek discrimination during
     the Geek Grok '99 telethon
OPPRESSED GEEK: Everybody keeps blaming me for the Y2K problem, the
Melissa Virus, Windows crashes... you name it. When somebody finds out
you're a bona fide geek, they start bugging you about computer problems. I
frequently hear things like, "Why can't you geeks make Windows work
right?", "What kind of idiot writes a program that can't handle the year
2000?", "Geeks are evil, all they do is write viruses", and "The Internet
is the spawn of Satan".

I'm afraid to admit I have extensive computing experience. When somebody
asks what kind of job I have, I always lie. From my experience, admitting
that you're a geek is an invitation to disaster.

LARRY WALL: I know, I know. I sometimes say that I'm the founder of a
pearl harvesting company instead of admitting that I'm the founder of the
Perl programming language.

ERIC S. RAYMOND: This is tragic. We can't live in a world like this. We
need your donations to fight social oppression and ignorance against
geekdom...

   -- Excerpt from the Geek Grok '99 telethon      
Brief History Of Linux (#20)
Linux is born

Linus' superhuman programming talent produced, within a year, a full
operating system that rivaled Minix. The first official announcement on
comp.os.minix came October 5th, in which Linus wrote these famous words:

   Do you pine for the nice days of minix-1.1, when men were men and wrote
   their own device drivers? Do you want to cut your teeth on an operating
   system that will achieve world domination within 15 years? Want to get
   rich quick by the end of the century by taking money from hordes of
   venture capitalists and clueless Wall Street suits? Need to get even
   with Bill Gates but don't know what to do except throw cream pies at
   him? Then this post might just be for you :-)

Linux (which was known as "Lindows", "Freax", and "Billsux" for short
periods in 1991) hit the bigtime on January 5, 1992 (exactly one year
after Linus wasn't hit by a bus) when version 0.12 was released under the
GNU GPL. Linus called his creation a "better Minix than Minix"; the famous
Linus vs. Tanenbaum flamewar erupted soon thereafter on January 29th and
injured several Usenet bystanders.
Are you sick of wasting valuable seconds while ingesting caffeine or
eating a cold pizza? Is your programming project running behind because
you keep falling asleep? EyeOpener(tm) brand caffeinated beverages has the
solution. Our new ActiveIV product will provide a 24 hour supply of
caffeine via intravenous tube while you work -- so you can hack without
any interruptions at all (except going to the bathroom -- but our
Port-a-Urinal(tm) can help solve that problem as well).

EyeOpener(tm) beverages contain at least 5,000% of the daily recommended
dose of caffeine, a quantity that will surely keep you wide awake, alert,
and in Deep Hack Mode for weeks at a time. With EyeOpener and ActiveIV,
you won't waste your valuable time at a vendine machine.

EyeOpener(tm): You'll Never Waste Another Millisecond Ever Again.
UNobfuscated Perl Code Contest

The Perl Gazette has announced the winners in the First Annual Unobfuscated
Perl Code Contest. First place went to Edwin Fuller, who submitted this
unobfuscated program:

  #!/usr/bin/perl
  print "Hello world!\n";

"This was definitely a challenging contest," said an ecstatic Edwin
Fuller. "I've never written a Perl program before that didn't have
hundreds of qw( $ @ % & * | ? / \ ! # ~ ) symbols. I really had to summon
all of my programming skills to produce an unobfuscated program."

...The second place winner, Mrs. Sea Pearl, submitted the following code:

  #!/usr/bin/perl
  use strict;
  # Do nothing, successfully
  exit(0);
It BASICally Sucks

Older versions of MS-DOS came with bundled programming languages including
GW-BASIC and QBasic. Windows XP continues the Microsoft tradition of
ruining budding programmers with horrible programming tools by including
XPBasic, an interpreted language in which all of the customary BASIC
keywords have been replaced with advertising slogans.

Nike has paid a handsome amount to Microsoft for "keyword rights". Instead
of saying PRINT "HELLO WORLD", XPBasic programmers must now type JUST DO
IT "HELLO WORLD". Other common XPBasic statements include WHERE DO YOU
WANT TO GOTO 20 TODAY? and DIM ARRAY(1 TO 20) AS INTEGER BROUGHT TO YOU BY
VERIZON WIRELESS.

  -- from Humorix's review of Windows XP (eXceptionally Pathetic)
Severe Acronym Shortage Cripples Computer Industry

SILICON VALLEY, CALIFORNIA (SVC) -- According to a recent study by the
Blartner Group, 99.5% of all possible five letter combinations have
already been appropriated for computer industry acronyms. The impending
shortage of 5LC's is casting a dark shadow over the industry, which relies
heavily on short, easy-to-remember acronyms for everything.

"Acronym namespace collisions (ANCs) are increasing at a fantastic rate
and threaten the very fabric of the computing world," explained one ZD
pundit. "For example, when somebody talks about XP, I don't know whether
they mean eXtreme Programming or Microsoft's eXceptionally Pathetic
operating system. We need to find a solution now or chaos will result."

Leaders of several SVC companies have floated the idea of an
"industry-wide acronym conservation protocol" (IWACP -- one of the few
5LCs not already appropriated). Explained Bob Smith, CTO of IBM, "If
companies would voluntarily limit the creation of new acronyms while
recycling outdated names, we could reduce much of the pollution within the
acronym namespace ourselves. The last thing we want is for Congress to get
involved and try to impose a solution for this SAS (Severe Acronym
Shortage) that would likely only create many new acronyms in the process."
"I would suggest you to read through the following book and files:
        * Kernighan & Pike, "The Practice of Programming"
        * Documentation/CodingStyle
        * drivers/net/aironet4500_proc.c
and consider, erm, discrepancies. On the second thought, reading K&R
might also be useful. IOW, no offense, but your C is bad beyond belief."

         - Al Viro
"I hold open source people to higher standards. They are supposed to be
the people who do programming because it's an art-form, not because it's
their job."

         - Linus Torvalds
You know, if you really do not understand the implications of
running everything with permissions equivalent to root - get
the hell out of any UNIX-related programming until you learn.

        - Al Viro explaining the merits of doing everything as root
Step #1 in programming: understand people.

        - Linus Torvalds on linux-kernel
As I'm sure you're all aware, being experts in userland programming, that  
the above obviously cannot work and is totally bogus.

        - Russell King on linux-kernel
Microsoft is a cross between the Borg and the Ferengi.  Unfortunately,
they use Borg to do their marketing and Ferengi to do their
programming.
        -- Simon Slavin
Excusing bad programming is a shooting offence, no matter _what_ the
circumstances.
        -- Linus Torvalds, to the linux-kernel list
Column 1                Column 2                Column 3

0. integrated                0. management                0. options
1. total                1. organizational        1. flexibility
2. systematized                2. monitored                2. capability
3. parallel                3. reciprocal                3. mobility
4. functional                4. digital                4. programming
5. responsive                5. logistical                5. concept
6. optional                6. transitional                6. time-phase
7. synchronized                7. incremental                7. projection
8. compatible                8. third-generation        8. hardware
9. balanced                9. policy                9. contingency

        The procedure is simple.  Think of any three-digit number, then select
the corresponding buzzword from each column.  For instance, number 257 produces
"systematized logistical projection," a phrase that can be dropped into
virtually any report with that ring of decisive, knowledgeable authority.  "No
one will have the remotest idea of what you're talking about," says Broughton,
"but the important thing is that they're not about to admit it."
                -- Philip Broughton, "How to Win at Wordsmanship"
[End of diatribe.  We now return you to your regularly scheduled
programming...]
             -- Larry Wall in Configure from the perl distribution
Perl programming is an *empirical* science!
             -- Larry Wall in <10226@jpl-devvax.JPL.NASA.GOV>
I knew I'd hate COBOL the moment I saw they'd used "perform" instead of
"do".
             -- Larry Wall on a not-so-popular programming language
Don't worry, nobody really LISTENS to lectures in MOSCOW, either! ...
FRENCH, HISTORY, ADVANCED CALCULUS, COMPUTER PROGRAMMING, BLACK
STUDIES, SOCIOBIOLOGY! ...  Are there any QUESTIONS??
No guarantee of accuracy or completeness!
©TU Chemnitz, 2006-2024
Your feedback:
Ad partners