Quotes About Improvement

We are born, we grow up, we live our lives as best we can. If we are thoughtful we are good parents and good partners. If we are wise we strive for integrity and intimacy. If we are fortunate we discover love and joy. If we are able, we make the world a little better than we found it. That is all there is for any of us.

Leave this world a little better than you found it.

A direct relationship exists between the caliber of the writing you read and the caliber of the writing you make.

The law of change says, "Things do not stay the same. If they don't get better, they get worse." If relationships do not get stronger, they will get weaker; if they do not become closer, they will become more distant; if they do not become more productive, they will become less productive.

How often in life we complete a task that was beyond the capability of the person we were when we started it.

Learning is a lifetime process, but there comes a time when we must stop adding and start updating.

Either way, things are a lot better — either a lot better than they were or a lot better than they're going to be.

So, take, and use thy work: Amend what flaws may lurk, What strain o' the stuff, what warpings past the aim! My times be in thy hand! Perfect the cup as planned! Let age approve of youth, and death complete the same!

Using the official $1 per day line, we estimate that [from 1970 to 2006] world poverty rates have fallen by 80 percent.

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

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

It is not enough for code to work. Code that works is often badly broken. Programmers who satisfy themselves with merely working code are behaving unprofessionally. They may fear that they don't have time to improve the structure and design of their code, but I disagree. Nothing has a more profound and long-term degrading effect upon a development project than bad code.

Learning to write clean code is hard work. It requires more than just the knowledge of principles and patterns. You must sweat over it. You must practice it yourself, and watch yourself fail. You must watch others practice it and fail. You must see them stumble and retrace their steps. You must see them agonize over decisions and see the price they pay for making those decisions the wrong way.

Duplication and expressiveness take me a very long way into what I consider clean code, and improving dirty code with just these two things in mind can make a huge difference. There is, however, one other thing that I'm aware of doing, which is a bit harder to explain.

To write clean code, you must first write dirty code and then clean it.

One of the best ways to ruin a program is to make massive changes to its structure in the name of improvement. Some programs never recover from such "improvements." The problem is that it's very hard to get the program working the same way it worked before the "improvement.

refactored)    /**

Don't comment bad code—rewrite it." —Brian W. Kernighan and P. J. Plaugher1

You are reading this book for two reasons. First, you are a programmer. Second, you want to be a better programmer. Good. We need better programmers.

all winter, far into the night, we read books and we practised writing. 20.

Daily Law: No calling is superior to another. What matters is that it be tied to a personal need and inclination, and that your energy moves you toward improvement and continuous learning from experience. The Laws of Human Nature, 13: Advance with a Sense of Purpose—The Law of Aimlessness

One thing I designed, I've done a lot of work on improving kosher slaughter. They need to make a head holding device that would go on the end of the conveyer. A normal kosher head holding device, the thing is like a cradle that lifts up the head. If I have it on the end of a conveyer, how do I make this work?

This means that you move toward challenges that will toughen and improve you, where you will get the most objective feedback on your performance and progress. You do not choose apprenticeships that seem easy and comfortable.

So I'd gotten rid of that negativity and I'd show, "Well, here's something done right. Here's the mistake, but here's how to fix the mistake.