Re: Good news / bad news
Good News: You start tomorrow
Bad News: Taking the unremunerated six-week training. Again.
7327 publicly visible posts • joined 12 Jun 2008
The *proximate* causes of the blackout, as detailed in the official report on it were:
1) The power company had fired anyone with any real knowledge of managing power infrastructure and replaced them with cheaper computer-literate staff.
2) Computers had frozen on "nothing bad happening" screens because too many real-time problems were being received and no-one realized that.
3) because of point 2, no-one believed the field reports being phoned in of shorting lines.
4) Said lines were shorting to ground because they were heavily overloaded and the proper tree-trimming had not taken place (see point 1). Sagging lines arced to tree limbs causing line breakage and fires.
5) The overloads were happening because the power company had 6 "resistive load" type power generating stations and only one "reactive" load station (with the required I/V phase corrective hardware), which was down for maintenance during the heaviest reactive load season (summer, a/c etc) because, well point 1. The current in the transmission wires was, as a result, way higher than spec.
6) When the computer staff finally got a clue, they didn't get a proper clue and rebooted the computers, which helpfully re-instated the message queues that jammed them again. Time was wasted because this was seen as a computer problem, not a power distribution disaster in the making. See point 1.
7) The people in charge of mitigating the situation (more experienced staff would have started rolling "brown outs" to decrease loads, but see point 1) had an actual, honest to Cray playbook. It was set out in "Failover Class" order, a class one being that one power station was down, a class two that two stations were down and so forth. The staff were working the book from the class 0 situation, failing to recognize that because the "reactive" power station was down they were already in a class 1 failover. The mitigation script they were following (blindly) was the wrong script.
When the power went out, the grid momentarily reversed "sense" before throwing open all the breakers everywhere all at once, which caused a false assumption the problem was originating in Canada when in fact the problem was entirely localized in Ohio.
All in all a self-fulfilling prophecy of cheap-out economics, and a wonderful fiasco if you weren't unfortunate enough to be caught in it in, say, Manhattan on a hot August night.
Thumbed down?
That fuck faced fucker narrowly missed a Mom-mobile with a kid inside and left a 70ft evidence trail including his passenger-side front wheel c/w motor and wishbone assembly in addition to the sheared-through telephone pole that took out power, cable and internet for several hours - in a heatwave.
Fuck him and fuck the twat who thumbed me down.
Probably a Tesla owner fond of attempting his own Donald Campbell impersonation on the public highways.
Well the bloke who destroyed his Tesla along with large parts of the local infrastructure when he attempted traveling at Time Distort 7 outside my house will certainly be in the market for a new one.
Assuming a) He stays out of jail and 2) Can get insurance.
I'm really confused by companies that are blowing a gasket over remote working.
Pre-Covid The Register was alive with tales of "Hot Desking" and down-sizing offices to cut costs.
Post-Covid businesses are bleating about the need to fill those same offices they couldn't afford three years before.
Baffling.
I made a flying Klingon battlecruiser out of a couple of punch cards while working on a contract at Bitney Powes (name changed).
One staffer tried to harsh my 60s show mellow by stating I couldn't possibly know how it flew, but I went on a two minute monologue about how the canard design I had used would not only fly but was effectively stall proof as the "deck" above the "globe" was set deliberately at a slightly higher angle of attack than the wings, and the "globe" (actually just a 2d silhouette) acted as a rudder until he begged for mercy.
Pheasants are thick as bricks, about as aerodynamic and have the taxi-to-take-off acceleration of an ice-cream van firing on two cylinders.
And their feathers squeak loudly as they ineffectually flap their wings while strolling out of harm's way so predators can track them even in dense fog.
So slow and stupid, in fact, that it was illegal in Norfolk in the 70s to pick up a pheasant you'd hit with a car.
Which is why poachers of my acquaintance (M'lud) would use two vans.
Around the same time the good folk of Guernsey decided they were tired of looking at the Nazi-occupation-era fort in St Peter Port (built with local slave labour I was told) and so experts were called in to demolish it.
It made the Book of Heroic Failures as he least successful demolition. From memory:
The first time there was a bang and nothing else of note happened.
The second time the fort lifted off its foundation, but safely landed on it again. Bits of demolition shrapnel were found in local walls, though.
The third time they did it at night to avoid the possibility of shrapnel casualties, and woke the entire island population, but achieved no actual demolition.
At which point the people of the island demanded that the demolitions should stop, and they turned the fort into a museum.
Flixborough.
Remember that one happening in my first year at UEA.
Prof. McKillop used it in a seminar to illustrate why chemists could make a decent living in the stock market. "Who else can predict that the price of everything from nylon shirts to bleach is going to soar in the next 9-12 months because of the shortage of precursor chemicals?"
Never fix cyclohexane pipes with duct tape, especially if they run parallel to dry steam lines.
The ICl operators at my first job were impressed by the fact that Univac tape drives could be started with the glass down and liked to do that until one day the outer side of a tape spool fell off the other bits and 2700 feet of tape went corkscrewing all over the room.
This will be confirmed by any Univac operator except those from a certain large dairy operation, whose tape drives were intercepted on the road and redirected to our place by the salesman.
Long lead time on those tape drives in '79.
Good luck with that.
In every single yootoob video I've seen with subtitles those subtitles are riddled with gibberish created by the speech-to-text software being almost good enough for primetime. The hallucination issue will fade into insignificance behind the nonsense used as training issue.
Naturally, the "creatives" responsible for the content are too busy (ie bone idle) to proofread their visual word salad - which is a problem I foresee getting well-and-truly out of claw when AI software starts authoring everything from stereo instructions to software modules.
Once humans start automating things they forget the need for sanity checks or won't afford the staff to do them. "Yippee! It's Free" thinking goes all the way down to the Earth's core.
The noise to signal ratio will look like a tangent curve plot over time, making for medical procedure documentation and legal contractese that could have been written by Donald Trump.
And in 20 years this will be a superfund toxic cleanup site just like the ones the Pataki admin "bought" from IBM.
And decided would be used as-is for government staff, heavy metal contamination be damned.
Chip fabbing is dirty. That is why we let other countries do it and buy from them.
Luckily this one will be situated somewhere the pollution won't be noticed for a bit.
I'll be dead before the crocodile tears start flowing.
Back in the late 80s/early 90s an ATT spokesman said his biggest fear was that someone would realize how much copper they possessed, buy out the company in a hostile takeover so they could strip-mine the copper and not only bankrupt ATT, but leave the country with no comms infrastructure.
This was not an unrealistic fear in those Gordon Gecko days.
So T mobile recover the monies paid, with interest and penalties, and the now-healthy citizens of Wanaque can get back to waving their phones in the air looking for bars as their roads degrade and their services fail and their schools close due to lack of funds until the council raises taxes to cover the shortfall.
Win-win.
In the early days of Office, PowerPoint saved my company a contract.
I was in a quandary about how to re-explain a concept involving the switch from a DMS-style set-based database to a relational model for something the set-based model did extremely well. (Clever use of manual sets, if you care). I'd covered the subject already but the customer was understandably skittish and my words were inadequate to the task.
On my plane journey to the client I wondered if this "PowerPoint" thing, which I'd never so much as seen before, could help.
Yes it could.
I quickly put together a set of pictures to help me convey what my explanations had so far been unable to do. Same talk - with pictures.
Sat with small group of client's staff, in a cube, using my lappy and a (wired) mouse as a clicker.
Intelligent and probing questions were asked about the approach being described as each slide was shown and explained, and I was able to answer them. A marked contrast to the silence that greeted my previous attempt.
Job done, on a plane with a Windows 95 laptop with a battery life measured in hurryhurryhurry units.
So I quite like PowerPoint and it's free office clones. Don't use it much, but it does what it says on the side of the tin, which is unusual for anything computer-y.
Nonononono.
No.
*Attempting* to chat on teams without the blasted thing hanging is work. Restarting teams to make the borked MFA thing work as advertised is work. Attempting to place a telephone call using Teams without the seemingly mandatory three hangs-up-on-answer thing is work.
Teams meetings are what they've always been. An excuse for managers to schedule staff meetings in the unpaid lunch hour of their "subordinates".
Counting tickets as a measure of productivity. Yep, had this one, with EXACTLY the same issue. Meeting called. Example of "golden employee" was helldesk quick fix ticket history. Others pointed out that one ticket assigned usually encompassed 15 minutes of effort (assuming requestor had all ducks in a row, and was contactable if not) and could often take one or more days of effort (switch work, provision new server etc).
Water off a duck's back.
Back before remote work, before PCs in the workplace, I had a manager who was convinced I was not working to my contracted effort level.
I suggested he "ghost" me (pre-social media meaning) so he would have eyes-on while I was in the office.
He would come into the office and find me working already. He had to stay past his end-of-day too - I preferred to blitz problems and had a policy of "If I broke it, I fix it" that superseded my contracted work day (ie I was working for free, but that wasn't a problem since there was absolutely nothing to do of a weeknight in that benighted town. They closed the swimming pool at 7pm FFS I digress).
Manager lasted exactly four days, and never questioned my timesheet again.
Covid-era had me facing a similar issue over remote-maybe-he's-not working and I used the same tactic. This time the fish didn't bite, but did stop with the nonsense.
After all, stuff was demonstrably getting done.
ICL line printers used a barrel, not a ribbon.
A colleague of mine had worked in a place with an ICL "shuffle" printer. This beast had 120 character lines as per usual, but only a 40 character barrel. It would apparently print the line by doing the first 40 characters, then a carriage mechanism would pull the barrel back and shift it 40 characters, then shift it forward and he next 40 characters would be printed, then it would do it all again for the final 40 characters.
Thing is, the barrel was quite massive, as was the carriage mechanism (British engineering, built to last), so inertia was a bit of a bugger.
My colleague (who was not prone to tall tales, though who knows?) said that when the payroll or general ledger was being run they would use three operators; one to enter the console commands and do the running-around necessary for the old GEORGE-powered machine, and two to steer the printer away from important bits of the machine room when it went walkabout and prevent it pulling its plug out of the socket.
True? Who knows, but it's a great image for the old brain on boring days.
Fuel is so ridiculously cheap in the USA that cars here often have a remote starter so you can start the car and have the heater, defroster, heated seats and heated steering wheel run up to comfy while you get ready for work or walk from the train to the car park.
Used to scoff at this, but I guess I'm going native because it saves oodles of time in the winter (and nothing beats having a computer activated warm steering wheel in an otherwise freezing cold car should one forget to set the heater up appropriately before putting the jalopy to bed).
Cars in Alberta Canada have not only block heaters to keep the oil loose and stop the coolant icing, but also have cabin heaters to prevent windshield damage when using a warmed up engine's defroster.
You can often see two extension cords peeking out of the radiator grills, and motels usually have electrical stands for overnight use.
That was using Sperry Univac 1100. You remember those? The ones with 6-bit bytes and no lower case charcters. Solid as a pile of jelly.
Oh, you were working with FIELDATA encoding. The 1100 word was 36 bits and could easily hold four ACSII bytes if you told it to. Indeed, you could chop up the word in any number of novel ways to get your job done on 60s, 80s 90s and Clearpath machines running Exec-1100.
FIELDATA was and probably still is used on 1100-derived mainframes running Exec-1100 for file system naming and related stuff because you don't need lower case or special characters that aren't allowed in the filenames anyway, and using a six bit encoding scheme gains you 50% more usable bytes over ASCII encoding under those conditions.
Solid as a depleted uranium anvil - if you knew what you were doing.
Of course, most banks in the city used IBM hardware back then, so banking staff who were introduced to Sperry 1100s often had to unlearn a bunch of stuff. I had a supervisor once who blithered on about how much trouble I would be in with a solution I was deploying when it came across packed decimal fields - of which we had none and which the 1100 Cobol did not support natively (though it could read and write them using one of the umptytump special COMP-n formats listed in the Supplementary Reference).
Let's do select jump keys next.
In the Badole Dayz of NT I once listened sweetly to a unix "expert" rant about how he had to install cigwin to get anything done because he only knew how to do things the correct, POSIX-compliant way.
When he paused for breath I said "So you don't remember about the POSIX API in Windows NT?"
It was dropped because it was never really popular, but the look on said expert's face was worth the wait. He and I had sat together in the NY course but he was so busy asking "Can you turn off the GUI?" at every new topic he had obviously missed most of the content.