Real Programmer n.
[indirectly, from the book
"Real Men Don't Eat Quiche"] A particular sub-variety of
hacker: one possessed of a flippant attitude toward complexity that
is arrogant even when justified by experience. The archetypal
`Real Programmer' likes to program on the bare metal and is
very good at same, remembers the binary opcodes for every machine
he has ever programmed, thinks that HLLs are sissy, and uses a
debugger to edit his code because full-screen editors are for
wimps. Real Programmers aren't satisfied with code that hasn't
been bummed into a state of tenseness just short of
rupture. Real Programmers never use comments or write
documentation: "If it was hard to write", says the Real
Programmer, "it should be hard to understand." Real Programmers
can make machines do things that were never in their spec sheets;
in fact, they are seldom really happy unless doing so. A Real
Programmer's code can awe with its fiendish brilliance, even as its
crockishness appalls. Real Programmers live on junk food and
coffee, hang line-printer art on their walls, and terrify the crap
out of other programmers -- because someday, somebody else might
have to try to understand their code in order to change it. Their
successors generally consider it a Good Thing that there
aren't many Real Programmers around any more. For a famous (and
somewhat more positive) portrait of a Real Programmer, see
"The Story of Mel" in Appendix A. The term itself
was popularized by a 1983 Datamation article "Real
Programmers Don't Use Pascal" by Ed Post, still circulating on
Usenet and Internet in on-line form.
You can browse "Real Programmers Don't Use Pascal" from the
Datamation home page http://www.datamation.com.
[indirectly, from the book
"Real Men Don't Eat Quiche"] A particular sub-variety of
hacker: one possessed of a flippant attitude toward complexity that
is arrogant even when justified by experience. The archetypal
`Real Programmer' likes to program on the bare metal and is
very good at same, remembers the binary opcodes for every machine
he has ever programmed, thinks that HLLs are sissy, and uses a
debugger to edit his code because full-screen editors are for
wimps. Real Programmers aren't satisfied with code that hasn't
been bummed into a state of tenseness just short of
rupture. Real Programmers never use comments or write
documentation: "If it was hard to write", says the Real
Programmer, "it should be hard to understand." Real Programmers
can make machines do things that were never in their spec sheets;
in fact, they are seldom really happy unless doing so. A Real
Programmer's code can awe with its fiendish brilliance, even as its
crockishness appalls. Real Programmers live on junk food and
coffee, hang line-printer art on their walls, and terrify the crap
out of other programmers -- because someday, somebody else might
have to try to understand their code in order to change it. Their
successors generally consider it a Good Thing that there
aren't many Real Programmers around any more. For a famous (and
somewhat more positive) portrait of a Real Programmer, see
"The Story of Mel" in Appendix A. The term itself
was popularized by a 1983 Datamation article "Real
Programmers Don't Use Pascal" by Ed Post, still circulating on
Usenet and Internet in on-line form.
You can browse "Real Programmers Don't Use Pascal" from the
Datamation home page http://www.datamation.com.
Related:
- Real programmers don't comment their code. If it was hard to write,
it should be hard to understand... - Real programmers don't comment their code. It was hard to write,
it should be hard to understand... - Datamation /day`t*-may'sh*n/ n.
A magazine that many
hackers assume all suits read.
Used to question an unbelieved quote, as in "Did... - Real programmers don't document their code. The brilliance of the
program itself is self-evident,
and anyone who can't figure it out isn't a real programmer... - REAL programmers write self
modifying code... - Unix is a lot more complicated (than CP/M) of course -
the typical Unix hacker can never remember what the... - Real programmers don't document; if it was
hard to write,
it should be hard to understand...
From the same category:
- console n.
1. The operator's station of a mainframe.
In times past, this was a privileged location that... - recursive acronym n.
A hackish (and especially MIT)
tradition is to choose acronyms/abbreviations that refer humorously
to themselves or to other acronyms/abbreviations.
The classic ... - console jockey n.
See terminal junkie... - free software n.
As defined by Richard M. Stallman and
used by the Free Software movement,
this means software that gives users enough freedom... - asbestos adj.
[common] Used as a modifier to anything
intended to protect one from flames;
also in other highly flame-suggestive usages. See...
