software rot n.
Term used to describe the tendency of
software that has not been used in a while to lose; such
failure may be semi-humorously ascribed to bit rot. More
commonly, `software rot' strikes when a program's assumptions
become out of date. If the design was insufficiently robust,
this may cause it to fail in mysterious ways.
For example, owing to endemic shortsightedness in the design of
COBOL programs, most will succumb to software rot when their
2-digit year counters wrap around at the beginning of the
year 2000. Actually, related lossages often afflict centenarians
who have to deal with computer software designed by unimaginative
clods. One such incident became the focus of a minor public flap
in 1990, when a gentleman born in 1889 applied for a driver's
license renewal in Raleigh, North Carolina. The new system
refused to issue the card, probably because with 2-digit years the
ages 101 and 1 cannot be distinguished.
Historical note: Software rot in an even funnier sense than the
mythical one was a real problem on early research computers (e.g.,
the R1; see grind crank). If a program that depended on a
peculiar instruction hadn't been run in quite a while, the user
might discover that the opcodes no longer did the same things they
once did. ("Hey, so-and-so needs an instruction to do
such-and-such. We can snarf this opcode, right? No one uses
it.")
Another classic example of this sprang from the time an MIT hacker
found a simple way to double the speed of the unconditional jump
instruction on a PDP-6, so he patched the hardware. Unfortunately,
this broke some fragile timing software in a music-playing program,
throwing its output out of tune. This was fixed by adding a
defensive initialization routine to compare the speed of a timing
loop with the real-time clock; in other words, it figured out how
fast the PDP-6 was that day, and corrected appropriately.
Compare bit rot.
Term used to describe the tendency of
software that has not been used in a while to lose; such
failure may be semi-humorously ascribed to bit rot. More
commonly, `software rot' strikes when a program's assumptions
become out of date. If the design was insufficiently robust,
this may cause it to fail in mysterious ways.
For example, owing to endemic shortsightedness in the design of
COBOL programs, most will succumb to software rot when their
2-digit year counters wrap around at the beginning of the
year 2000. Actually, related lossages often afflict centenarians
who have to deal with computer software designed by unimaginative
clods. One such incident became the focus of a minor public flap
in 1990, when a gentleman born in 1889 applied for a driver's
license renewal in Raleigh, North Carolina. The new system
refused to issue the card, probably because with 2-digit years the
ages 101 and 1 cannot be distinguished.
Historical note: Software rot in an even funnier sense than the
mythical one was a real problem on early research computers (e.g.,
the R1; see grind crank). If a program that depended on a
peculiar instruction hadn't been run in quite a while, the user
might discover that the opcodes no longer did the same things they
once did. ("Hey, so-and-so needs an instruction to do
such-and-such. We can snarf this opcode, right? No one uses
it.")
Another classic example of this sprang from the time an MIT hacker
found a simple way to double the speed of the unconditional jump
instruction on a PDP-6, so he patched the hardware. Unfortunately,
this broke some fragile timing software in a music-playing program,
throwing its output out of tune. This was fixed by adding a
defensive initialization routine to compare the speed of a timing
loop with the real-time clock; in other words, it figured out how
fast the PDP-6 was that day, and corrected appropriately.
Compare bit rot.
Related:
- bit rot n.
[common] Also bit decay. Hypothetical
disease the existence of which has been deduced from the
observation that unused programs or features will often stop
working after sufficient time has passed
even if `nothing has changed'. The theory explains that bits decay as if they were radioactive.... - bit rot: n. Also {bit decay}. Hypothetical disease the existence
of which has been deduced from the observation that unused programs
or features will often stop working after sufficient time has
passed
even if `nothing has changed'. The theory explains that bits decay as if they were radioactive.... - brute force adj.
Describes a primitive programming style
one in which the programmer relies on the computer's processing power instead of using his or her own intelligence to simplify the problem, often ignoring problems of scale and applying naive methods suited to small problems directly to large ones.... - bit bang n.
Transmission of data on a serial line, when
accomplished by rapidly tweaking a single output bit, in software,
at the appropriate times.
The technique is a simple loop with eight OUT and SHIFT instruction pairs for each byte.... - bug n.
An unwanted and unintended property of a program or
piece of hardware, esp.
one that causes it to malfunction. Antonym of feature.... - phase of the moon n.
Used humorously as a random parameter
on which something is said to depend.
Sometimes implies unreliability of whatever is dependent, or that reliability seems to be dependent on conditions nobody has been able to determine.... - bit bang: n. Transmission of data on a serial line, when
accomplished by rapidly tweaking a single output bit, in software,
at the appropriate times.
The technique is a simple loop with eight OUT and SHIFT instruction pairs for each byte.... - cosmic rays n.
Notionally, the cause of bit rot.
However, this is a semi-independent usage that may be invoked as a humorous way to handwave away any minor randomness that doesn't seem worth the bother of investigating.... - bit-paired keyboard n.,obs.
(alt. `bit-shift
keyboard') A non-standard keyboard layout that seems to have
originated with the Teletype ASR-33 and remained common for several
years on early computer equipment.
The ASR-33 was a mechanical device (see EOU), so the only way to generate the character codes from keystrokes was by some physical linkage....
