Zitate von Eric S. Raymond

Eric S. Raymond Foto

1   0

Eric S. Raymond

Geburtstag: 4. Dezember 1957

Eric Steven Raymond , auch bekannt als ESR, ist ein US-amerikanischer Autor und Softwareentwickler in der Hacker- und Open-Source-Szene.

Zitate Eric S. Raymond

Bestellen Sie Zitate:

„Die Linux-Gemeinde gleicht schon eher einem großen plappernden Basar mit verschiedenen Tagesabläufen und Ansätzen (repräsentiert durch die Linux-Archive, in die jeder einbringen kann, was er will). Dass aus diesen Teilen ein zusammenhängendes stabiles Betriebssystem nur aufgrund einer Reihe von wundersamen Zufällen entstehen konnte, liegt ja wohl auf der Hand.“ Eric S. Raymond, "Die Kathedrale und der Basar", Quelle: web. archive. org, (übersetzt von Lukas Müller)

„Every good work of software starts by scratching a developer’s personal itch.“ Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary

„CSV (fields separated by commas, double quotes used to escape commas, no continuation lines) is rarely found under Unix.“ The Art of UNIX Programming

„When you feel the urge to design a complex binary file format, or a complex binary application protocol, it is generally wise to lie down until the feeling passes.“ The Art of UNIX Programming

„When the superior programmer refrains from coding, his force is felt for a thousand miles.“ The Art of UNIX Programming

„Transparency is therefore more than an esthetic triumph; it is a victory that will be reflected in lower costs throughout the software’s life cycle. 6.2.2“ The Art of UNIX Programming

„Top-down tends to be good practice when three preconditions are true: (a) you can specify in advance precisely what the program is to do, (b) the specification is unlikely to change significantly during implementation, and (c) you have a lot of freedom in choosing, at a low level, how the program is to get that job done.“ The Art of UNIX Programming

„Use # as an introducer for comments. It is good to have a way to embed annotations and comments in data files. It’s best if they’re actually part of the file structure, and so will be preserved by tools that know its format. For comments that are not preserved during parsing, # is the conventional start character.“ The Art of UNIX Programming

„Python language is one example. As we noted above, it is also heavily used for mathematical and scientific papers, and will probably dominate that niche for some years yet. 18.3.3“ The Art of UNIX Programming

„There is a flip side to this. In the Unix world, libraries which are delivered as libraries should come with exerciser programs.“ The Art of UNIX Programming

„Web pages get bogged down in the dispute over whether the reader or author should control the appearance.“ The Art of UNIX Programming

„If you have any trouble sounding condescending, find a Unix user to show you how it’s done. Dilbert newsletter 3.0, 1994 —Scott Adams“ The Art of UNIX Programming

„To design the perfect anti-Unix, write an operating system that thinks it knows what you’re doing better than you do. And then adds injury to insult by getting it wrong.“ The Art of UNIX Programming

„The nightmare scenario is one in which corporate monopolism and statist power-seeking, always natural allies, feed back into each other and create rationales for increasing regulation, repression, and criminalization of digital speech.“ The Art of UNIX Programming

„Rushing to optimize before the bottlenecks are known may be the only error to have ruined more designs than feature creep. From tortured code to incomprehensible data layouts, the results of obsessing about speed or memory or disk usage at the expense of transparency and simplicity are everywhere. They spawn innumerable bugs and cost millions of man-hours—often, just to get marginal gains in the use of some resource much less expensive than debugging time. Disturbingly often, premature local optimization actually hinders global optimization (and hence reduces overall performance). A prematurely optimized portion of a design frequently interferes with changes that would have much higher payoffs across the whole design, so you end up with both inferior performance and excessively complex code.“ The Art of UNIX Programming

„Tools that look glossy but shatter under stress are not good long-term value. Unix“ The Art of UNIX Programming

Ähnliche Autoren