Comparing to another activity is useful if it helps you formulate questions, it's dangerous when you use it to justify answers.

Now I'm a pretty lazy person and am prepared to work quite hard in order to avoid work.

In almost all cases, I’m opposed to setting aside time for refactoring. In my view refactoring is not an activity you set aside time to do. Refactoring is something you do all the time in little bursts.

Comprehensiveness is the enemy of comprehensibility.

When to use iterative development? You should use iterative development only on projects that you want to succeed.

A pattern is an idea that has been useful in one practical context and will probably be useful in others.

If you're a technical lead, you need to be coding.