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

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

A LISP programmer knows the value of everything, but the cost of nothing.
                -- Alan Perlis
        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 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 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 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 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 programmer is a person who passes as an exacting expert on the basis of
being able to turn out, after innumerable punching, an infinite series of
incomprehensible answers calculated with micrometric precisions from vague
assumptions based on debatable figures taken from inconclusive documents
and carried out on instruments of problematical accuracy by persons of
dubious reliability and questionable mentality for the avowed purpose of
annoying and confounding a hopelessly defenseless department that was
unfortunate enough to ask for the information in the first place.
                -- IEEE Grid newsmagazine
===  ALL USERS PLEASE NOTE  ========================

Compiler optimizations have been made to macro expand LET into a WITHOUT-
INTERRUPTS special form so that it can PUSH things into a stack in the
LET-OPTIMIZATION area, SETQ the variables and then POP them back when it's
done.  Don't worry about this unless you use multiprocessing.
Note that LET *could* have been defined by:

        (LET ((LET '`(LET ((LET ',LET))
                        ,LET)))
        `(LET ((LET ',LET))
                ,LET))

This is believed to speed up execution by as much as a factor of 1.01 or
3.50 depending on whether you believe our friendly marketing representatives.
This code was written by a new programmer here (we snatched him away from
Itty Bitti Machines where he was writing COUGHBOL code) so to give him
confidence we trusted his vows of "it works pretty well" and installed it.
... 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
        *** 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.
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"
Fellow programmer, greetings!  You are reading a letter which will bring
you luck and good fortune.  Just mail (or UUCP) ten copies of this letter
to ten of your friends.  Before you make the copies, send a chip or
other bit of hardware, and 100 lines of 'C' code to the first person on the
list given at the bottom of this letter.  Then delete their name and add
yours to the bottom of the list.

Don't break the chain!  Make the copy within 48 hours.  Gerald R. of San
Diego failed to send out his ten copies and woke the next morning to find
his job description changed to "COBOL programmer."  Fred A. of New York sent
out his ten copies and within a month had enough hardware and software to
build a Cray dedicated to playing Zork.  Martha H. of Chicago laughed at
this letter and broke the chain.  Shortly thereafter, a fire broke out in
her terminal and she now spends her days writing documentation for IBM PC's.

Don't break the chain!  Send out your ten copies today!
For example, if \thinmskip = 3mu, this makes \thickmskip = 6mu.  But if
you also want to use \skip12 for horizontal glue, whether in math mode or
not, the amount of skipping will be in points (e.g., 6pt).  The rule is
that glue in math mode varies with the size only when it is an \mskip;
when moving between an mskip and ordinary skip, the conversion factor
1mu=1pt is always used.  The meaning of '\mskip\skip12' and
'\baselineskip=\the\thickmskip' should be clear.
                -- Donald Knuth, TeX 82 -- Comparison with TeX80
        I'm sure that VMS is completely documented, I just haven't found the
right manual yet.  I've been working my way through the manuals in the document
library and I'm half way through the second cabinet, (3 shelves to go), so I
should find what I'm looking for by mid May.  I hope I can remember what it
was by the time I find it.
        I had this idea for a new horror film, "VMS Manuals from Hell" or maybe
"The Paper Chase : IBM vs. DEC".  It's based on Hitchcock's "The Birds", except
that it's centered around a programmer who is attacked by a swarm of binder
pages with an index number and the single line "This page intentionally left
blank."
                -- Alex Crain
If at first you don't succeed, you must be a programmer.
If God had a beard, he'd be a UNIX programmer.
If Machiavelli were a programmer, he'd have worked for AT&T.
        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"
        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!"
Our documentation manager was showing her 2 year old son around the office.
He was introduced to me, at which time he pointed out that we were both
holding bags of popcorn.  We were both holding bottles of juice.  But only
*__he* had a lollipop.
        He asked his mother, "Why doesn't HE have a lollipop?"
        Her reply: "He can have a lollipop any time he wants to.  That's
what it means to be a programmer."
        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"
Proposed Additions to the PDP-11 Instruction Set:

DC        Divide and Conquer
DMPK        Destroy Memory Protect Key
DO        Divide and Overflow
EMPC        Emulate Pocket Calculator
EPI        Execute Programmer Immediately
EROS        Erase Read Only Storage
EXCE        Execute Customer Engineer
HCF        Halt and Catch Fire
IBP        Insert Bug and Proceed
INSQSW        Insert into queue somewhere (for FINO queues [First in never out])
PBC        Print and Break Chain
PDSK        Punch Disk
Seems a computer engineer, a systems analyst, and a programmer were
driving down a mountain when the brakes gave out.  They screamed down the
mountain, gaining speed, but finally managed to grind to a halt, more by
luck than anything else, just inches from a thousand foot drop to jagged
rocks.  They all got out of the car:
        The computer engineer said, "I think I can fix it."
        The systems analyst said, "No, no, I think we should take it
into town and have a specialist look at it."
        The programmer said, "OK, but first I think we should get back
in and see if it does it again."
The Analytical Engine weaves Algebraical patterns just as the Jacquard
loom weaves flowers and leaves.
                -- Ada Augusta, Countess of Lovelace, the first programmer
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
The day-to-day travails of the IBM programmer are so amusing to most of
us who are fortunate enough never to have been one -- like watching
Charlie Chaplin trying to cook a shoe.
        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 number of UNIX installations has grown to 10, with more expected.
        -- The Unix Programmer's Manual, 2nd Edition, June 1972
        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 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"
To the systems programmer, users and applications serve only to provide a
test load.
Wasn't there something about a PASCAL programmer knowing the value of
everything and the Wirth of nothing?
        "Well," said Programmer, "the customary procedure in such cases is
as follows."
        "What does Crustimoney Proseedcake mean?" said End-user.  "For I am
an End-user of Very Little Brain, and long words bother me."
        "It means the Thing to Do."
        "As long as it means that, I don't mind," said End-user humbly.

        [with apologies to A.A. Milne]
... 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
You can measure a programmer's perspective by noting his attitude on
the continuing viability of FORTRAN.
                -- Alan Perlis
...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.
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 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"
"An ounce of prevention is worth a ton of code."
-- an anonymous programmer
"The number of Unix installations has grown to 10, with more expected."
-- The Unix Programmer's Manual, 2nd Edition, June, 1972
"The computer programmer is a creator of universes for which he alone
is responsible. Universes of virtually unlimited complexity can be
created in the form of computer programs."
-- Joseph Weizenbaum, _Computer Power and Human Reason_
"(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_
To the systems programmer, users and applications serve only to provide a
test load.
Bug, n.:
        An aspect of a computer program which exists because the
        programmer was thinking about Jumbo Jacks or stock options when s/he
        wrote the program.

Fortunately, the second-to-last bug has just been fixed.
                -- Ray Simard
comment:
        A superfluous element of a source program included so the
        programmer can remember what the hell it was he was doing
        six months later.  Only the weak-minded need them, according
        to those who think they aren't.
flowchart, n. & v.:
        [From flow "to ripple down in rich profusion, as hair" + chart
"a cryptic hidden-treasure map designed to mislead the uninitiated."]
1. n. The solution, if any, to a class of Mascheroni construction
problems in which given algorithms require geometrical representation
using only the 35 basic ideograms of the ANSI template.  2. n. Neronic
doodling while the system burns.  3. n. A low-cost substitute for
wallpaper.  4. n.  The innumerate misleading the illiterate.  "A
thousand pictures is worth ten lines of code." -- The Programmer's
Little Red Vade Mecum, Mao Tse T'umps.  5. v.intrans. To produce
flowcharts with no particular object in mind.  6. v.trans. To obfuscate
(a problem) with esoteric cartoons.
                -- Stan Kelly-Bootle, "The Devil's DP Dictionary"
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.
User n.:
        A programmer who will believe anything you tell him.
Q:        Why did the programmer call his mother long distance?
A:        Because that was her name.
"I thought that you said you were 20 years old!"
"As a programmer, yes," she replied,
"And you claimed to be very near two meters tall!"
"You said you were blonde, but you lied!"
Oh, she was a hacker and he was one, too,
They had so much in common, you'd say.
They exchanged jokes and poems, and clever new hacks,
And prompts that were cute or risque'.
He sent her a picture of his brother Sam,
She sent one from some past high school day,
And it might have gone on for the rest of their lives,
If they hadn't met in L.A.
"Your beard is an armpit," she said in disgust.
He answered, "Your armpit's a beard!"
And they chorused: "I think I could stand all the rest
If you were not so totally weird!"
If she had not said what he wanted to hear,
And he had not done just the same,
They'd have been far more honest, and never have met,
And would not have had fun with the game.
                -- Judith Schrier, "Face to Face After Six Months of
                Electronic Mail"
"No program is perfect,"
They said with a shrug.
"The customer's happy--
What's one little bug?"

But he was determined,                        Then change two, then three more,
The others went home.                        As year followed year.
He dug out the flow chart                And strangers would comment,
Deserted, alone.                        "Is that guy still here?"

Night passed into morning.                He died at the console
The room was cluttered                        Of hunger and thirst
With core dumps, source listings.        Next day he was buried
"I'm close," he muttered.                Face down, nine edge first.

Chain smoking, cold coffee,                And his wife through her tears
Logic, deduction.                        Accepted his fate.
"I've got it!" he cried,                Said "He's not really gone,
"Just change one instruction."                He's just working late."
                -- The Perfect Programmer
Oh, I am a C programmer and I'm okay
        I muck with indices and structs all day
And when it works, I shout hoo-ray
        Oh, I am a C programmer and I'm okay
'Tis the dream of each programmer,
Before his life is done,
To write three lines of APL,
And make the damn things run.
'Twas the night before crisis, and all through the house,
        Not a program was working not even a browse.
The programmers were wrung out too mindless to care,
        Knowing chances of cutover hadn't a prayer.
The users were nestled all snug in their beds,
        While visions of inquiries danced in their heads.
When out in the lobby there arose such a clatter,
        I sprang from my tube to see what was the matter.
And what to my wondering eyes should appear,
        But a Super Programmer, oblivious to fear.
More rapid than eagles, his programs they came,
        And he whistled and shouted and called them by name;
On Update!  On Add!  On Inquiry!  On Delete!
        On Batch Jobs!  On Closing!  On Functions Complete!
His eyes were glazed over, his fingers were lean,
        From Weekends and nights in front of a screen.
A wink of his eye, and a twist of his head,
        Soon gave me to know I had nothing to dread...
                -- "Twas the Night before Crisis"
I'm not a programmer, but I play one at Microsoft.

   -- From a Slashdot.org post
'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!"
Mad Programmer Commits Suicide

KENNETT, MO -- For two years Doug Carter toiled away in his basement computer
lab working on his own 'Dougnix' operating system. Apparently he was sick of
Windows 95 so he decided to create his own OS, based loosely on Unix. He had
developed his own 'DougUI' window manager, Doug++ compiler, DougFS filesystem,
and other integrated tools.

All was going well until last week when he hooked his computer up to the
Internet for the first time. It was then that he stumbled on to www.linux.org.
Reports are sketchy about what happened next. We do know he committed suicide
days after, leaving behind a rambling suicide note. Part of the note says:

"I've wasted the past two years of my life... Wasted... Gone... Forever...
Never return to. [illegible] Why did I bother creating my own OS... when Linux
is exactly what I needed!?!?!?! If I had only known about Linux! Why someone
didn't tell me? [illegible] Wasted! Aggghhh!" [The rest of the note is filled
with incomprehensible assembly language ramblings.]
Microsoft Mandatory Survey (#18)

Customers who want to upgrade to Windows 98 Second Edition must now fill
out a Microsoft survey online before they can order the bugfix/upgrade.

Question 18: Witnessing the popularity of "Dilbert", Microsoft has plans
     to launch a syndicated comic strip featuring life at Microsoft. What
     characters would you like to see in such a comic strip?

A. Judge Jackson, the goofy court judge who is always making foolish (and
   funny) decisions

B. Bob, a wacky Microsoft programmer who likes to insert easter eggs in
   his work, and who is addicted to playing "Age of Empires"

C. Bill Gates, the intelligent nerd extraordinaire who always gets his way
   by simply giving people large sums of money

D. Ed Muth, the Microsoft spokesman who keeps putting his foot in his
   mouth. When not in public, he's a surprisingly sexy "chic magnet"

E. Poorard Stalinman, the leader of a movement of hackers to provide
   "free" software for the masses at the expense of Capitalistic values
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
Right now hundreds of Anonymous Cowards are cheering the fact that only
Windows boobs are victims of ILOVEYOU and other email viruses. I realize
Outlook is so insecure that using it is like posting a sign outside your
door saying, "DOOR UNLOCKED -- ROB ME!". However, Linux isn't immune. If I
had a dollar for every pine buffer overflow uncovered, I could buy a
truckload of fresh herring.

I expect the next mass email virus to spread will be cross-platform. If
the recipient is a Windows/Outlook luser, they'll get hit. If the
recipient is a Linux/pine user, they'll find themselves staring at a
self-executing bash script that's has just allocated 1 petabyte of memory
and crashed the system (or worse).

Either that or the next mass email virus will only damage Linux systems. I
can just see Bill Gates assigning some junior programmer that very task.
Be afraid. Be very afraid.

   -- A speech given at the First Annual Connecticut Conspiracy]
      Convention (ConConCon) by an anonymous creature said to
      be "wearing what appeared to be a tuxedo".
Brief History Of Linux (#17)
Terrible calamity

IBM chose Microsoft's Quick & Dirty Operating System instead of CP/M for
its new line of PCs. QDOS (along with the abomination known as EDLIN) had
been acquired from a Seattle man, Tim Paterson, for the paltry sum of
$50,000. "Quick" and "Dirty" were truly an accurate description of this
system, because IBM's quality assurance department discovered 300 bugs in
QDOS's 8,000 lines of assember code (that's about 1 bug per 27 lines --
which, at the time, was appalling, but compared with Windows 98 today, it
really wasn't that shabby).

Thanks in part to IBM's new marketing slogan, "Nobody Ever Got Fired For
Choosing IBM(tm)", and the release of the VisiCalc spreadsheet program
that everybody and their brother wanted, IBM PCs running DOS flew off the
shelves and, unfortunately, secured Microsoft's runaway success. Bill
Gates was now on his way to the Billionaire's Club; his days as a mediocre
programmer were long gone: he was now a Suit. The only lines of code he
would ever see would be the passcodes to his Swiss bank accounts.
Unobfuscated Perl (#1)

A rogue group of Perl hackers has presented a plan to add a "use
really_goddamn_strict" pragma that would enforce readability and
UNobfuscation. With this pragma in force, the Perl compiler might say:

* Warning: Program contains zero comments. You've probably never seen or
  used one before; they begin with a # symbol. Please start using them or
  else a representative from the nearest Perl Mongers group will come to
  your house and beat you over the head with a cluestick.

* Warning: Program uses a cute trick at line 125 that might make sense in
  C. But this isn't C!

* Warning: Code at line 412 indicates that programmer is an idiot. Please
  correct error between chair and monitor.

* Warning: While There's More Than One Way To Do It, your method at line
  523 is particularly stupid. Please try again.
Unobfuscated Perl (#2)

A rogue group of Perl hackers has presented a plan to add a "use
really_goddamn_strict" pragma that would enforce readability and
UNobfuscation. With this pragma in force, the Perl compiler might say:

* Warning: Write-only code detected between lines 612 and 734. While this
  code is perfectly legal, you won't have any clue what it does in two
  weeks. I recommend you start over.

* Warning: Code at line 1,024 is indistinguishable from line noise or the
  output of /dev/random

* Warning: Have you ever properly indented a piece of code in your entire
  life? Evidently not.

* Warning: I think you can come up with a more descriptive variable name than
  "foo" at line 1,523.

* Warning: Programmer attempting to re-invent the wheel at line 2,231.
  There's a function that does the exact same thing on CPAN -- and it
  actually works.
"... and don't ask me about the extraneous parenthesis. I bet some LISP
programmer felt alone and decided to make it a bit more homey."

        - Linus Torvalds
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.

        - Linus Torvalds
<mikkei> There once was a guy called Riel,
<mikkei> Who thought Tux should have been an Eel,
<mikkei> Although he was a fine programmer,
<mikkei> He called the little penguin,
<mikkei> A veritably ugly hack,
<mikkei> But they all laughed and said "He's on crack!"
<mikkei>  
<mikkei> There once was a guy called Riel,
<mikkei> At whose feet the newbies would kneel,
<mikkei> Each and every day, one newbie would say:
<mikkei> "Make my patch the Patch of the Month."
<mikkei> But Riel, saying no with a negative, "hummpfh"
<mikkei> Would say "fsck off" to the newbies's dismay.

        - Anonymous on #kernelnewbies
<viro> "scanf is tough" -- programmer Barbie...

        - Al Viro on #kernelnewbies
"scanf is tough" --- programmer Barbie...

        - Alexander Viro on linux-kernel
<Coderjoe> gib, perl?
<gib> methinks perl is the programmer's Swiss Army Chainsaw
<knghtbrd> "Java for the COBOL Programmer"
<knghtbrd> who writes these things?
<raptor> people on crack
<raptor> and cobol programmers
<raptor> :)
<knghtbrd> that's redundant.
<Deek> "A good programmer can write FORTRAN in any language."
<Deek> knghtbrd has proven that you can write C++ in any language too.
       <grin>
<Mercury> We are currently considdering if we should give him or prize, or
          kill him..
<Mercury> (Of course, by all rights, this means we should give him the
          prize, and then kill him.. <G>)
The choice of approaches could be made the responsibility of the
programmer.
             -- Larry Wall in <199709081901.MAA20863@wall.org>
(To the extent that anyone but a Prolog programmer can understand \X totally.
(And to the extent that a Prolog programmer can understand "cut". :-))
             -- Larry Wall in <199710211624.JAA17833@wall.org>
No guarantee of accuracy or completeness!
©TU Chemnitz, 2006-2024
Your feedback:
Ad partners