The best code is the code never written.
The most secure code is the code never written.
The most reliable code is the code never written.
The fastest code is the code never written.
Less is more.
Related to the classic quote:
"It seems that perfection is attained, not when there is nothing more to add, but when there is nothing more to take away." -Antoine de Saint-Exupery
And some others:
Days of development can save hours of planning.
Your real problem is that you don't understand your problem.
Reading code is harder than writing code.
Great theme. I'm reminded of a Gordon Bell quote found in Jon Bentley's 'Programming Pearls': 'The cheapest, fastest and most reliable components of a computer system are those that aren't there.'
“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 way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.” ― C.A.R. Hoare
I love this one (saw it in one of the pull requests)
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." --Brian Kernighan
"Programs must be written for people to read, and only incidentally for machines to execute." - Abelson & Sussman, SICP, preface to the first edition
"That language is an instrument of human reason, and not merely a medium for the expression of thought, is a truth generally admitted." - George Boole, quoted in Iverson's Turing Award Lecture
"Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay
"Dealing with failure is easy: Work hard to improve. Success is also easy to handle: You've solved the wrong problem. Work hard to improve." - Alan Perlis
"Premature optimization is the root of all evil (or at least most of it) in programming." - Donald Knuth
"Lisp has jokingly been called "the most intelligent way to misuse a computer". I think that description is a great compliment because it transmits the full flavor of liberation: it has assisted a number of our most gifted fellow humans in thinking previously impossible thoughts." - Edsger Dijkstra, CACM, 15:10
"The key to performance is elegance, not battalions of special cases." - Jon Bentley and Doug McIlroy
"Change breaks the brittle." - Jan Houtema
"Your twenties are always an apprenticeship, but you don't always know what for." - Jan Houtema
Love it! Same in music: hours spend mangling a piece makes you good at mangling that piece. Much better to do deliberate practice - slowly move through nailing every phrase, every note. Then speed up.
"Greenspun's Tenth Rule of Programming: any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp." - Philip Greenspun
"Lisp isn't a language, it's a building material."- Alan Kay
"The greatest single programming language ever designed" - Alan Kay, on Lisp
"Lisp is a programmable programming language." - John Foderaro, CACM, September 1991
"Lisp is worth learning for the profound enlightenment experience you will have when you finally get it; that experience will make you a better programmer for the rest of your days, even if you never actually use Lisp itself a lot." - Eric Raymond, "How to Become a Hacker"
"Lisp is a programmer amplifier." - Martin Rodgers (first said by Chuck Moore about Forth)
Most papers in computer science describe how their author learned what someone else already knew. - Peter Landin (This is a paraphrase. I'd appreciate it if anyone can tell me the exact quote. - pg)
"The only way to learn a new programming language is by writing programs in it." - Kernighan and Ritchie
"SQL, Lisp, and Haskell are the only programming languages that I've seen where one spends more time thinking than typing." - Philip Greenspun
"The continuation that obeys only obvious stack semantics, O grasshopper, is not the true continuation." - Guy Steele
Jon Bentley [1] had a whole chapter in More Programming Pearls: Confessions of a Coder [2], called Bumper-Sticker Computer Science, which was of this sort. There seems to be a copy of it online [3].
OP here, I can't grow a beard, but yeah, that's pretty much what it is.
It's a reference to how "beards" have become a symbol in popular culture associated with wisdom. The highest level of such beardage is the "greybeard" while the lowest is "neckbeard" (associated with people who don't know anything but pretend to).
It's been around for a long time. Think of the stereotypical medieval wizard or Greek philosopher. What does he always have? Bingo.
For most of human existence, listening to the people with grey hair (male and female) was the most reliable way of learning how to survive. They'd been there, done that, and lived to tell the tale.
It's only in recent history that things have started changing so fast that age==wisdom is no longer always true (though I think it still is more often true than some of the younger folks would like to believe).
Edit: a previous poster mentioned Gandalf. The Gandalf character wouldn't work nearly as well if he had a nose ring and a bunch of trendy facial tats, right?
"The buggiest code is that which has had the most bugs fixed."
or
"Buggy code is buggy."
(That is, having had bugs fixed is an indicator that the code is either complex or poorly written, and is likely to harbor further undiscovered (or newly introduced) bugs.)
Could the first also imply towards that all code is buggy, absence of proof doesn't equal proof of absence. As in, if you don't find bugs yet, it doesn't mean they don't exist.
Au contraire – the evidence of absence of bugs is that the code works. (i.e., to some degree, programs find their own bugs simply by being used.)
Code that has been humming along issue-free is likely either simple, or well-written, and harbors few, if any, bugs. Otherwise, they would have evinced themselves by now.
I believe openSSL has been humming along issue free for quite a while before a somewhat famous bug popped up for some anecdotal evidence at a refutation.
"A framework is an understanding of how things could fit together.
When designing these things, it's important to remember that your understanding is incomplete."
Thanks! :) It reminds me of the craigslist posts about how an "idea guy" wants to build a site "just like facebook but better" and they're offering a few hundred dollars. "You can build that in less than a week, right?"
"It seems that perfection is attained, not when there is nothing more to add, but when there is nothing more to take away." -Antoine de Saint-Exupery
And some others:
Could get a LOT based on this: Frequently Forgotten Facts about Software Engineering http://www.eng.auburn.edu/~hendrix/comp6710/readings/Forgott... [PDF](Also in book form, "Facts and Fallacies of Software Engineering" Robert Glass)