Quotes About Code

Rutherford arches his neck toward her outstretched hand. Freckles of light float across his patchy hindquarters. He licks the girl's palm according to a code that he's worked out: - - - -, which means that he is Rutherford Birchard Hayes, the nineteenth president of the United States of America, and that she should alert the local officials. "Ha-ha!" the girl laughs. "That tickles.

He'd once explained that when he was a boy his very proper parents had forbidden him and his brothers to curse in the house so 'feather buckets' was the young boys coded way of saying 'f*ck it

If you don't measure the performance, you're just guessing, and if you're guessing, you're not very likely to write top-notch code.

Compact code was inherently good since it consumed less internal memory. Consisting of slivers of silicon chips called DRAM ("dynamic-random-access-memories"), internal memory was like a gas tank. The larger the tank, the farther the car would go. The smaller the operating program, the more gas was left for all other programs. Because

Often pieces of the kernel called a bedrock layer of code, the "microkernel," which was the ultimate chief of staff within NT.

Bugs were the backdrop of the code writer's life. A comma in the wrong place. An "if" where there should be a "then." An erroneous call from one piece of the program to another. Each could instantly cause a seizure, the collapse of a finely wrought abstraction into a puddle of ones and zeroes. Only human, software was born to fail. If not catastrophically, then aesthetically. Every software captain knew this.

The best testers were masters at deducing the chain of events leading to a failure. They provided code writers with a virtual road map to fix their bug. The worst testers offered little more than a description of the hangup and a half-baked hypothesis of the cause. Manheim

Code writing was a solitary pursuit, but designing and fitting together diverse pieces demanded cooperation and compromise.

The best testers were masters at deducing the chain of events leading to a failure. They provided code writers with a virtual road map to fix their bug.

A computer is a merciless critic," Joseph Weizenbaum, a pioneering computer scientist, has observed. Designers are ranked by peers, but code writers ultimately are measured by a machine. The

He knew what he was experiencing was a basic error in programming, and he wished he could open up his brain and delete the bad code. Unfortunately, the human brain is every bit as closed a system as a Mac.

Sam knew the foot was gone. He could see it was gone. He knew what he was experiencing was a basic error in programming, and he wished he could open up his brain and delete the bad code. Unfortunately, the human brain is every bit as closed a system as a Mac.

One's nature comes from within, not from without. The abomination occurs in subverting one's instinct in favor of a rigid code written by others. Trying to force yourself into a role that confounds your spirit will always break you.

One's nature comes from within, not from without. The abomination occurs in subverting one's instinct in favor of a rigid code written by others. Trying to force yourself into a role that confounds your spirit will always break you." I

There's a code of honor in sports, Guerin believed. You do not deliberately embarrass your opponent or set records outside the normal flow of the game. The Warriors were breaking a code.

However, we do not recommend relying too heavily on volatile variables for visibility; code that relies on volatile variables for visibility of arbitrary state is more fragile and harder to understand than code that uses locking.

There will be times when good object-oriented design techniques are at odds with real-world requirements; it may be necessary in these cases to compromise the rules of good design for the sake of performance or for the sake of backward compatibility with legacy code. 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.

A synchronized block has two parts: a reference to an object that will serve as the lock, and a block of code to be guarded by that lock.

Don't comment bad code—rewrite it.

int i = inputStream.read(readData); while (i != -1) { outputStream.write(readData, 0, i);

One of the blessings of Notre Dame is where it's at. It's in the middle of nowhere, but you become part of the community. It's a lifestyle, and it has a code, and that code teaches young men and women responsibility and leadership.

If, for example, all the codons are triplets, then in addition to the correct reading of the message, there are two incorrect readings which we shall obtain if we do not start the grouping into sets of three at the right place.

It would appear that the number of nonsense triplets is rather low, since we only occasionally come across them. However this conclusion is less secure than our other deductions about the general nature of the genetic code.

In the face of entropy and nothingness, you kind of have to pretend it's not there if you want to keep writing good code.