Re: You really pushed the big red switch?
"I agree that it's unlikely if the DC's power system had been design & built"
But we all know it's always the DNS - except when it's the UPS.
43081 publicly visible posts • joined 16 Jun 2014
"A sensible and organised (and easily navigable) hierarchical structure"
This is apt to come into the "no plan survives contact with reality" category when one branch of the hierarchy proliferates so much that everything else is miniscule in comparison and you realise the real root should have been some node about a third of the way down it.
"We also used to have a senior procurement manager who did something similar but in her mailbox. Hundreds of sub-folder, filled with who knows what. She thought that the appropriate place to store all the contracts the company had entered into during her tenure was in her own mailbox."
What better system had you provided that would automate, or at least simplify, her storing this elsewhere, bearing in mind that the covering mails might need to be accessible alongside the actual contracts, for both herself and her successor?
"and a worry he could follow BASIC instructions"
Clearly he did follow your basic instructions. The documentation for the nuclear train was probably written to very controlled standards. It wasn't his fault that you didn't follow them when you wrote yours.
Here's a suggestion: using whatever piece of software you're responsible for is part of the users' day-to-day operations. The place for is is not a separate document, it should be an integral part of their standard operating documentation.* Get together with whoever writes such documentation and have them incorporate into the documentation for their routines. Help them ensure that it's correct but otherwise it should be couched in the users' terminology, not something different that they don't understand.
* OK, it's a big assumption that this exists but the principle still stands - it should be integrated into whatever form of training is given to the users to do their job and not something separate.
"We never did find out who was giving out this epically bad advice, eventually the users learned it was a Very Bad Idea."
The response to this thread, as with any other thread recounting such anecdotes, shows that this is extremely common and undoubtedly users are training each other about this.* The other solution seems to be to keep everything in the inbox.
Don't blame users for creative, if inappropriate, solutions to a problem which should have been solved properly by the application designer.
The reason for this is that there appears to be no email client makes provision for anything saner**.
* Rather like checkout operators who are convinced the only way to control the belt is by using one of the only two separators that the supermarket has deigned to provide with each checkout.
** See also providing a Sent folder and automatically putting all sent emails there to ensure they're kept out of the threads to which they belong, which are probably still in the inbox or the trash.
It depends. In my usage a lot of things do indeed go in project hierarchies. OTOH some files, particularly pictures and maps, are collected resources that are used in multiple projects. They sit in the appropriate directories exposed as desktop folders. There really isn't a more appropriate way to deal with them - possibly other ways could be equally appropriate but this suits me.
Document files include various manuals. Obviously there's a manual directory tree. But because its contents are documents it lives in documents although some sub-trees are linked to the desktop. And not just manuals - there's a whole hierarchy of downloaded historical sources - JYAS, YAS Record series, Wakefield manorial rolls and others. They're documents so that goes in the documents directory but the head of that particular hierarchy is also linked as a folder on the desktop.
Other documents are - well - just documents. They might as well be organised in some way in the documents directory, again, represented as a desktop folder.
Downloads? A lot of downloaded documents are in the historical sources hierarchy, of course. OTOH there are a lot of downloads of S/W such as various Linux Distro installers. They're all downloads not linked to any particular project. Where should I keep them? Downloads seems as good a place as any.
What really deserves scorn is assuming one form of organisation fits all users.
If the US government imposes sanctions on you, you company/organisation or country it becomes illegal for US based companies to do business with you. That's why the ICC switched their email from Microsoft to Proton. If the customer's infrastructure is actually AWS, Microsoft, Google or anything else run by a US company then it could indeed be turned off. If it is actually on-prem or run by a local provider, then you're correct, it can't (although updates could stop)* but that's what sovereignty is about.
If your data is adequately encrypted and static, then again it can't be got at. If it's being processed then it has to be read and there will be at least some unencrypted data and the keys to access it in memory. The US government or CIA will not need to surreptitiously exfiltrate it. They'll use the CLOUD Act to compel your vendor to give it to you.
* This assumes that it doesn't periodically check in with the vendor for licencing reasons.
Maybe they should have added a fifth bullet point: "It will not be turned off at the whim of a US president."
There's always that pesky spreadsheet or file that refuses to be translated away from Office
The point of view changes and it becomes known as "legacy".
I used to look after a PA system which would periodically become unstable with one of the output pair's anodes becoming red hot which inspired the thought that if the system were set up so that the valves which were on drew enough current and the clock was slow enough the entire operation of it could be followed viaually.
As I suggested in response to the the NRW artivel https://www.theregister.com/security/2026/09/07/welsh-environment-regulators-foi-blunder-exposes-diversity-data-of-2000-staff/5294748 there may be instances where responsibility goes further up than the organisation responsible. Government might be forcing organisations to keep data which is, in effect, toxic. An organisation with no need for, say, cyanide, wouldn't keep a couple of barrels in stock just for the sake of it and nobody in government would require them to do so. Once you get into the realms of the intangible common sense judgements get left behind.
It would be relevant to look at this from TFA She cited the maximum fines of £17 million or 4 percent of the offending organization's annual turnover, whichever is higher, calling it "a meaningful enforcement regime." and ask whether there should be some minimum fines.
One has to ask how many of this categories of information are relevant to environmental monitoring and if they're not, why were they kept. Of course we all know the answer: none of them. It's a box-ticking exercise. The value of that box-ticking should be set against the consequences of events like this and whoever demanded it, even if it was higher up the government food-chain held responsible for not conducting a risk/value analysis, or, if they did, for going ahead in defiance of the results of that analysis.
"If you go to the original Twitter thread"
I don't go near it. However the influence doesn't necessarily run neatly along the time line. It depends on what individuals see and when. Someone could come into the area late, be familiar with one or two of the current examples and them maybe familiarise themselves with earlier ones or maybe not.
Influence may also be along the lines of "That's not the way to do it. This is much better."
There's also parallel evolution.
It's possible, of course, that the R should stand for Re-write.
The manual might have said something like "Disconnect each fibre in turn. After disconnecting a fibre do $MAINTENANCE" and never said anything about when to reconnect the fibres or even whether to reconnect them. Some people can be very literal. It was once said that a good tester was someone who could look at the system menu button on the top left of the then Windows ~3 window and see a minus sign.
Well, the article starts off by quoting actual evidence: children saying it's made no difference to them so your first option can be ruled out. The remainder, however, splits into two: no changes have been made o change have been made but the kids worked round them anyway.
It's just another example of the fact that no plan survives contact with reality.