Real Programmers

REAL PROGRAMMERS DON'T WRITE SPECS

Real programmers don't write specs -- users should consider themselves lucky
to get any programs at all and take what they can get.

Real programmers don't comment their code. If it was hard to write, it should
be hard to understand.

Real programmers don't write application programs, they program right down to
the bare metal. Application programming is for feebs who can't do systems
programming.

Real programmers don't eat quiche. They eat Twinkies and take-out Szechuan.

Real programmers don't write in COBOL. COBOL is for wimpy applications
programmers.

Real programmers' programs never work right the first time. But if you throw
them on the machine, they can be patched into working in "only a few" 30 hour
debugging sessions.

Real programmers don't write in FORTRAN. FORTRAN is for pipe stress freaks
and crystallography weenies.

Real programmers never work 9 to 5. If any real programmers are around at 9 am,
it's because they were up all night.

Real programmers don't write in BASIC. Actually, no programmers write in
BASIC after the age of 12.

Real programmers don't write in PL/I. PL/I is for people who can't decide
whether to write in FORTRAN or COBOL.

Real programmers don't play tennis, or any other sport that requires you to
change clothes. Mountain climbing is OK, and real programmers wear their
climbing boots to work in case a mountain should suddenly spring up in the
middle of the machine room.

Real programmers don't document. Documentation is for simps who can't read
the listings or the object deck.

Real programmers don't write in PASCAL, or BLISS, or ADA, or any of those
pinko computer science languages. Strong typing is for people with weak
memories.

Real programmers don't draw flowcharts; the code speaks for itself.

Real programmers don't plan ahead; they have a gut feel for the work
required.

(see the rest here, http://www.boo.net/~jasonp/progrmrs )

| I like _NIGGERquote. But where does it come from and how is it made?