Favourite Programming Quotes
programmers.stackexchange.com
programmers.stackexchange.com
"On two occasions I have been asked, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" In one case a member of the Upper, and in the other a member of the Lower House put this question. I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question. — Charles Babbage"
Anyone who's interested, GIGO means "Garbage In, Garbage Out". Wiki: http://en.wikipedia.org/wiki/GIGO.
By the way, the Wikipedia page specifically mentions Babbage's quote.
"How long will people continue believing in the myth of the 15-year-old hacker genius while simultaneously decrying the unreliability of software before the cognitive dissonance finally cracks?" - Dave Herman (http://calculist.blogspot.com/2005/12/12-weeks-with-geeks.ht...)
Also, there are quite a few at cat-v (http://quotes.cat-v.org/programming/).
Bjarne Stroustrup
"I'm not a computer guy,” they'll say with a big smile on their face. Well gee, the personal computer is only the most significant invention to come along in the past 100 years. You'd think one might be mildly curious about how it works. -- Anon
By relieving the brain of all unnecessary work, a good notation sets it free to concentrate on more advanced problems, and, in effect, increases the mental power of the race. -- Alfred Whitehead (replace notation by abstraction and it holds for programming too)
As soon as we started programming, we found out to our surprise that it wasn't as easy to get programs right as we had thought. Debugging had to be discovered. I can remember the exact instant when I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs -- Maurice Wilkes
Eventually a friend of a friend is a security hole -- Anon
“I saw `cout’ being shifted “Hello world” times to the left and stopped right there.”
— Steve Gonedes
(via http://q4td.blogspot.com/search/label/programming)> There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors.
Not sure what the original source is, or even what the original formulation is, but it rings true to me.
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
Dan Garcia
"cracking is like sex with a prostitute, you have to get in, take all the goodies and get out without leaving a trace."
EDIT: spelling mistake