Some lovely software design quotes

  sonic0002        2012-10-13 09:13:34       6,664        1    

 

Every time when I read technical books, I like reading the quote of a famous person at the start of a chapter(if any), usually they are very interesting. Here is a collection of famous quotes.

  1. Life’s too short to build something nobody wants – Ash Maurya, Running Lean author
  2. Give someone a program, you frustrate them for a day; teach them how to program, you frustrate them for a lifetime. – David Leinweber
  3. 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. — C.A.R. Hoare
  4. Actually, I’m trying to make Ruby natural, not simple. Ruby is simple in appearance, but is very complex inside, just like our human body. – Matz, Ruby creator
  5. Much of the essence of building a program is in fact the debugging of the specification. – Fred Brooks, The Mythical Man-Month author
  6. The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. – Tom Cargill
  7. Complication is what happens when you try to solve a problem you don’t understand – Andy Boothe
  8. Weeks of programming can save you hours of planning. – Unknown
  9. Controlling complexity is the essence of computer programming. — Brian Kernighan
  10. All problems in computer science can be solved by another level of indirection(abstraction) – David Wheeler
  11. …except for the problem of too many layers of indirection. – Kevlin Henney’s corollary
  12. Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. — Rick Cook
  13. 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 W. Kernighan
  14. I’m not a great programmer; I’m just a good programmer with great habits. ― Kent Beck
  15. Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris. – Larry Wall, Perl creator
  16. Any fool can write code that a computer can understand. Good programmers write code that humans can understand. – Martin Fowler
  17. Measuring programming progress by lines of code is like measuring aircraft building progress by weight. – Bill Gates
  18. It’s not a bug – it’s an undocumented feature. – Unknown
  19. The most depressing thing about life as a programmer, I think, is if you’re faced with a chunk of code that either someone else wrote or, worse still, you wrote yourself but you no longer dare to modify. That’s depressing. – Peyton Jones
  20. It works on my machine! – Unknown
  21. Talk is cheap. Show me the code. – Linus Torvalds
  22. I thought of objects being like biological cells and/or individual computers on a network, only able to communicate with messages — Alan Kay, Smalltalk creator
  23. When you choose a language, you’re choosing more than a set of technical trade-offs—you’re choosing a community. -Joshua Bloch
  24. Quality, Speed or Cheap. Pick two. – Unknown
  25. Developer testing isn’t primarily about verifying code. It’s about making great code. If you can’t test something, it might be your testing skills failing you but it’s probably your code code’s design. Testable code is almost always better code. – Chad Fowler
  26. We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. – Donald Knuth

Do you have any recommendation in your mind?

 

QUOTE  SOFTWARE DESIGN 

       

  RELATED


  1 COMMENT


Luca [Reply]@ 2012-11-09 23:41:49
For the last few days I've been working on a proof-of-concept OpenGL C++ atolicapipn that loads a Blender model file (object data, lights, entities, etc) and renders it on-screen with some physics simulation included. The physics engine I use is Box2D with some modifications so that it works well with a scene manager I wrote to optimize complex scenes. I can get up to 30 or so bipeds before I start loosing a few FPS, but always remain up in the high 40s


  RANDOM FUN

How to write proper resume