Articles & Blogs
Imagine a world where accountants told their stakeholders: "Accounts don’t need to be prefect, they only need to be good enough. Double entry bookkeeping is overkill." Silly right? In this article, Uncle Bob elaborates on the parallels between double entry accounting and test-driven development.
In this short parable, Arlo discusses the difference between "improving" and "safeguarding" using the metaphor of cutting your hand daily in the kitchen.
Sandi shares three different ideas to work with big monolithic structures and demonstrates how you can make small objects, and over time, the big ones will disappear.
There are all sorts of ways to define technical debt. In this article, Michael Feathers explains his rationale for his personal definition: Technical Debt is the refactoring effort needed to add a feature non-invasively. This article has been posted a BUNCH in the slack channel. Thanks, Tim Ottinger, Cory Wheeler, Brandon Dees, and of course, Michael Feathers for making sure we all saw it.
Matthew Carlson explores the striking similarities between refactoring and mathematic transformations through rules such as "The Associative Property" and "The Communicative Property". Thanks, Jay Bazuzi for sending this one in for us all to enjoy!
Have something you'd like to share? Post it in our Slack channel
There are a lot of teams out there saying they practice agile software development, when in reality they’ve just broken up their waterfall roadmap into two-week sprints (often called agilefall). This can lead to executives in government thinking “well, we tried agile and it didn’t help at all.” When you get to that point, what do you do?
What happens when you run a mob programming session with 35 people? Jay shares his experience from a recent "mega mobbing" session.