Proverbs, aphorisms, quotations (English) | by Linux fortune |
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 | |
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 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. | |
The following quote is from page 4-27 of the MSCP Basic Disk Functions Manual which is part of the UDA50 Programmers Doc Kit manuals: As stated above, the host area of a disk is structured as a vector of logical blocks. From a performance viewpoint, however, it is more appropriate to view the host area as a four dimensional hyper-cube, the four dimensions being cylinder, group, track, and sector. . . . Referring to our hyper-cube analogy, the set of potentially accessible blocks form a line parallel to the track axis. This line moves parallel to the sector axis, wrapping around when it reaches the edge of the hyper-cube. | |
To those accustomed to the precise, structured methods of conventional system development, exploratory development techniques may seem messy, inelegant, and unsatisfying. But it's a question of congruence: precision and flexibility may be just as disfunctional in novel, uncertain situations as sloppiness and vacillation are in familiar, well-defined ones. Those who admire the massive, rigid bone structures of dinosaurs should remember that jellyfish still enjoy their very secure ecological niche. -- Beau Sheil, "Power Tools for Programmers" | |
"Pseudocode can be used to some extent to aid the maintenance process. However, pseudocode that is highly detailed - approaching the level of detail of the code itself - is not of much use as maintenance documentation. Such detailed documentation has to be maintained almost as much as the code, thus doubling the maintenance burden. Furthermore, since such voluminous pseudocode is too distracting to be kept in the listing itself, it must be kept in a separate folder. The result: Since pseudocode - unlike real code - doesn't have to be maintained, no one will maintain it. It will soon become out of date and everyone will ignore it. (Once, I did an informal survey of 42 shops that used pseudocode. Of those 42, 0 [zero!], found that it had any value as maintenance documentation." --Meilir Page-Jones, "The Practical Guide to Structured Design", Yourdon Press (c) 1988 | |
"All the system's paths must be topologically and circularly interrelated for conceptually definitive, locally transformable, polyhedronal understanding to be attained in our spontaneous -- ergo, most economical -- geodesiccally structured thoughts." -- R. Buckminster Fuller [...and a total nonsequitur as far as I can tell. -kl] | |
Goto, n.: A programming tool that exists to allow structured programmers to complain about unstructured programmers. -- Ray Simard | |
Mid-Twenties Breakdown: A period of mental collapse occurring in one's twenties, often caused by an inability to function outside of school or structured environments coupled with a realization of one's essential aloneness in the world. Often marks induction into the ritual of pharmaceutical usage. -- Douglas Coupland, "Generation X: Tales for an Accelerated Culture" |