Quotes About Development

The trouble with learning to parent on the job is that your child is the teacher.

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

In the time it takes you to understand a 14-year-old, they turn 15.

We are each a dozen people who were all the same child.

Each day learn something new, and just as important, relearn something old.

A watched child never learns.

Making a different mistake every day is not only acceptable, it is the definition of progress.

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

Parenting is a stage of life's journey where the milestones come about every fifty feet.

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

There is a strong chance that siblings who turn out well were hassled by the same parents.

You start making progress in life when you realize that you don't always have to resume where you left off.

The Lord gives us friends to push us to our potential — and enemies to push us beyond it.

Empty the pond to get the fish.

What? Was man made a wheel-work to wind up, And be discharged, and straight wound up anew? No! grown, his growth lasts; taught, he ne'er forgets: May learn a thousand things, not twice the same.

The only fault's with time; All men become good creatures: but so slow!

Over the past century and a half, we've gone from harnessing animals—and enduring all the shit they shat—to harnessing the subatomic motion of electrons.

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

But maybe you shouldn't wonder so much about his secret, he says. What's really important is finding your secret - something that becomes like a seed inside you - that will grow as you grow up.

Every obstacle is a gift, every problem is an opportunity for growth.

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

You should plan on working 60 hours per week. The first 40 are for your employer. The remaining 20 are for you. During this remaining 20 hours you should be reading, practicing, learning and otherwise enhancing your career.

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.