Smaller software releases generally means fewer bugs, and bugs that are easier to fix. The number of bugs created typically increases with the complexity of interactions of code, which in turn increases with the size of release. This means that a number of smaller releases can hopefully get you to a large change in a safer way with less bugs, and less problematic bugs, created along the way than a single release with the whole lot. There’s probably a somewhat more general relationship with amount of unexpected problems created and the size of any change.

Bugs and releases

A term I’d always found intriguing, mostly because it’s such an unusual word. It’s a concept from mathematics and computer science but can be applied more generally—not that it often is. Basically, it’s an operation that, no matter how many times you do it, you’ll still get the same result, at least without doing other operations in between. A classic example would be view_your_bank_balance being idempotent, and withdraw_1000 not being idempotent.

HTs: @aidmcg and Ewan Silver who kept saying it

Sketchplanations tagged with coding