Dictionary De - En
De - Es
De - Pt| Proverbs, aphorisms, quotations (English) | by Linux fortune |
| I still maintain the point that designing a monolithic kernel in 1991 is a fundamental error. Be thankful you are not my student. You would not get a high grade for such a design :-) (Andrew Tanenbaum to Linus Torvalds) | |
| According to Microsoft, it's by design | |
| 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 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" | |
| Almost anything derogatory you could say about today's software design would be accurate. -- K.E. Iverson | |
| AmigaDOS Beer: The company has gone out of business, but their recipe has been picked up by some weird German company, so now this beer will be an import. This beer never really sold very well because the original manufacturer didn't understand marketing. Like Unix Beer, AmigaDOS Beer fans are an extremely loyal and loud group. It originally came in a 16-oz. can, but now comes in 32-oz. cans too. When this can was originally introduced, it appeared flashy and colorful, but the design hasn't changed much over the years, so it appears dated now. Critics of this beer claim that it is only meant for watching TV anyway. | |
| At first sight, the idea of any rules or principles being superimposed on the creative mind seems more likely to hinder than to help, but this is quite untrue in practice. Disciplined thinking focuses inspiration rather than blinkers it. -- G.L. Glegg, "The Design of Design" | |
| Brian Kernighan has an automobile which he helped design. Unlike most automobiles, it has neither speedometer, nor gas gauge, nor any of the numerous idiot lights which plague the modern driver. Rather, if the driver makes any mistake, a giant "?" lights up in the center of the dashboard. "The experienced driver", he says, "will usually know what's wrong." | |
| ... C++ offers even more flexible control over the visibility of member objects and member functions. Specifically, members may be placed in the public, private, or protected parts of a class. Members declared in the public parts are visible to all clients; members declared in the private parts are fully encapsulated; and members declared in the protected parts are visible only to the class itself and its subclasses. C++ also supports the notion of *_______friends*: cooperative classes that are permitted to see each other's private parts. -- Grady Booch, "Object Oriented Design with Applications" | |
| Conceptual integrity in turn dictates that the design must proceed from one mind, or from a very small number of agreeing resonant minds. -- Frederick Brooks Jr., "The Mythical Man Month" | |
| Cosmotronic Software Unlimited Inc. does not warrant that the functions contained in the program will meet your requirements or that the operation of the program will be uninterrupted or error-free. However, Cosmotronic Software Unlimited Inc. warrants the diskette(s) on which the program is furnished to be of black color and square shape under normal use for a period of ninety (90) days from the date of purchase. NOTE: IN NO EVENT WILL COSMOTRONIC SOFTWARE UNLIMITED OR ITS DISTRIBUTORS AND THEIR DEALERS BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING ANY LOST PROFIT, LOST SAVINGS, LOST PATIENCE OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. -- Horstmann Software Design, the "ChiWriter" user manual | |
| Do not simplify the design of a program if a way can be found to make it complex and wonderful. | |
| [From the operation manual for the CI-300 Dot Matrix Line Printer, made in Japan]: The excellent output machine of MODEL CI-300 as extraordinary DOT MATRIX LINE PRINTER, built in two MICRO-PROCESSORs as well as EAROM, is featured by permitting wonderful co-existence such as; "high quality against low cost," "diversified functions with compact design," "flexibility in accessibleness and durability of approx. 2000,000,00 Dot/Head," "being sophisticated in mechanism but possibly agile operating under noises being extremely suppressed" etc. And as a matter of course, the final goal is just simply to help achieve "super shuttle diplomacy" between cool data, perhaps earned by HOST COMPUTER, and warm heart of human being. | |
| I've noticed several design suggestions in your code. | |
| If it happens once, it's a bug. If it happens twice, it's a feature. If it happens more than twice, it's a design philosophy. | |
| ... it is easy to be blinded to the essential uselessness of them by the sense of achievement you get from getting them to work at all. In other words... their fundamental design flaws are completely hidden by their superficial design flaws. -- The Hitchhiker's Guide to the Galaxy, on the products of the Sirius Cybernetics Corporation. | |
| Overall, the philosophy is to attack the availability problem from two complementary directions: to reduce the number of software errors through rigorous testing of running systems, and to reduce the effect of the remaining errors by providing for recovery from them. An interesting footnote to this design is that now a system failure can usually be considered to be the result of two program errors: the first, in the program that started the problem; the second, in the recovery routine that could not protect the system. -- A.L. Scherr, "Functional Structure of IBM Virtual Storage Operating Systems, Part II: OS/VS-2 Concepts and Philosophies," IBM Systems Journal, Vol. 12, No. 4. | |
| The primary function of the design engineer is to make things difficult for the fabricator and impossible for the serviceman. | |
| There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies and the other is to make it so complicated that there are no obvious deficiencies. -- C.A.R. Hoare | |
| 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" | |
| 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" | |
| X windows: It's not how slow you make it. It's how you make it slow. The windowing system preferred by masochists 3 to 1. Built to take on the world... and lose! Don't try it 'til you've knocked it. Power tools for Power Fools. Putting new limits on productivity. The closer you look, the cruftier we look. Design by counterexample. A new level of software disintegration. No hardware is safe. Do your time. Rationalization, not realization. Old-world software cruftsmanship at its finest. Gratuitous incompatibility. Your mother. THE user interference management system. You can't argue with failure. You haven't died 'til you've used it. The environment of today... tomorrow! X windows. | |
| You can bring any calculator you like to the midterm, as long as it doesn't dim the lights when you turn it on. -- Hepler, Systems Design 182 | |
| "Don't fear the pen. When in doubt, draw a pretty picture." --Baker's Third Law of Design. | |
| The computer can't tell you the emotional story. It can give you the exact mathematical design, but what's missing is the eyebrows. - Frank Zappa | |
| There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies and the other is to make it so complicated that there are no obvious deficiencies. - Charles Anthony Richard Hoare | |
| In the pitiful, multipage, connection-boxed form to which the flowchart has today been elaborated, it has proved to be useless as a design tool -- programmers draw flowcharts after, not before, writing the programs they describe. - Fred Brooks, Jr. | |
| Conceptual integrity in turn dictates that the design must proceed from one mind, or from a very small number of agreeing resonant minds. - Frederick Brooks Jr., "The Mythical Man Month" | |
| It is important to note that probably no large operating system using current design technology can withstand a determined and well-coordinated attack, and that most such documented penetrations have been remarkably easy. -- B. Hebbard, "A Penetration Analysis of the Michigan Terminal System", Operating Systems Review, Vol. 14, No. 1, June 1980, pp. 7-20 | |
| Overall, the philosophy is to attack the availability problem from two complementary directions: to reduce the number of software errors through rigorous testing of running systems, and to reduce the effect of the remaining errors by providing for recovery from them. An interesting footnote to this design is that now a system failure can usually be considered to be the result of two program errors: the first, in the program that started the problem; the second, in the recovery routine that could not protect the system. -- A. L. Scherr, "Functional Structure of IBM Virtual Storage Operating Systems, Part II: OS/VS-2 Concepts and Philosophies," IBM Systems Journal, Vol. 12, No. 4, 1973, pp. 382-400 | |
| 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" | |
| "One of the problems I've always had with propaganda pamphlets is that they're real boring to look at. They're just badly designed. People from the left often are very well-intended, but they never had time to take basic design classes, you know?" -- Art Spiegelman | |
| Ill-chosen abstraction is particularly evident in the design of the ADA runtime system. The interface to the ADA runtime system is so opaque that it is impossible to model or predict its performance, making it effectively useless for real-time systems. -- Marc D. Donner and David H. Jameson. | |
| There is something you must understand about the Soviet system. They have the ability to concentrate all their efforts on a given design, and develop all components simulateously, but sometimes without proper testing. Then they end up with a technological disaster like the Tu-144. In a technology race at the time, that aircraft was two months ahead of the Concorde. Four Tu-144s were built; two have crashed, and two are in museums. The Concorde has been flying safely for over 10 years. -- Victor Belenko, MiG-25 fighter pilot who defected in 1976 "Defense Electronics", Vol 20, No. 6, pg. 100 | |
| HP had a unique policy of allowing its engineers to take parts from stock as long as they built something. "They figured that with every design, they were getting a better engineer. It's a policy I urge all companies to adopt." -- Apple co-founder Steve Wozniak, "Will Wozniak's class give Apple to teacher?" EE Times, June 6, 1988, pg 45 | |
| "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 | |
| My own life has been spent chronicling the rise and fall of human systems, and I am convinced that we are terribly vulnerable. ... We should be reluctant to turn back upon the frontier of this epoch. Space is indifferent to what we do; it has no feeling, no design, no interest in whether or not we grapple with it. But we cannot be indifferent to space, because the grand, slow march of intelligence has brought us, in our generation, to a point from which we can explore and understand and utilize it. To turn back now would be to deny our history, our capabilities. -- James A. Michener | |
| design, v.: What you regret not doing later on. | |
| Quality control, n.: Assuring that the quality of a product does not get out of hand and add to the cost of its manufacture or design. | |
| Wombat's Laws of Computer Selection: (1) If it doesn't run Unix, forget it. (2) Any computer design over 10 years old is obsolete. (3) Anything made by IBM is junk. (See number 2) (4) The minimum acceptable CPU power for a single user is a VAX/780 with a floating point accelerator. (5) Any computer with a mouse is worthless. -- Rich Kulawiec | |
| Japanese Minimalism: The most frequently offered interior design aesthetic used by rootless career-hopping young people. -- Douglas Coupland, "Generation X: Tales for an Accelerated Culture" | |
| Climate and Surgery R C Gilchrist, who was shot by J Sharp twelve days ago, and who received a derringer ball in the right breast, and who it was supposed at the time could not live many hours, was on the street yesterday and the day before -- walking several blocks at a time. To those who design to be riddled with bullets or cut to pieces with Bowie-knives, we cordially recommend our Sacramento climate and Sacramento surgery. -- Sacramento Daily Union, September 11, 1861 | |
| An architect's first work is apt to be spare and clean. He knows he doesn't know what he's doing, so he does it carefully and with great restraint. As he designs the first work, frill after frill and embellishment after embellishment occur to him. These get stored away to be used "next time." Sooner or later the first system is finished, and the architect, with firm confidence and a demonstrated mastery of that class of systems, is ready to build a second system. This second is the most dangerous system a man ever designs. When he does his third and later ones, his prior experiences will confirm each other as to the general characteristics of such systems, and their differences will identify those parts of his experience that are particular and not generalizable. The general tendency is to over-design the second system, using all the ideas and frills that were cautiously sidetracked on the first one. The result, as Ovid says, is a "big pile." -- Frederick Brooks, "The Mythical Man Month" | |
| And this is a table ma'am. What in essence it consists of is a horizontal rectilinear plane surface maintained by four vertical columnar supports, which we call legs. The tables in this laboratory, ma'am, are as advanced in design as one will find anywhere in the world. -- Michael Frayn, "The Tin Men" | |
| Any circuit design must contain at least one part which is obsolete, two parts which are unobtainable, and three parts which are still under development. | |
| Lucas is the source of many of the components of the legendarily reliable British automotive electrical systems. Professionals call the company "The Prince of Darkness". Of course, if Lucas were to design and manufacture nuclear weapons, World War III would never get off the ground. The British don't like warm beer any more than the Americans do. The British drink warm beer because they have Lucas refrigerators. | |
| The Lord and I are in a sheep-shepherd relationship, and I am in a position of negative need. He prostrates me in a green-belt grazing area. He conducts me directionally parallel to non-torrential aqueous liquid. He returns to original satisfaction levels my psychological makeup. He switches me on to a positive behavioral format for maximal prestige of His identity. It should indeed be said that notwithstanding the fact that I make ambulatory progress through the umbragious inter-hill mortality slot, terror sensations will no be initiated in me, due to para-etical phenomena. Your pastoral walking aid and quadrupic pickup unit introduce me into a pleasurific mood state. You design and produce a nutriment-bearing furniture-type structure in the context of non-cooperative elements. You act out a head-related folk ritual employing vegetable extract. My beverage utensil experiences a volume crisis. It is an ongoing deductible fact that your inter-relational empathetical and non-ventious capabilities will retain me as their target-focus for the duration of my non-death period, and I will possess tenant rights in the housing unit of the Lord on a permanent, open-ended time basis. | |
| "So right now the only vendor that does such a stupid thing is Microsoft." -- Linus Torvalds on bad file system interface design. (Open Sources , 1999 O'Reilly and Associates.) | |
| This telethon isn't just about helping disenfranchised geeks. We're also here for the betterment of mankind through our research into finding a Cure for Windows. Each day, millions of man-hours are wasted due to design flaws in Microsoft Windows. Each day, millions of dollars are sent by business and individuals like yourself into a huge black hole known as "Microsoft" for exorbitantly priced software products that should be free. But don't worry. We've almost found a Cure for Windows. Geeks worldwide have toiled endlessly for the past eight years working on a replacement operating system called Linux. It's almost ready. Now we need to convince the world to use our creation and eliminate the virus known as Windows. -- Excerpt from Eric S. Raymond's speech during the Geek Grok '99 telethon held in Silicon Valley | |
| Brief History Of Linux (#23) Linus Torvalds certainly wasn't the only person to create their own operating system from scratch. Other people working from their leaky basements did create their own systems and now they are sick that they didn't become an Alpha Geek like Torvalds or a Beta Geek like Alan Cox. Linus had one advantage not many else did: Internet access. The world was full of half-implemented-Unix-kernels at the time, but they were sitting isolated on some hacker's hard drive, destined to be destroyed by a hard drive crash. Thankfully that never happened to Linux, mostly because everyone with Net access could download a copy instead of paying shipping charges to receive the code on a huge stack of unreliable floppy disks. Indeed, buried deep within a landfill in Lansing, Michigan sits a stack of still-readable 5-1/4 floppies containing the only known copy of "Windows Killer", a fully functional Unix kernel so elegant, so efficient, so easy-to-use that Ken Thompson himself would be jealous of its design. Unfortunately the author's mother threw out the stack of floppies in a bout of spring cleaning. The 14 year old author's talents were lost forever as his parents sent him to Law School. | |
| This nation is sinking into the quicksand of the Paperwork Age, a postmodern world in which judges issue meta-injuctions against other judges who issue injuctions against lawyers who file lawsuits every 3.2 minutes. It's an age where lawyers design ballots forms and then proceed to argue over how to count them. The United States has bluescreened. A fatal exception error occured on Election Night, and now all of our unsaved work has been lost. -- Jon Splatz, Humorix's Pundit and Social Commentator, ranting about the 2000 US Presidential Election From Hell and the dreaded "Lawyerclysm" | |
| The policy is not to have policy. It works as well in kernel design as politics. - Alan Cox on linux-kernel | |
| Basically, ioctl's will _never_ be done right, because of the way people think about them. They are a back door. They are by design typeless and without rules. They are, in fact, the Microsoft of UNIX. - Linus Torvalds on linux-kernel | |
| Code like that would not pass through anybody's yuck-o-meter. - Linus Torvalds about design on linux-kernel | |
| Linus, Alan - Please apply the following self-explanatory patch. + /* LynuxWorks are politely reminded that removing copyright + notices is an offence under the Copyright Design and + Patents Act 1988, and under equivalent non-UK law in + accordance with the Berne Convention. */ + printk("Portions (C) 2000, 2001 Red Hat, Inc.\n"); - David Woodhouse on linux-kernel | |
| > That is reimplementing file system functionality in user space. > I'm in doubts that this is considered good design... Keeping things out of the kernel is good design. Your block indirections are no different to other database formats. Perhaps you think we should have fsql_operation() and libdb in kernel 8) - Alan Cox on linux-kernel | |
| From: Alan Cox <alan@lxorguk.ukuu.org.uk> Subject: Re: Yet another design for /proc. Or actually /kernel. > Here's my go at a new design for /proc. I designed it from a userland > point of view and tried not to drown myself into details. Did you have to change the subject line. It makes it harder to kill file when people keep doing that | |
| There is a bog-standard way to combine several files in one - cpio. Or tar. No need to bring Apple Shit-For-Design(tm)(r) when standard tools are quite enough. - Alexander Viro on linux-kernel | |
| <evilkalla> heh, I never took a coding class <evilkalla> or a graphics class <evilkalla> or a software design class <vegan> and it shows :P | |
| I still maintain the point that designing a monolithic kernel in 1991 is a fundamental error. Be thankful you are not my student. You would not get a high grade for such a design :-) -- Andrew Tanenbaum to Linus Torvalds | |
| The most important design issue... is the fact that Linux is supposed to be fun... -- Linus Torvalds at the First Dutch International Symposium on Linux | |
| * Phaedrus wishes he could get a machine that consists of Sparc IO, Alpha Processors and sleek design of an SGI <pp> And intel prices -- Seen on #Linux | |
| But the greatest Electrical Pioneer of them all was Thomas Edison, who was a brilliant inventor despite the fact that he had little formal education and lived in New Jersey. Edison's first major invention in 1877, was the phonograph, which could soon be found in thousands of American homes, where it basically sat until 1923, when the record was invented. But Edison's greatest achievement came in 1879, when he invented the electric company. Edison's design was a brilliant adaptation of the simple electrical circuit: the electric company sends electricity through a wire to a customer, then immediately gets the electricity back through another wire, then (this is the brilliant part) sends it right back to the customer again. This means that an electric company can sell a customer the same batch of electricity thousands of times a day and never get caught, since very few customers take the time to examine their electricity closely. In fact the last year any new electricity was generated in the United States was 1937; the electric companies have been merely re-selling it ever since, which is why they have so much free time to apply for rate increases. -- Dave Barry, "What is Electricity?" | |
| What they say: What they mean: A major technological breakthrough... Back to the drawing board. Developed after years of research Discovered by pure accident. Project behind original schedule due We're working on something else. to unforseen difficulties Designs are within allowable limits We made it, stretching a point or two. Customer satisfaction is believed So far behind schedule that they'll be assured grateful for anything at all. Close project coordination We're gonna spread the blame, campers! Test results were extremely gratifying It works, and boy, were we surprised! The design will be finalized... We haven't started yet, but we've got to say something. The entire concept has been rejected The guy who designed it quit. We're moving forward with a fresh We hired three new guys, and they're approach kicking it around. A number of different approaches... We don't know where we're going, but we're moving. Preliminary operational tests are Blew up when we turned it on. inconclusive Modifications are underway We're starting over. | |
| What they say: What they mean: New Different colors from previous version. All New Not compatible with previous version. Exclusive Nobody else has documentation. Unmatched Almost as good as the competition. Design Simplicity The company wouldn't give us any money. Fool-proof Operation All parameters are hard-coded. Advanced Design Nobody really understands it. Here At Last Didn't get it done on time. Field Tested We don't have any simulators. Years of Development Finally got one to work. Unprecedented Performance Nothing ever ran this slow before. Revolutionary Disk drives go 'round and 'round. Futuristic Only runs on a next generation supercomputer. No Maintenance Impossible to fix. Performance Proven Worked through Beta test. Meets Tough Quality Standards It compiles without errors. Satisfaction Guaranteed We'll send you another pack if it fails. Stock Item We shipped it before and can do it again. | |
| Besides, including <std_ice_cubes.h> is a fatal error on machines that don't have it yet. Bad language design, there... :-) -- Larry Wall in <1991Aug22.220929.6857@netlabs.com> | |
| Anyway, there's plenty of room for doubt. It might seem easy enough, but computer language design is just like a stroll in the park. Jurassic Park, that is. -- Larry Wall in <1994Jun15.074039.2654@netlabs.com> | |
| (Presuming for the sake of argument that it's even *possible* to design better code in Perl than in C. :-) -- Larry Wall on core code vs. module code design | |
| Part of language design is purturbing the proposed feature in various directions to see how it might generalize in the future. -- Larry Wall in <199709032332.QAA21669@wall.org> | |
