For Want Of a Unit Test
I read something in Sahil Bloom's Curiosity Chronicle. Great newsletter - check it out if you haven't yet. Here's my referral link.
As Sahil writes,
"For want of a nail, the shoe was lost.For want of a shoe, the horse was lost.For want of a horse, the rider was lost.For want of a rider, the battle was lost.
For want of a battle, the kingdom was lost.
All for the want of a horseshoe nail.A powerful reminder of an important truth: Small things become big things.
Your entire life will change when you realize that everything matters.
You don't get to pick and choose when to show up, because the world will ignore your best and judge you for your worst.
The tiny thing you choose to ignore—the thing you convince yourself doesn’t matter—it may be the nail that destroys your kingdom."
Made me think of my own little version:
For want of a fast MVP, the unit test was skipped.
For want of a unit test, the bug was "lost".
For having a bug, the customer was lost.
For want of a customer, the revenue was lost.
For want of revenue, the company was lost.
All for the want of a fast MVP.
Unit tests and code-reviewed pull requests, with protected branches, are tools you might want to get really strict about. Just sayin'.
Are you allowing a missing unit test to destroy the company?
