In this Q&A episode, guest co-host Amando Abreu and I answer listener questions about automatic rollback, how to prepare for an interview, and the meaning of life.

Which tools a team chooses are useful only if they help the team work toward cooperation and collaboration. Focus on these and tools will fall into place.

Code should have certain patterns and rythms that make it easy to read and understand.

Common break-even calculations for TDD are wrong when experienced TDD devs are involved becuase TDD makes development faster.

Taylorism has gotten a lot of flack for being inhumane at worst, and ineffective at best. But DevOps is about applying Taylorism to computer systems.

I was making really great progress at instilling a culture of quality until the pressure above from to "hire more people!"

Just about the last thing I really care about is someone's actual ability to code.

Joel Clermont, host of the No Compromises podcast, shares his wisdom on the topic of good digital hygiene, as it relates to development projects, particularly the bits that aren't software. Have you ever joined a team with poor documentation? With third-party credentials scattered all over the place?

It's easy to find examples of of books and conferences dedicated to "Agile." But Agile has never been the goal.

"Improving daily work is even more important than doing daily work." — Gene Kim

Why are new joiners often quick to offer unwanted advice on how to improve things? Many "newbies" can't distinguish between core skills and company-specific skills.