There are two Motorolas
This one is Motorola Solutions, which does govt & big business tech. The other one is the bandset biz, Motorola Mobility, owned by Lenovo.
89 publicly visible posts • joined 4 Jun 2022
It's surprising what can be done with a slow connection if you're patient. I recall a data system for a retail firm with hundreds of stores, where every store had tills that fed sales data to a store controller. This then used a slow modem connection (400 baud IIRC, later 1200 baud) to feed the data back to HQ. Because the controller and connection operated 24/7, but stores only generated data during trading hours, there was plenty of time to get the day's data up to HQ before each store opened the next day. At the time, having data up to date to yesterday at HQ was state of the art.
Also if you use AI to drastically reduce the workforce now, you run the risk in future of not having a supply of people with enough experience to know how to use the tool safely and productively.
Cue more recruiters searching for 18-year-olds with 20 years' experience.
One of the areas where code *had* to be rewritten to use 4 digit years was banking and insurance - because there were customers with 19th century birthdates, 20th century account opening dates, and 21st century policy renewal dates. Not a lot, but enough to render old methods of guesstimating the century completely invalid.
Also there were a lot of one-man companies involved in Y2K work because in the 1990s that was the standard way of operating as a contractor. Most clients wouldn't engage you unless you operated as a limited company.
One could argue that because the US legal system places duty to shareholders before everything, with dire penalties for failing, that the shareholders are actually The Powers That Be, and also sole controllers of the money. Hence the current situation - everywhere, not just at MS.
Adverts for Eightsleep started popping up in something I followed, so I remember taking a look at their website. From what I recall it's a bulky mattress covered with sensors and filled with pipes containing distilled water, with a box beside the bed that heats or cools said water and pumps it through the mattress. In addition to the monthly charges, there's also the cost and faff of replacing all the water at regular intervals to prevent it from becoming some sort of bacteriological hazard. I also recall hearing complaints that the pipework tended to spring leaks after a while. Somehow I just don't like the idea of sleeping on something that combines mains electricity and water, and is apparently known to leak - anecdotally, of course.
Now I am reminded of the line delivered with gusto by Trevor Howard in the film "Sir Henry at Rawlinson End" :
"I don't know what I want and I want it NOW!!"
This seems to be current leadership thinking. The film (and TH) score pretty highly in terms of demented leadership. A Vivian Stanshall classic IIRC.
Not going to use it.
Every time I go through the process of problem definition, solution design, solution construction, I can feel my brain learning and refining skills. Using AI for any part of those processes means I lose valuable experience and become less skilled than I otherwise would be. Or waste time correcting stupid errors that teach me nothing.
The best kind of work is a life-long learning experience.
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).