Best 218 quotes in «programming quotes» category

What's in your hands I think and hope is intelligence: the ability to see the machine as more than when you were first led up to it that you can make it more.

When I deal with smart IT programmers, I have a strong impression that their job has much in common with the phenomenon of how the Lord arranged the Universe and created genetics (cells, DNA, molecules, etc.). Both genetics and computer programming create their magic by performing highly intelligent coding work.

why bother with null and java 8 has optional

When you decide to put your business online it is a little bet tricky step for novice computer users because they want to keep data safe & secure. This problem developed from companies which did not take security seriously

Why was Simpson called "OJ" except in some kind of branding or headlinese that said, "Look, this guy is sweet, wholseome, and nourishing (and 'Orenthal' is just too fancy)? You can have him for breakfast." (And "Sweetness" and "Sweet" are nicknames often given to black men.) Is "OJ" that far away from Jell-O? Wasn't that extended advertising campaign a way of saying you can trust our pudding because Bill Cosby likes it—sweet, wholesome, and pretty?

With programmes such as flooding of emotions, the parts involved might not feel safe in turning the programme off. But you might be able to negotiate that they turn it down so it is barely noticeable. Or you could ask the spinner parts to spin in the opposite direction, so that they spin the effects back into the part who originally held those feelings rather than out to the rest of the system. Or you could insert a hidden drain and start draining out some of the feelings. Or you could find a way for the parts doing their jobs to implement the programme without doing harm. p126-127

Without requirements and design, programming is the art of adding bugs to an empty text file.

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.

You can program a computer to make mistakes, and you do it not by crossing wires, but by manipulating the 'language' you teach it to 'think' in.

A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable.

You haven't created a new body for me. I'm electricity, or light, or whatever bullshit you said I am. Just some complicated programming.

You should imagine variables as tentacles, rather than boxes. They do not contain values; they grasp them—two variables can refer to the same value.

About 90 percent of the downtime comes from, at most, 10 percent of the defects.

A class, in Java, is where we teach objects how to behave.

You can spread an ideology only by bombs. Either by real bombs or love bombs (manipulation).

Your limitations are largely programming instilled by others that you choose to believe.

Another trick in software is to avoid rewriting the software by using a piece that's already been written, so called component approach which the latest term for this in the most advanced form is what's called Object Oriented Programming.

After you finish the first 90% of a project, you have to finish the other 90%.

A good threat is worth a thousand tests.

All objects transmit their image to the eye in pyramids and the nearer to the eye these pyramids are intersected the smaller will the image appear of the objects which cause them.

All programming is maintenance programming, because you are rarely writing original code.

And C++ programming languages, we own those, have licensed them out multiple times, obviously. We have a lot of royalties coming to us from C++.

An API that isn't comprehensible isn't usable.

A primary cause of complexity is that software vendors uncritically adopt almost any feature that users want.

A security system is only as secure as its secret. Beware of pseudo-secrets.

As a programmer, it is your job to put yourself out of business. What you do today can be automated tomorrow.

BASIC is to computer programming as QWERTY is to typing.

As Mr. Nagle so competently points out, almost no one uses Eiffel; in fact until recently there were only 9 users. But now a 10th person just started, so we are holding a conference, appropriately titled the TENTH Eiffel USER conference, to celebrate.

A smart terminal is not a smartass terminal, but rather a terminal you can educate.

Complexity has nothing to do with intelligence, simplicity does.

Bugs lurk in corners and congregate at boundaries.

C is quirky, flawed, and an enormous success.

Copy and paste is a design error.

C++ tries to guard against Murphy, not Machiavelli.

Development is maintenance.

Ether is the only substance we are confident of in dynamics. One thing we are sure of and that is the reality and substantiality of the luminferous ether.

Eiffel borrows quite openly from several earlier programming languages and I am sure that if we had found a good language construct in C we would have used it as well.

Don't ask what it means, but rather how it is used.

Don't document bad code - rewrite it.

Experience shows that the success of a programming course critically depends on the choice of these examples.

Every good work of software starts by scratching a developers personal itch.

Every big computing disaster has come from taking too many ideas and putting them in one place.

Experience doesn't necessarily teach anything.

Go is no Erlang, Smalltalk or Scheme, nothing pure. But it works great and is fun!

Fancy algorithms are slow when N is small, and N is usually small.

Fancy optimizers have fancy bugs.

For many phenomena, 80% of consequences stem from 20% of the causes.

FORTRAN is not a flower but a weed - it is hardy, occasionally blooms, and grows in every computer.

Go isn't functional, it's pragmatical. Why pure paradigms like FP or OOP are always a must? (sigh)

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.