RE: Backseat Software

Reading through Mike Swanson's article "Backseat Software" made me realize why I tend to gravitate to older platforms and software. Software used to be sold with the expectation that it would accomplish the goal you purchased it for. Now, software is all about keeping you engaged, on platform, etc so that you keep renewing your subscription (or even better, part with more money and data).

Mike writes "Great tools get out of the way so the user can accomplish their goal". I've been in enough companies where the goal is the opposite. You can't let the user just hop on, finish their task and hop off, think of the metrics! If a user's task is accomplished, they won't realize the value and might not renew!

Mike also writes "I don’t want to go back to floppy disks. I like fast updates. I like security patches. I like sync. I like crash reports when they help fix real issues", and to be honest, I disagree with this to a point. I'd love to go back to boxed software on a disc. If a company has to manufacture and distribute, they typically made sure the software was well tested to prevent the cost of reprinting discs. These days, it's a "ship first, fix later" mentality. Speed is all that matters to a modern software company. This mindset is even growing with the VCDLC (Vibe Code Development Life Cycle).

Just this morning I found my childhood copy of KidPix Deluxe on CD. I know that, if I had a computer from the era, inserting that disc would result in a full, functional experience. No failed license checks due to offline servers, no gigs of updates and no online account. Instead, KidPix would load and be fun just like it was when I played it.

I don't need new features. Software should be sold as is. While new features might come, what you purchased still accomplishes the goal you bought it for. When I run software on my Palm Pilot, it does exactly what it should. No tracking, no announcements, no updates. If a Palm Pilot app is buggy or lacking, you use an app from a different vendor. Quality was necessary to make sales.

When you buy a hammer, you expect to be able to hit nails. You don't need a manual, just a good nail to hit. Years later the manufacturer might introduce a new carbon fiber hammer with a larger head that hits nails with 30% more accuracy. Your old hammer won't get these features, but it continues to hit nails just fine. And sure, maybe the new hammer fixed a design flaw with the grip occasionally shifting. But again, you've learned to live with it and it hits nails. The hammer doesn't define your life or act as a status symbol. It's not engaging or addictive. It's a tool, and it hits nails.

Software should be like a hammer.