The airport hit a snag Thursday – yet another nationwide glitch in the border control kiosks, the second one this week, following another two weeks ago.
Is the software or the network bad? Are we certain these glitches are not due to external meddling?
azrhey 09:27 on 2025-04-11 Permalink
My knowledge dates from 2009-2011 but at the time I was working at SITA as tech support for airports all through America… I was specialized in Bag Tag printer, but was trained in most other systems… Airport computer systems work on spit and prayer most of the time. Double that for kiosks as they were a “newer” system that just got added on top the rest. I had to learn the basics of Fortran to solve about 75% of the problems and then escalated when it became too complex. Some things were just … “god knows, but it works”.
I remember in Dorval Air Transat hd/has a number of check-in counters. the same setting, the same equipment, exactly the same models of everything… the odd ( or maybe even, it was a long time ) numbered counters, the printers ONLY worked with a parallel port , the even ones worked both with parallel port and USB A port… why? WHY? Nobody knew… it worked that way… don’t look at it too hard or it might stop.
So airports… it’s a mess and I doubt they’ve fixed it since I left. When we mentioned it to our director he used to say “you think this is bad? you should see Atlanta, most of the printers work, but the user needs to click “printer not found” warning every time before it prints the baggage tags. IF we try to fix it the prints stops working” Nobody alive knows why…..
So yeah… airports… old code, cold machines… lots of silent prayers…
walkerp 10:16 on 2025-04-11 Permalink
Really appreciate some of that background azrhey. It’s interesting because they did put in that new self-check baggage hardware. It looks very modern and sleek and mechanically is quite impressive. Does not surprise me, though, that the software that ties it all together is archaic and kludgey.
Kevin 10:29 on 2025-04-11 Permalink
All software is kludge upon kludge, newer systems built on older systems that are never replaced, they just get more accretions, with updates and revamps forgotten because the person working on them was laid off or got a new job elsewhere.
I spend all day working with two computer systems that were created in the mid-90s, one built in-house that managers and IT have talked about replacing for the past 15 years — and all they’ve done is add a different interface that periodically fails. (I just use the old interface every day, and ignore the message that’s been displayed for several years that the system will soon be turned off.)
Blork 12:15 on 2025-04-11 Permalink
After working 30+ years in the software industry, I agree with azrhey and Kevin. According to a number of IT people I know, the entire banking system is built like that.
This is one of the reasons why it’s so hard to roll out things like healthcare database systems and whatnot (and why doctors still use fax machines). Nothing is ever built from scratch; it’s always a matter of kludging together disparate kludgy systems.
MarcG 12:40 on 2025-04-11 Permalink
Relevant xkcd https://xkcd.com/2347/
Joey 14:05 on 2025-04-11 Permalink
And yet the DOGE assholes think they can transform the entire US government into some built-on-the-fly AI system. Turns out they need to learn COBOL, a programming language so out-dated that one of its leading programmers was Art Garfunkel’s deceased brother, Jerry.
Blork 14:59 on 2025-04-11 Permalink
I learned programming by doing COBOL on punch cards!
Ian 16:01 on 2025-04-11 Permalink
Air Canada’s booking engine was running on COBOL.10 years ago and may be still.