What's a counter example for "If it ain't broke, don't fix it"?

andarwaid@lemm.ee to Ask Lemmy@lemmy.world – 60 points –
34

You are viewing a single comment

Software

That's how you get into tech debt, stuck with entire infrastructure written in COBOL.

And even for purely UI changes, the UI totally impacts user adoption. Eg, a 90s style grey everything form is going to feel outdated to many users and they'll associate that with the rest of the software being dated (regardless of whether or not it's true). If your goal is adoption/sales, you often have to keep changing the UI even if it's not broke with regards to functionality.

Unless you’re an ERP software vendor. Wouldn’t want to put consultants out of the job.