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

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

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.

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

When you actually sit down to write some code, you learn things that you didn't get from thinking about them in modeling terms...there is a feedback process there that you can only really get at from executing some things and seeing what works

One of the things I've been trying to do is look for simpler or rules underpinning good or bad design. I think one of the most valuable rules is avoid duplication. "Once and only once" is the Extreme Programming phrase.

I can't choose whether someone is offended by my actions. I can choose whether I care.