Technology

hideshow 7 child comments

[–] buzz@piefed.world 13 points 1 day ago (4 children)

If it ain’t broke, don’t fix it.

hideshow 4 child comments

parent

[–] ExcessShiv@lemmy.dbzer0.com 2 points 1 day ago (3 children)

That kind of bullshit thinking is why I have to do shitty half-assed solutions because I need to work around unsupported equipment that's 50 years old and was EOL'ed three decades ago. At some point you absolutely should upgrade even if it isn't broken.

hideshow 3 child comments

parent

[–] Taldan@lemmy.world 2 points 23 hours ago

The absolute #1 priority in aviation is safety. Old, stable systems are safer. Just add new systems in parallel for new features

parent

[–] buzz@piefed.world 1 point 11 hours ago

I agree it’s often misapplied.

parent

[–] 3laws@lemmy.world 1 point 23 hours ago*

It fact you just gave us the true answer.

If it ain't broke don't fix it, so now when it breaks it can't be fixed.

parent

[–] cdnk5@piefed.ca 5 points 1 day ago (1 child)

Lol I use software every day that was written in COBOL. It would cost billions to replace. So leadership never wants to add that expense to their budget so they just hobble along and leave it for the next people.

parent

hideshow 1 child comment

[–] walden@wetshav.ing 1 point 1 day ago

I'm pretty sure the software I use for work is written in COBOL too, but they're currently in a multi-year rollout of a modern replacement. So that's good, I guess.