Quotes About Code

I am very concerned about anything that says 'revenue' because let's just be honest; revenue for Democrats has become code for tax increases.

I'd think people would want me to follow the law and pay only what the tax code requires.

We need to even out the tax code for small businesses so that we lower their tax rate to 25 percent, just as we need to lower it for all businesses.

I firmly believe Americans are far better off under tax reform than they ever were sticking with this old, messed up, outdated tax code.

We all want a simpler code, but tax reform is about much more. It is about ensuring that everyone pays their fair share. The tax code is also used to promote behavior that we as a nation support, such as home ownership or charitable contributions.

Our tax code is arcane, burdensome and unwieldy. In the years since Ronald Reagan's 1986 Tax Reform Act, the code has gone from fewer than 30,000 pages to more than 70,000.

What I want to do is make certain that no one's taxes go up. Let's look at cleaning up the tax code.

The rationale for eliminating the alternative minimum tax is that such a backup system should not be necessary if the tax code is fundamentally fair and eliminates all the loopholes that made it possible for high-income taxpayers to escape taxation in the first place.

We shouldn't be debating whether to deal with the current code by allowing it to be extended or not. We should have a president who shows leadership and comes to Congress and says: 'You know what? We need to reform this whole tax code.'

Memes don't move: Signal-instigators do. This means the idea of a meme may be a meme, but the spoken word 'meme' is not itself a meme; it is a signal. A meme can only be a state of matter coded in 'brain language.

All flat-tax proposals benefit the rich more than the poor for one simple reason: today's tax code is still at least moderately progressive. The rich usually pay a higher percentage of their incomes in income taxes than do the poor. A flat tax would eliminate that slight progressivity.

You must question a code of ethics that never impedes your progress.

The true professional knows that delivering function at the expense of structure is a fool's errand. It is the structure of your code that allows it to be flexible. If you compromise the structure, you compromise the future.

Why don´t you fix bad code when you see it? Your first reaction upon seeing a messy function is ´This is a mess, it needs to be cleaned' . Your second reaction is ´I'm not touching it!´. Beacuse you know that if you touch it you risk breaking it; and if you break it; it becomes yours

But I can write my tests later", you say. No, you can't. Not really. Oh, you can write some tests later. You can even approach high coverage later if you are careful to measure it. But the tests you write after the fact are defense. Tests you write first are offense. After-the-fact tests are written by someone who is already vested in the code and already knows how the problem was solved. There's just no way those tests can be anywhere near as incisive as tests written first.

The proper use of comments is to compensate for our failure to express ourself in code. Note that I used the word failure. I meant it. Comments are always failures.

When you see commented-out code, delete it!

The first rule of functions is that they should be small. The second rule of functions is that they should be smaller than that.

Whatever else a TODO might be, it is not an excuse to leave bad code in the system.

First Law You may not write production code until you have written a failing unit test. Second Law You may not write more of a unit test than is sufficient to fail, and not compiling is failing. Third Law You may not write more production code than is sufficient to pass the currently failing test.

The unit tests are documents. They describe the lowest-level design of the system.

If we all checked-in our code a little cleaner than when we checked it out, the code simply could not rot.

Code, without tests, is not clean. No matter how elegant it is, no matter how readable and accessible, if it hath not tests, it be unclean. Dave

These comments are so noisy that we learn to ignore them. As we read through code, our eyes simply skip over them. Eventually the comments begin to lie as the code around them changes.