Embrace instability

We loathe downtime and failing services. We talk about how we can keep our code stable. How we can avoid instability. However, certain types of instability should be embraced.

Write your own code

Writing code is easy. Dealing with the the wrong dependencies down the line is hard, and can cost hundreds or thousands of hours to clean up when you suddenly need to. Spend time actively managing your dependencies - for any lasting software, this'll save both time, risk and money in the long run.

The cost of not deleting code

Through the years, I've stumbled across thousands of lines of unused code of all kinds. It might have been nice, well tested, neatly architected code fitting perfectly into all the tools, frameworks and standards for its time. But in the end, it was never called.