Code Review —1 min read
When is a pull request too big?

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

Coding Practices —41 min episode
Tiny DevOps episode #19 J. B. Rainsberger — Mastering Evolutionary Design, Part 1

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

Agile Principles —1 min read
The importance of finger painting

Finger painting is an essential part of the Agile process.

Code Review —2 min read
The one code review method to rule them all

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

Coding Practices —1 min read
Staying DRY in a WET codebase

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

Coding Practices —1 min read
DRY can be expensive

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

Software Delivery —65 min listen
Adventures In DevOps 093: Deconstructing the Minimum Viable Continuous Deployment

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.

Coding Practices —1 min read
Readability vs performance

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

Coding Practices —2 min read
Readability is paramount

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

Agile Principles —47 min episode
Tiny DevOps episode #18 Steve Pereira — The value of value flow mapping

Steve Pereira describes the concept of value stream mapping, and how it, and related techniques, can be used to improve the flow of practically any process from product ideation to delivery and customer experience. Steve is the founder of Visible, and is obsessed with making tech human, and leveraging it to deliver continuous value.

Teams & Culture —1 min read
Engineering is like high school

After we find land a first job we learn that correct answers often often technically inferior solutions, answers, or proposals win the day. Why?