Re: Boris pleads ignorance
i ii iii iv
42029 publicly visible posts • joined 16 Jun 2014
It's not just one scandal, it's a whole stack.
First there's the scandal of the original prosecutions including inducing the innocent to plead guilty.
Secondly the fact that as soon as it was discovered urgent action wasn't taken to proactively and promptly quash every single verdict as unsafe. There may well have been some real fraud cases in there but given the circumstances it would likely have been impossible to work out which they were.
Thirdly the fact that immediate urgent action wasn't taken to proactively and promptly compensate those convicted or forced to make up "deficits".
Fourthly that criminal cases weren't investigated and, where appropriate, prosecuted by the barrier presented by the ongoing enquiry and finally that the PO has been allowed to drag out the enquiry for so long with delaying tactics.
It's not just an IT scandal either, it bears on the entire British justice system. There's an old saying "justice delayed is justice denied.". An awful lot of people are being denied justice.
I reckoned at the time we should have had a whip-round for Labour funds. I'm sure we could have managed half a Bernie,especially as it would be refundable when the press found out. As we'd have had to include some freelance journalists on the basis that they might be affected it would have been hard to prevent them finding out.
Mine's got a brown envelope in the pocket.
This particular story is a recurrent one. It will turn up every so often in every Who Me, On Call or any other IT forum and, if you've read the comments, you'll see that the articles that prompt it are only the tip of the iceberg as commentards will add there own experiences.
You'll also find a few of us complaining that email clients are to blame for poor design; personally I'd like to think that some day someone working on Thunderbird, Outlook or whatever would read such a thread and undertake a bit of introspection.
However it does provide a bit of light relief to read of someone who's bullied their way to the top get a bit of comeuppance for failing to have picked up a few working skills along the way.
Presumably these Linux boxes were servers, not PCs that get shut down every night - or even more regularly than that. The contents of /tmp are not unimportant but the application would be expected to manage its temporary files. Also, a proper shutdown procedure would signal the application to shutdown and give it time to do so. However in the event of an unplanned shutdown it would be important not to clear /tmp because the files in there might need to be recovered.
Paranoia is a requirement for a DBA or any server admin. Managing a server is not the same as managing a PC.
His logic was that if someone was not screaming for something in the last pile by the time it got there, then it was irrelevant and no longer needed.
"That contract from eight years ago that we're going to sue about. Everybody says you had it last..."
Sometimes stuff is never too old to be irrelevant.
"have people just generally lost that mentality of keeping the inbox tidy?"
Yes. The absence of that pending tray is part of the problem.
Email clients are apparently built by people who have never worked with physical mail. In the past a busy exec would probably have had a PA or secretary who would systematically file mail that needed to be kept. A large bureaucracy might have a registry dedicated to the task. Now we have email clients designed by supposedly clever people which ought to be able to automate all that but which can't even manage the basics.
"The weirdest thing I had to contend with the tube a few years back ... was that apparently the Circle Line no longer operates as a continual loop"
Not having visited London for years I couldn't believe it when I saw it. My regular commute when I worked there was from Marylebone or Paddington to Euston so it would have been a big inconvenience. The name's a big clue as to how it should work. I wonder if it was a Boris idea.
"Now, we live near a reasonably large city elsewhere in the UK and have busses and trains that are reasonably regular, but you do learn the timetable."
We have one bus an hour to town which takes 40 minutes but if I drive over to another village there are 4 scheduled and it takes 15 minutes so that's what I do." In fact there were 2 companies on the route vying with each other, each apparently with 4 buses an hour. Since COVID although there are still timetables and the displays in the bus shelters tell when the next bus is due the relationship between the display and arrival of buses is random. In fact although the shelter is only a few minutes from the start of the route I've seen the "due in x minutes" message increase the value of x.
Learning the time-table is of no use whatsoever.
* No I'm not going to drive to town and faff around with trying to guess how long a pay and display ticket to buy.
She was, however, amazed at some of the allegedly clever scientists whose reaction was "but how an I going to get home?"
She, of course, had nothing to do all day except wander round the place. The staff who did the actual work had plenty of other things to occupy their minds. Not having wandered around the place all day and had the opportunity to see which gates were locked and which weren't, they might be concerned that if one gate was locked the rest might also be. If she were that bright she might have realised that.
If an exec is capable of "saving" messages in Deleted they're not going to be capable of creating new folders; it's an either/or situation due to a limited supply of brain cells. And even when the new folder is created it doesn't have a handy key such as Del to put it there. You then have to provide a filter to move a message from Inbox to Old messages once it's been read. This is really behaviour that should be part of the client if we're going to break users out of this behaviour.
"Personally, I'd like to see a time limit on trash being implemented at an OS level."
In Linux the trash-empty command is available. It's found in /usr/bin of course.
Without arguments it empties the desktop's trash, with a numeric argument it empties trash older than that number of days. I have it in my KDE startup list to run with a 180 day parameter. It's strictly for trash bins specified by freedesktop.org so it doesn't help with email clients which have their own trash handling.
They had apparently been "told" to do it, but when pressed they couldn't say by whom or why.
They probably train each other to do that. The email client doesn't provide any options other than Inbox and Trash or, as someone said above, Drafts. Maybe some use Sent - that probably would get restored in migrations so doesn't become part of support stories.
Using trash as storage, temporary or otherwise gets mentioned here from time to time. It seems a big gap in email clients that there doesn't seem to be anything between Inbox - which in any sensible usage ought to be for incoming mail yet to be read and Trash which anyone ought to realise is for stuff held temporarily before deletion. Deletion from Trash ought to be automatic after a configurable interval to discourage use as storage.
Sans serif fonts are the triumph of form (for some values of form) over function. The requirement of a font must be to unambiguously indicate the character to the reader. Any font which includes a single vertical stroke as one of its glyphs is apt to be ambiguous between lower case L, upper case i and possibly number one*. A font which has this for two characters is really problematical even if they're differentiated by slightly different lengths and if there are two equal in length you end up with with the worst case which is Arial.
* The way I, and the article, had to convey this surely stands as condemnation.
True. But if the cloud provider is acting as your DBA they should also have backups, especially when they know they're about to turn off the service. Your backup is against the cloud provider having a bad accident and their routine backups be the same. But natural caution should indicate that a final archive should be taken just in case. But if they don't grok "just in case" and a backup should be available only by accident is beyond belief makes you wonder just what sort of background they have in managing data.
"What is happening here is that the new, young things doing the programming don't want to learn legacy, they want the new, shiny, and feel that re-inventing the wheel rather than just changing the tyres is the way to go."
Unless they learn the legacy first they won't know that which they're reinventing is supposed to do. That means there's little chance that their reinvention will do it. Then stuff breaks and they don't care because they don't know that caring was necessary.