'Martyrdom' is the only way a person can become famous without ability.
--George Bernard Shaw
Progress is possible only if we train ourselves to think about programs without thinking of them as pieces of executable code.
--Edsger W. Dijkstra
How do you expect to succeed if you do not know the rules?
--Anonymous
Learn the rules like a pro, so you can break them like an artist
--Pablo Picasso
Not only is this incomprehensible, but the ink is ugly and the paper is from the wrong kind of tree.
--Professor W.
There ain't no rules around here. We are trying to accomplish something.
--Thomas Edison
The big optimizations come from refining the high-level design, not the individual routines.
--Steve McConnell
Happiness should be a function without any parameters.
--Pranshu Midha
A language that doesn't affect the way you think about programming is not worth knowing.
--Unix Fortune
What kind of programmer is so divorced from reality that she thinks she'll get complex software right the first time?
--James Alan Gardner
[On identifying talented programmers] It’s just enthusiasm. You ask them what’s the most interesting program they worked on. And then you get them to describe it and its algorithms and what’s going on. If they can’t withstand my questioning on their program, then they’re not good. I’m asking them to describe something they’ve done that they’ve spent blood on. I’ve never met anybody who really did spend blood on something who wasn’t eager to describe what they’ve done and how they did it and why. I let them pick the subject. I don’t pick the subject, so I’m the amateur and they’re the professional in this subject. If they can’t stand an amateur asking them questions about their profession, then they don’t belong.
--Ken Thompson
The really good programmers spend a lot of time programming. I haven’t seen very good programmers who don’t spend a lot of time programming. If I don’t program for two or three days, I need to do it. And you get better at it—you get quicker at it. The side effect of writing all this other stuff is that when you get to doing ordinary problems, you can do them very quickly.
--Joe Armstrong
The three principal virtues of a programmer are Laziness, Impatience, and Hubris. See the Camel Book for why.
--perldoc perl
The most difficult thing in the world is to know how to do a thing and to watch someone else do it wrong without comment.
--Theodore H. White
I'm a programmer. I like programming. And the best way I've found to have a positive impact on code is to write it.
--Robert C. Martin
Learning the art of programming, like most other disciplines, consists of first learning the rules and then learning when to break them.
--Joshua Bloch
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live
--John Woods
First solve the problem. Then, write the code.
--Waseem Latif
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
--Nartin Fowler
People who are really serious about software should make their own hardware
--Alan Kay
With software there are only two possibilites: either the users control the programme or the programme controls the users. If the programme controls the users, and the developer controls the programme, then the programme is an instrument of unjust power.
--Richard Stallman
The most important property of a program is whether it accomplishes the intention of its user.
--C.A.R. Hoare
You are not reading this book because a teacher assigned it to you, you are reading it because you have a desire to learn, and wanting to learn is the biggest advantage you can have.
--Cory Althoff
Good programmers write code that humans can understand.
--Martin Fowler
Delivering good software today is often better than perfect software tomorrow, so finish things and ship.
--David Thomas
Know the rules well, so you can break them effectively
--Dalai Lama XIV
Managers of programming projects aren’t always aware that certain programming issues are matters of religion. If you’re a manager and you try to require compliance with certain programming practices, you’re inviting your programmers’ ire. Here’s a list of religious issues:
■ Programming language
■ Indentation style
■ Placing of braces
■ Choice of IDE
■ Commenting style
■ Efficiency vs. readability tradeoffs
■ Choice of methodology—for example, Scrum vs. Extreme Programming vs. evolutionary delivery ■ Programming utilities
■ Naming conventions
■ Use of gotos
■ Use of global variables
■ Measurements, especially productivity measures such as lines of code per day
--Steve McConnell
|