AI = The Plan
For those old enough to remember "In the beginning was The Plan...", it struck me that you could replace every instance of "The Plan" with "AI" and it would still be pretty true...
52 publicly visible posts • joined 4 Jun 2022
One of the reasons mainframe assembler programs hadn't been replaced is that they could be significantly faster than the higher-level languages in use in the 90s. A financial org, aware of their Y2K problem, brought in a prestigious consultancy who confidently said they could provide a replacement system. In tests, it was unable to complete the overnight reconciliation process for accounts before the next day branch opening times, something the assembler code managed with time to spare.
The assembler code was rewritten to handle 4-digit years, and for all I know might still be in use now.
"As I understand it, the errant code was so deeply intertwined with the kernel that it wasn't possible to throw an error"
Pure speculation here, based on a completely different OS and architecture, but whatever: one additional factor that might have contributed to the instant disaster is that the uninitialised pointer held the hex value 9c. If you use that as an address, my thought is that it is so low in the memory space it might be something that is only supposed to be used during OS load, and any attempt to access it, even by the kernel, causes an immeduate protective stop because it's a "this must never happen" condition.
Back in the days when I was programming on mainframes, an address with that many digits was an absolute address, i.e. relative to the total memory space of the machine. Address 9C would have been firmly in what we called "the bottom left-hand corner of the machine", where things like the system clock resided. I have no idea whether that concept translates in any way to the PC world, but I do know that if any process on a mainframe had high enough privileges to access that area, but was not the actual OS, everything stopped. Very quickly.
Whenever you're given a really, really stupid order, ask for written confirmation. Saved my behind when an order to put a one-line patch live without testing brought down a key government system for three days.
(The patch was fine. It was the undocumented dicking around in unallocated memory that it unintentionally trampled that was the problem. But at least it found it).
30+ years back, I used to work for a firm that supplied Tesco with their till systems, and the new superstore systems specified every till having three netwirk connections over 3 100% independent networks back to 3 minicomputers in the back office, with failover redundancy such that any one of them could switch to running the whole store if needed.
But that was back in the days when a dial-up modem was fine for the amount of data that went back to head office, all transactions were reconciled by overnight processing and paper reports, and paying by card meant having your credit card put in a slidey clamp that embossed the details on a multipart carbon receipt. These days everything has to be instant and online, which means no connection = no workey.
There could be a much simpler way of creating an ID card. If someone hasn't passed a driving test and isn't seeking a provisional licence, allow them to apply for a driver's licence with zero classes of vehicle on it, i.e. it doesn’t permit you to drive anything but does act as evidence of ID. Could use the existing system throughout at minimal cost (adding one extra option to the system). A logical nonsense, but one that's cheap and functional.
Oh darn, I can't resist it.
Computers? Luxury!
Up to about age 12 our school desks still had china inkwells in them, and a pupil appointed Ink Monitor, charged with filling them with Stephens Blue-black Ink (why in god's name not Royal Blue Washable? Would have saved so much grief). And struggling with the steel dip pens that went with them, while trying to learn cursive handwriting. Later I had to teach myself to write all over again, to get rid of the illegibility caused by cursive.
Any hint of computers didn't appear until the later secondary school, wben a Physics teacher introduced us to binary addition and subtraction via a home made switch-&-light board.
I valued Wordpad for its ability to leave simple formatted files alone, retaining formatting witbout adding anything unwanted. And as others have said, it could open almost anything - you could get useful clues from the opening bytes of a mystery file as to what it was infended to be - a sadly not infrequent occurrence with easily corrupted floppy disks.
I have posted it before, but it's worth another airing. Working on a large government system, a colleague eventually moved on to pastures new after complaining about the impossibility of getting a detailed spec from the systems analysts. One of his programs later caused some excitement by giving users the response "Error 4338 - some day they're going to specify this message".
Back in the 90s I worked for a minicomputer manufacturer, happened upon one of the FEs dismantling a parallelogram shaped fridge-sized machine from a bank. Movers had pushed it out of their van onto the tail-lift, hadn't realised it had rollers underneath... It kept going, straight off the edge. Fortunately these machines were built to a military spec which included being able to be parachuted out of planes: the chassis was scrap, but all the boards and components were servicable.
I feel like opening and successfully closing three levels of parenthesis with a degree of elegance calls for some sort of award, similar to the recognition given to achiement in gymnastics. Most of us (and I include myself in this) are far too prone to throwing in an opening bracket, then forgetting to close it. Although programming (and using Excel formulae) does tend to reduce the error rate a bit.
We moved into a house where the proud former owner had fully rewired it in the 1950s - using salvaged ex-GPO lead covered cable and the various-sized round-pin sockets. Surprise jolts from touching parts of it. Even better, he'd nailed a long run of it to the garden fence to aviaries at the end of the garden. Using uninsulated staples.
We had the only electrified fence in the neighbourhood.
Good lord, that's brought back a memory of around 50 years ago. It might have been in Harrods or a similar department store, some distant memory says "the Tudor Restaurant", but definitely a Gents with a liveried attendant who said "Thank you Sir, thank you very much indeed!" in a stentorian voice every time a coin hit the platter. What a weird recollection.
I worked on developing a government system that went live in the 1980s, and remember the flailing and squawking in management dovecotes when it emitted a message to the effect of "Error 2388 - Some day they're going to specify this message".
I knew the chap who programmed that bit of the system, and remembered his complaints about the impossibility of getting a workable specification out of the systems analysts. He moved on to another employer shortly before the go-live date, as I recall.
Brings back horrible memories of ancient code with stacked nested IF statements, some with ELSE, some without, and no check on whether it was possible to create an input that wouldn't trigger a single one of those statements. Which led to adding something like PERFORM FATAL-ERROR-ROUTINE (from which there was no return) at the end of such horrors, to catch "can't possibly happen" events.
Back in the 1970s, and while it was still in active use, I had a tour of RailMail, the underground rail system that carried parcels and letters between central London sorting offices - miniature driverless trains on a third-rail electrified system.
The station setup included traction current circuit breakers, which looked like the sort of massive knife switches any self-respecting mad scientist had in his lab in B&W horror films. Below them were kept a massive pair of elbow-length leather gauntlets. I was told that occasionally a bit of metal might fall off a train, or a lost tool be kicked up, and bridge between the power and running rails, tripping the 750v breaker.
Rather than sending someone out with a torch to search for the offending item, standard operating procedure was to don the gauntlets, close the breaker (with sparks) and hold it closed for a count of ten. Apparently this was usually enough to either knock the offending item off the rails or melt it, allowing operations to continue until close of service when a track walk could be done to find whatever remained of it.
Hmm. 45+ years ago I stayed with friends at a small hotel in Bournemouth. It had an attached restaurant, and the restaurant manager was a tallish, dark-haired man with a small moustache and an air of poorly-suppressed irritation (name unknown).
We invited a friend staying in a nearby hotel to dine with our party. Orders placed, we waited, and waited... After 45 mins one of our party ventured past the swing door, returning to report that the kitchen was full of smoke, but empty of staff.
Just then, the restaurant manager appeared, swanning his way through at a high rate of knots. Our guest put out and hand to stop him, and very politely said he feared there might be a problem, as we'd been waiting 45 mins for our starters. The manager fixed him with a baleful glare and said with emphasis: "Are you staying at this establishment?"
"No, but..."
"This restaurant is provided solely for the convenience of persons residing at the hotel, not outsiders. If I have anything to do with it, you'll wait another 45 minutes!"
And flounced off with his nose in the air.
I have often suspected that there's more Bournemouth in Basil Fawlty than we've been told...
[nerd voice] Well, technically... he's not being sued by Chazzer, but by the Crown Estate, which is a quasi-government body set up to make money out of a big parcel of land and buildings & stuff that George III gave to the government, in return for not having to fund the government out of his own pocket. But that doesn't sound as exciting.
The oldest scam baiter site I know is whatsthebloodypoint.com - only ten scam examples and hasn't been updated in almost 20 years, but the lead-ons are wonderful, as are the names for them. For example, Norman Gorman Smith-Bidet III and his planned (non-PC) dwarf-throwing complex. "Please keep in mind that I am just a simple minded multi-millionaire..."
If it was a *real* legacy system, then 3 hours sounds good to me too. Assuming a complex mainframe system, the ones I worked one needed in excess of an hour for a controlled shutdown and restart.
It's probably still a legacy system because it could be written in assembler language with minimal documentation - good luck explaining the cost of reverse engineering that to a budget holder when a rewrite gets discussed.
Could be pre-database, so lots of flat files with custom links between them - delete a file that hasn't been updated since 1985 and looks irrelevant, and the whole system falls over because the link is gone.
And the mistake made by a "contractor" - could be a massive government subcontractor rather than a hapless individual, so less likely one person will be held responsible. Especially if the client demanded a clean-up to reduce storage requirements (for example).