Top 40 Programming Code Quotes
#1. Content zips around the Internet thanks to code - programming code. And code is subject to intellectual property laws.
Jonathan Zittrain
#2. One IT executive in an investment banking company claimed that 80 percent of his company's programming code was dedicated to linking disparate systems, as opposed to creating new capabilities.
Jeanne W. Ross
#3. Sometimes abstraction and encapsulation are at odds with performance - although not nearly as often as many developers believe - but it is always a good practice first to make your code right, and then make it fast.
Brian Goetz
#4. One of her secret fantasies had been that, as a girl who could code, she would work in the one place where a geeky fat girl could get dates. It had not been entirely untrue. But as someone had pointed out to her in school, although the odds are good, the goods are odd.
Maureen F. McHugh
#5. But while you can always write 'spaghetti code' in a procedural language, object-oriented languages used poorly can add meatballs to your spaghetti.
Andrew Hunt
#6. How can we make sure we wind up behind the right door when the going gets tough? The answer is: craftsmanship.
Robert C. Martin
#7. Are you quite sure that all those bells and whistles, all those wonderful facilities of your so called powerful programming languages, belong to the solution set rather than the problem set?
Edsger Dijkstra
#8. Think like a fundamentalist, code like a hacker.
Erik Meijer
#9. All programming is maintenance programming, because you are rarely writing original code.
Dave Thomas
#10. Progress is possible only if we train ourselves to think about programs without thinking of them as pieces of executable code.
Edsger W. Dijkstra
#11. Object-oriented programming offers a sustainable way to write spaghetti code. It lets you accrete programs as a series of patches.
Paul Graham
#12. Programming in machine code is like eating with a toothpick
Charles Petzold
#13. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.
Eric S. Raymond
#14. First solve the problem. Then, write the code.
Waseem Latif
#17. At forty, I was too old to work as a programmer myself anymore; writing code is a young person's job.
Michael Crichton
#18. Learning a language is not interesting than knowing how it works.
Ritesh Shrivastav
#19. So if you want to go fast, if you want to get done quickly, if you want your code to be easy to write, make it easy to read.
Robert C. Martin
#20. The value of a prototype is in the education it gives you, not in the code itself.
Amari Cooper
#21. Learning to code makes kids feel empowered, creative, and confident. If we want our young women to retain these traits into adulthood, a great option is to expose them to computer programming in their youth.
Susan Wojcicki
#22. Code without tests is bad code. It doesn't matter how well written it is; it doesn't matter how pretty or object-oriented or well-encapsulated it is. With tests, we can change the behavior of our code quickly and verifiably. Without them, we really don't know if our code is getting better or worse.
Michael C. Feathers
#23. If the discipline of requirements specification has taught us anything, it is that well-specified requirements are as formal as code and can act as executable tests of that code!
Robert C. Martin
#24. Measuring programming progress by lines of code is like measuring aircraft building progress by weight.
Bill Gates
#25. A great lathe operator commands several times the wage of an average lathe operator, but a great writer of software code is worth 10,000 times the price of an average software writer.
Bill Gates
#26. The real hero of programming is the one who writes negative code,
Douglas McIlroy
#27. Redundant comments are just places to collect lies and misinformation.
Robert C. Martin
#29. ...I'm not saying simple code takes less time to write. You'd think it would since you end up with less total code, but a good solution isn't an accretion of code, it's a distillation of it.
Robert Nystrom
#30. Indeed, the ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. ...[Therefore,] making it easy to read makes it easier to write.
Robert C. Martin
#31. The ALGOL compiler was probably one of the nicest pieces of code to come out at that time. I spent hours trying to fix and change the compiler. Working with it so closely affected the way I think about programming and had a profound influence on my style.
Gary Kildall
#32. Last week I was listening to a podcast on Hanselminutes, with Robert Martin talking about the SOLID principles ... they all sounded to me like extremely bureaucratic programming that came from the mind of somebody that has not written a lot of code, frankly.
Joel Spolsky
#33. It also makes the program more difficult to change because prose tends to be more tightly interconnected than code. This style is called literate programming. The
Marijn Haverbeke
#35. Don't gloss over a routine or piece of code involved in the bug because you "know" it works. Prove it. Prove it in this context, with this data, with these boundary conditions.
Andrew Hunt
#36. In William Shakespeare's Hamlet, "to be, or not to be, that is the question." In the 21st century, "to code, or not to code, that is the challenge.
Newton Lee
#37. As an Agile software development team, we'd been following the hallowed eXtreme Programming tenets, including YAGNI. That is, You Aren't Gonna Need It: a caution to not write unnecessary code -
Anonymous
#38. Writing code is not production, it's not always craftsmanship though it can be, it's design.
Joel Spolsky
#39. In the happy land of elegant code and pretty rainbows, there lives a spoil-sport monster called inefficiency.
Marijn Haverbeke
#40. Her assignment had been to write a simple Sumerian code for preserving a jar of pickled eggs. (To the programming-inclined reader, this is the magical equivalent of "HELLO WORLD.")
Sorin Suciu
Famous Authors
Popular Topics
Scroll to Top
