Blog Posts and Other Media

How can we encourage less superficial code reviews?

You can't eliminate technical debt. Nor should you want to. But where does that leaev us?

Where does technical debt come from? Three main sources.

Save 80% on my popular course "Ship Better Code Faster"!

J. B. Rainsberger offers practical advice on how to "get over the hump" of evolutionary design, and really, how to learn any new skill.

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.

How do you know that the work you're doing is building on a valid premise?

Often the "obvious" answer blinds us to the "correct" answer.

The thing with agilists is they don't understand that sometimes we have deadlines.

The panel puts their heads together to talk about how to bring DevOps practices into a work situation based where they're not implemented. They discuss the various pro's and con's of specific practices and how to get people on board with adoption.

Smaller pull requests are faster to write and easier to review. Here are 4 tests to see if your PR might be too big.

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

Finger painting is an essential part of the Agile process.

Find the method that works for you, and don't let anyone guilt you into thinking your way is "wrong".

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

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

The panel jumps in and discusses the Minimum Viable Continuous Deployment from the manifesto on the web and discuss where they agree and disagree with the requirements listed there and clarify some of the ideas in the document.

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