Software is like surgery

May 2, 2021
Software, like surgery, should be a last resort, when all other options have been exhausted.

Those of us who work on teams that produce software somewhat naturally think of our software or our code as an asset. Afterall, it is the thing we’re producing, right? When you hire a homebuilder to build you a home, that home becomes an asset.

Sadly, that’s not how software works. Nobody wants software. We make software to serve some other purpose. The software itself is a liability. It’s expensive to create, it’s complicated to maintain, and it’s risky to change.

Software is more like surgery.

Nobody ever says “I want lots of surgery! Give me as much surgery as possible as quickly as possible.”

Rather, surgery is considered a last resort, when all other safer, cheaper, fastr options have been exhausted. And then you want the least amount of it possible to achieve your goal.

Share this

Related Content

What is the ROI of Test-Driven Development?

Common break-even calculations for TDD are wrong when experienced TDD devs are involved becuase TDD makes development faster.

A merge a day keeps the conflicts away

Merge a minimum of one PR each day. Make small PRs. Don't worry if the feature is incomplete, only that each PR works.

Real "senior devs" don't fix bugs in production

A good developer will reproduce a bug in a test environment, fix it there, then deploy to production.