Ron Jeffries quotes:

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

Code never lies, comments sometimes do.

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

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

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.

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

Simple, not easy. There's a difference.

The wages of sin is debugging.

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!!