GoQuotes / quotes.xml

<quotes>
    <quote>
        <citation>Every time I see some piece of medical research saying that caffeine is good for you, I high-five myself. Because I'm going to live forever.</citation>
        <author>Linus Torvalds</author>
        <year>2010</year>
    </quote>
    <quote>
        <citation>I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones.</citation>
        <author>Linus Torvalds</author>
        <year>1991</year>
    </quote>
    <quote>
        <citation>Only wimps use tape backup: real men just upload their important stuff on ftp, and let the rest of the world mirror it ;)</citation>
        <author>Linus Torvalds</author>
        <year>1996</year>
    </quote>
    <quote>
      <citation>Praising companies for providing APIs to get your own data out is like praising auto companies for not filling your airbags with gravel.</citation>
      <author>Mark Pilgrim</author>
      <year>2007</year>
      <source>http://diveintomark.org/archives/2007/08/01/lolwreck</source>
    </quote>
    <quote>
      <citation>Beware of bugs in the above code; I have only proved it correct, not tried it.</citation>
      <author>Donald Ervin Knuth</author>
      <year>1977</year>
    </quote>
    <quote>
      <citation>A mathematical formula should never be "owned" by anybody! Mathematics belong to God.</citation>
      <author>Donald Ervin Knuth</author>
      <year>1999</year>
    </quote>
    <quote>
      <citation>Thanks to Mr. Gates, we now know that an open Internet with protocols anyone can implement is communism; it was set up by that famous communist agent, the US Department of Defense.</citation>
      <author>Richard Matthew Stallman</author>
      <year>2005</year>
    </quote>
    <quote>
        <citation>Let me start with a well-established fact: by and large the programming community displays a very ambivalent attitude towards the problem of program correctness. A major part of the average programmer's activity is devoted to debugging, and from this observation we may conclude that the correctness of his programs —or should we say: their patent incorrectness?— is for him a matter of considerable concern. I claim that a programmer has only done a decent job when his program is flawless and not when his program is functioning properly only most of the time. But I have had plenty of opportunity to observe that this suggestion is repulsive to many professional programmers: they object to it violently! Apparently, many programmers derive the major part of their intellectual satisfaction and professional excitement from not quite understanding what they are doing. In this streamlined age, one of our most under-nourished psychological needs is the craving for Black Magic, and apparently the automatic computer can satisfy this need for the professional software engineers, who are secretly enthralled by the gigantic risks they take in their daring irresponsibility. They revel in the puzzles posed by the task of debugging. They defend —by appealing to all sorts of supposed Laws of Nature— the right of existence of their program bugs, because they are so attached to them: without the bugs, they feel, programming would no longer be what is used to be! (In the latter feeling I think —if I may say so— that they are quite correct.)</citation>
        <author>Edsger Wybe Dijkstra</author>
        <year></year>
    </quote>
    <quote>
        <citation>You have to believe in something in your life. Strongly. Obsessively. Undoubtedly.</citation>
        <author>Oksana Chernyavskaya</author>
        <year>2011</year>
    </quote>
</quotes>
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.