Quotes About Code

If I lived by some code, my actions would become predictable. The enemy would take advantage of this and I'd be killed. An honorable death doesn't exist. Death is death. But it's funny that survival and revenge require the same thing: no honor codes, no supposed higher principles to aspire to, no mercy

One hat, one hatter. - Millinery Code

Frank glanced at his wristwatch. "Sufferin' snakes! We're almost late for class!" With a roar of exhaust, the convertible headed for Bayport High School. Not until they returned home that afternoon were the Hardys able to resume work on the code message.

I use Mac. Not because it's more secure than everything else - because it is actually less secure than Windows - but I use it because it is still under the radar. People who write malicious code want the greatest return on their investment, so they target Windows systems. I still work with Windows in virtual machines.

The 9-9-9 plan would resuscitate this economy because it replaces the outdated tax code that allows politicians to pick winners and losers, and to provide favors in the form of tax breaks, special exemptions and loopholes. It simplifies the code dramatically: 9% business flat tax, 9% personal flat tax, 9% sales tax.

We need to lower tax rates for everybody, starting with the top corporate tax rate. We need to simplify the tax code. The ultimate answer, in my opinion, is the fair tax, which is a fair tax for everybody, because as long as we still have this messed-up tax code, the politicians are going to use it to reward winners and losers.

Content zips around the Internet thanks to code - programming code. And code is subject to intellectual property laws.

Think she'll stay on awhile?" Preacher quietly asked Jack. Jack was frowning. "I think what she does to a pair of jeans ought to be against the law." He looked at Preacher. "You okay here? I'm thinking of having a beer in Clear River." It was code. There was a woman in Clear River. "I'm okay here," Preacher said. *

In software, you don't want to release a huge chunk of code only to find out something's wrong with it. You release small bite-sized chunks so you can pick up problems quickly.

What have we here, laddie? Mysterious scribblings? A secret code? Oh, poems, no less! Poems, everybody!

Language is legislation, speech is its code. We do not see the power which is in speech because we forget that all speech is a classification, and that all classifications are oppressive.

During planning, especially short-term planning, it's tempting to set up "stretch goals" or to "encourage" the team to do "just one more feature." Please do not do this. It's devastatingly destructive. The reason is that the team will in fact try. Eager to please, they'll unconsciously hurry. They'll leave out just a few tests. They'll leave the code not quite as clean as they might have, just to squeeze in one more feature.

See this, Juice? Science comes from nature. It's kind of a branch of it. Like Jesus is a branch of God. And if we believe science is true, then we can act. And we'll be saved. Juicy stuck a bleeding finger in his mouth. Saved like, go to heaven? Holmes, that's some Santa Claus shit. ...No. Like the earth. The climate. The animals, said Jack. Heaven's part of the code. It just means, a good place for us all to live.

The tax code requires special training.

Crises is the code that can open the gene of success for some.

The DRY principle tells us to keep the low-level knowledge in the code, where it belongs, and reserve the comments for other, high-level explanations.

Before you start to look at the bug, make sure that you are working on code that built cleanly—without warnings. We routinely set compiler warning levels as high as possible. It doesn't make sense to waste time trying to find a problem that the computer could find for you! We need to concentrate on the harder problems at hand.

One broken window—a badly designed piece of code, a poor management decision that the team must live with for the duration of the project—is all it takes to start the decline. If you find yourself working on a project with quite a few broken windows, it's all too easy to slip into the mindset of All the rest of this code is crap, I'll just follow suit.

Two or more things are orthogonal if changes in one do not affect any of the others. In a well-designed system, the database code will be orthogonal to the user interface: you can change the interface without affecting the database, and swap databases without changing the interface.

we just don't have the time to go chasing after bugs that the automated tests could have found for us. We have to spend our time writing new code—and new bugs.

Prototyping is a learning experience. Its value lies not in the code produced, but in the lessons learned. That's really the point of prototyping.

Commenting source code gives you the perfect opportunity to document those elusive bits of a project that can't be documented anywhere else: engineering trade-offs, why decisions were made, what other alternatives were discarded, and so on.

As programmers, we collect, organize, maintain, and harness knowledge. We document knowledge in specifications, we make it come alive in running code, and we use it to provide the checks needed during testing.

Other than when dealing with exception-unsafe legacy code (which we'll discuss later in this Item), offering no exception safety guarantee should be an option only if your crack team of requirements analysts has identified a need for your application to leak resources and run with corrupt data structures. As