I am.

Every milestone starts with a single.. In terms of programming it can be said “Every Program starts with one single line of code”

So before we start lets see what the world has to QUOTES about programming..

  1. The eyes are useless when the mind is blind.
  2. The scariest moment is always just before you start.
  3. This is the web. Fix it.
  4. Designing with watermarked photos is like baking with fake sugar.
  5. Design is redesign.
  6. Write drunk; edit sober.
  7. The nature of space reflects what it wants to be.
  8. Just because nobody complains doesn’t mean all parachutes are perfect.
  9. Don’t worry about people stealing an idea. If it’s original, you will have to ram it down their throats.
  10. Stop. I’m not going to take any more input until I’ve made something with what I got.
  11. There is no excellent beauty that hath not some strangeness in the proportion.
  12. Owning a camera doesn’t make you a photographer.
  13. Think more, design less.
  14. Never let your clients see you drive a more expensive car than they drive.
  15. Art does not reproduce what we see; rather, it makes us see.
  16. A well-defined problem is half solved.
  17. Remember to always be yourself. Unless you suck.
  18. I’ve been imitated so well I’ve heard people copy my mistakes.
  19. There’s big money in studying art … if you own the school.
  20. Bad design is smoke, while good design is a mirror.
  21. Great things are not accomplished by those who yield to trends and fads and popular opinion.
  22. Inspiration the seed. Design but the flower.
  23. Simplicity is the ultimate sophistication.
  24. Never re-invent the wheel, unless you’re sure the client needn’t go anywhere.
  25. Money is usually attracted, not pursued.
  26. A goal is a dream with a deadline.
  27. It’s not what you look at that matters, it’s what you see.
  28. Delay always breeds danger; and to protract a great design is often to ruin it.
  29. Do, or do not. There is no “try”.
  30. Every great design begins with an even better story.
  31. To push the boundaries, you need to know where the edges are.
  32. Creativity isn’t worth a thing if it isn’t served with an equal amount of reliability.
  33. … try to absorb what is useful, discard what is useless, and add what is essentially your own.
  34. Now that we can do anything, what should we do?
  35. Everything that can be said, can be said clearly.
  36. It’s the little details that are vital. Little things make big things happen.
  37. If design isn’t profitable, then it’s art.
  38. Everyone gets so much information all day long that they lose their common sense.
  39. The majority of iteration should be done in the privacy of your own head.
  40. If debugging is the process of removing software bugs, then programming must be the process of putting them in.
  41. The best method for accelerating a computer is the one that boosts it by 9.8 m/s2.
  42. Walking on water and developing software from a specification are easy if both are frozen.
  43. First, solve the problem. Then, write the code.
  44. Should array indices start at 0 or 1? My compromise of 0.5 was rejected without, I thought, proper consideration.
  45. Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
  46. Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
  47. Software sucks because users demand it to.
  48. Linux is only free if your time has no value.
  49. Beware of bugs in the above code; I have only proved it correct, not tried it.
  50. Programs must be written for people to read, and only incidentally for machines to execute.
  51. Programming can be fun, so can cryptography; however they should not be combined.
  52. Copy and paste is a design error.
  53. Before software can be reusable it first has to be usable.
  54. Without requirements or design, programming is the art of adding bugs to an empty text file.
  55. When someone says, “I want a programming language in which I need only say what I want done,” give him a lollipop.
  56. Computers are good at following instructions, but not at reading your mind.
  57. Any code of your own that you haven’t looked at for six or more months might as well have been written by someone else.
  58. That’s the thing about people who think they hate computers. What they really hate is lousy programmers.
  59. Talk is cheap. Show me the code.
  60. To create great work, here’s how you must spend your time:
    1% Inspiration
    9% Perspiration
    90% Justification
  61. A customer is the most important visitor on our premises.
    He is not dependent on us. We are dependent on him.
    He is not an interruption of our work. He is the purpose of it.
    He is not an outsider to our business. He is part of it.
    We are not doing him a favour by serving him.
    He is doing us a favour by giving us the opportunity to do so.
  62. A designer, like an archaeologist or geologist; researches, uncovers and adds context to precious, overlooked treasures by digging deep beneath the surface.
  63. Design is the fundamental soul of a human-made creation that ends up expressing itself in successive outer layers of the product or service.
  64. I don’t care if you’re a billionaire. If you haven’t started a company, really gambled your resume and your money and maybe even your marriage to just go crazy and try something on your own, you’re no pirate and you aren’t in the club.
  65. Those who say “it’s not personal, it’s just business” are lying. All business is personal, and the best business is very personal.
  66. The difference between an artist and a graphic designer. One says “it’s finished when I feel it’s finished” the other says “I will have this by the 30th.”
  67. If you never venture outside the box, you will probably not be creative. But if you never get inside the box, you will certainly be stupid.
  68. The second best friend you can have (the first being someone who can give you a good job) is another designer or illustrator.
  69. Like McDonalds proves, popular doesn’t necessarily mean good. I’m not particularly interested in what’s popular; I’m much more interested in what’s good.
  70. When I am working on a problem, I never think about beauty. I only think about how to solve the problem. But when I have finished, if the solution isn’t beautiful, I know it is wrong.
  71. Never fall in love with an idea. They’re whores. If the one you’re with isn’t doing the job, there’s always, always, always another.
  72. It’s hard enough to find an error in your code when you’re looking for it; it’s even harder when you’ve assumed your code is error-free.
  73. Rules of Optimization:
    Rule 1: Don’t do it.
    Rule 2 (for experts only): Don’t do it yet.
  74. 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.
  75. There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code.
  76. 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.
  77. Good code is its own best documentation. As you’re about to add a comment, ask yourself, “How can I improve the code so that this comment isn’t needed?” Improve the code and then document it to make it even clearer.
  78. Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves.
  79. when you don’t create things, you become defined by your tastes rather than ability. your tastes only narrow & exclude people. so create.
  80. Everyone in the world was programmed by the place they were born, hemmed in by their beliefs, but you had to at least try to grow your own brain.
  81. Well, Mr. Frankel, who started this program, began to suffer from the computer disease that anybody who works with computers now knows about. It’s a very serious disease and it interferes completely with the work. The trouble with computers is you *play* with them. They are so wonderful. You have these switches – if it’s an even number you do this, if it’s an odd number you do that – and pretty soon you can do more and more elaborate things if you are clever enough, on one machine.

    After a while the whole system broke down. Frankel wasn’t paying any attention; he wasn’t supervising anybody. The system was going very, very slowly – while he was sitting in a room figuring out how to make one tabulator automatically print arc-tangent X, and then it would start and it would print columns and then bitsi, bitsi, bitsi, and calculate the arc-tangent automatically by integrating as it went along and make a whole table in one operation.

    Absolutely useless. We *had* tables of arc-tangents. But if you’ve ever worked with computers, you understand the disease – the *delight* in being able to see how much you can do. But he got the disease for the first time, the poor fellow who invented the thing.

  82. 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.
  83. The best programs are written so that computing machines can perform them quickly and so that human beings can understand them clearly. A programmer is ideally an essayist who works with traditional aesthetic and literary forms as well as mathematical concepts, to communicate the way that an algorithm works and to convince a reader that the results will be correct.
  84. On two occasions, I have been asked [by members of Parliament], ‘Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?’ I am not able to rightly apprehend the kind of confusion of ideas that could provoke such a question.
  85. When they first built the University of California at Irvine they just put the buildings in. They did not put any sidewalks, they just planted grass. The next year, they came back and put the sidewalks where the trails were in the grass. Perl is just that kind of language. It is not designed from first principles. Perl is those sidewalks in the grass.
  86. Big Brother fills us all with the same crap. My guess is he was clever the same way everybody thinks they’re clever. I tell her to type in ‘password’
  87. Object-oriented programming offers a sustainable way to write spaghetti code. It lets you accrete programs as a series of patches.
  88. Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live
  89. Perl – The only language that looks the same before and after RSA encryption.
  90. At forty, I was too old to work as a programmer myself anymore; writing code is a young person’s job.
  91. The computer programmer is a creator of universes for which he alone is the lawgiver. No playwright, no stage director, no emperor, however powerful, has ever exercised such absolute authority to arrange a stage or field of battle and to command such unswervingly dutiful actors or troops.
  92. A language that doesn’t affect the way you think about programming is not worth knowing.
  93. The most disastrous thing that you can ever learn is your first programming language.
  94. Every program has (at least) two purposes: the one for which it was written and another for which it wasn’t.
  95. I think that it’s extraordinarily important that we in computer science keep fun in computing. When it started out it was an awful lot of fun. Of course the paying customers got shafted every now and then and after a while we began to take their complaints seriously. We began to feel as if we really were responsible for the successful error-free perfect use of these machines. I don’t think we are. I think we’re responsible for stretching them setting them off in new directions and keeping fun in the house. I hope the ?eld of computer science never loses its sense of fun. Above all I hope we don’t become missionaries. Don’t feel as if you’re Bible sales-men. The world has too many of those already. What you know about computing other people will learn. Don’t feel as if the key to successful computing is only in your hands. What’s in your hands I think and hope is intelligence: the ability to see the machine as more than when you were ?rst led up to it that you can make it more.
  96. We see a lot of feature-driven product design in which the cost of features is not properly accounted. Features can have a negative value to customers because they make the products more difficult to understand and use. We are finding that people like products that just work. It turns out that designs that just work are much harder to produce that designs that assemble long lists of features.
  97. The most important property of a program is whether it accomplishes the intention of its user.
  98. Programming went back to the beginning of time. It was a little like the midden out back of his father’s castle.
  99. A computer is like a violin. You can imagine a novice trying ?rst a phonograph and then a violin. The latter, he says, sounds terrible. That is the argument we have heard from our humanists and most of our computer scientists. Computer programs are good, they say, for particular purposes, but they aren’t ?exible. Neither is a violin, or a typewriter, until you learn how to use it.