Burning Bridges (Lost Forevermore?)
This is just another incident which underlines how administrators and technicians have thrown away their fallback technologies and methods after they've built systems based on, and dependent upon, always-working, networked-to-everything computers.
When I was in college, there were many non-computers-networked-to-the-entire-world ways of doing things. We had scheduled local-cable TV broadcasts of videotaped lectures, photocopies of professors' overhead-projector sheets (these days, called "slide decks"), mark-sense test sheets (fill in the correct circle with a #2 pencil), "announcement" messages on some phone lines, etc. The campus didn't screech to a halt if email wasn't working, because we had the postal service and land-line telephones. If the electricity failed, guess what? The buildings had large windows to let in daylight, some of us had manual typewriters, the school had some mechanical mimeograph machines, some of us had slide-rules, and we had trigonometry- and logarithm tables in books. It was slow and aggravating to do things using some of those methods, but we did have them as fallbacks.
Our local convenience store had no power one day due to an auto accident (power pole damage). Their PC-based point-of-sale system was useless. They were still open for business, though, using a battery-powered adding machine to print sales slips. They were able to do this because they had labelled the packages with the prices. A major retail-chain store just up the road simply closed for the day, because without the abiity to read bar codes on packages, and to access the price database in their store computers, they couldn't do business. (Why no battery backups for the major store's POS systems and back-end computers?! Good question!)
Business continuity. That's an actual thing.