this post was submitted on 30 Jan 2024
844 points (98.2% liked)

Technology

59341 readers
6370 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 9 months ago (1 children)

A lot of these systems are also always on.

Used to work at an airport that had a similar issue, turning some of these systems off simply isn't possible. So you end up having to run the replacement system simultaneously with the old system for a few days. Can't simply take it off line for a day.

[–] [email protected] 2 points 9 months ago (1 children)

Running two systems simultaneously for a couple of days, that's a huge problem, not solvable

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago)

It's an expensive problem, especially if it's a system that's being used all across the airport by regular staff.

You need to train thousands of employees to use the new software, you need to have one person using the old software as a backup, while the other uses the new software, often while surrounded by hundreds of often angry customers.

And if something goes wrong, which it invaribly does (even if it's user error or someone snagging a cable), shit can get very expensive. Small delays, add up to larger delays, and cascade through the entire system. Delayed flights, tens of thousands of euros in costs, hotels for thousands of passengers, missed flights, missed meetings, damages, lawsuits, penalties for missed landing/take-off slots, missed time windows for certain cities which don't allow flights after a certain time, etc. And often you discover legacy stuff while you're upgrading that needs fixing, stuff that no one knows how to replace anymore or is physically hard to access.

Sometimes it is genuinely better to leave it. COBOL is 60 years old. There's still plenty of stuff running on it, exactly because it's often too expensive and too risky to replace.