For many of us, code review is like eating broccoli: We know it's good for us, but we hate it. Here are my 10 tangible tips to improve the value of code reviews, and hopefully make them less distasteful.

J. B. Rainsberger joins me to talk about evolutionary design, and the barriers that keep many people from experiencing its benefits.

Can we get the benefits of WET and DRY at the same time?

Don't repeat yourself! Except when doing so might be harmful...

Are there times when performance is more important than readability? Yes. Should that be your starting point? Absolutely not!

What value is short, clever code that nobody understands? Readability should usually be the first priority in any technical artifact you write.

How do you decide between watching James Bond or a romantic comedy? Every decision optimizes for something. What do you optimize for when designing computing systems?

In the debate over the merits of BDUF vs emergant design, who's right? Both camps are right.

"Debugging is the act of answering questions and then answering them. Not: guessing what the answer is."

How do you use the scientific method in your daily work?

When test writing is removed from code writing, there's no observed benefit in IT performance. Writing tests in a silo is an anti-pattern.