When we use a language, we should commit ourselves to knowing it, being able to read it, and writing it idiomatically.

Code never lies, comments sometimes do.

If there's only one answer, then this must not be a very interesting topic.

Three bloody roles, Scrum has, and only three. If you can’t get that right, don’t call it Scrum, OK?

The wages of sin is debugging.

Simple, not easy. There's a difference.

The lesson is: Even if you know exactly what is going on in you system, measure performance, don't speculate. You'll learn something, and nine times out of ten, it won't be that you were right!!

It seems to me to be important to distinguish a good idea from poor implementations of it

One of the great skills in using any language is knowing what not to use, what not to say. There's that simplicity thing again.

Be a poet in action as well as in words.

The earliest bird gets the worm only if the worm is stupid enough to show up.

You boys going to get somewhere, or just going?" We didn't understand his question, and it was a damned good question.

For every thinking and reflecting man the existence of evil is a riddle he cannot escape.

No one can be happy in eternal solitude.

It's not so much a thankless task, it's more a job with no thanks

I apologize to the public, whom I promised better.

I've gotten pretty good at leaving characters on the set. I go home and try to relax and regroup and be ready for the next day.

The thought of being President frightens me and I do not think I want the job.

It's pretty much the same; it's just that Phil was very weird with his system. This is more of the traditional system.