If you had no idea what a restorable sequence is the takeaway is about halfway down the OP:
“This is why Linux now provides rseq() which is a much more enlightened solution. With restartable sequences, you actually can get rid of both the mutex and atomics, while the OS continues to fully abstract scheduling. The way it works is you advise the kernel whenever your program enters a critical section of code that you don't want interrupted. It's probably going to be maybe 10 assembly instructions tops. The first assembly opcode should be a move instruction that sets the rseq_cs field. The last instruction needs to be the thing that makes the modification to your global data structure. Think of it sort of like a really tiny database transaction. What makes it go fast, is that the bidirectional communication with the kernel happens via shared memory.”
"The system" almost always consists of mid-level bureaucrats. Maybe not this particular one, but her bosses -- a job which, if she sticks around long enough, she will eventually get promoted into. A large amount of what the government does isn't formally law, it's policy, which is often decided by those mid-level managers.
And like individual bureaucrats, "the system" in this case finds it easy to make demands of people if those demands do not result in increased workload for the agency. But if they do result in increased workload for the agency, then the policies that result in that increased workload often get rethought, or the agencies suddenly discover that they can make allowances, and so on.
In this case, I'm confident that "agency X cannot accept pdf documentation" isn't actually law. It might be guidance issued by an agency lawyer, but that isn't the same thing. It is likely to be a policy decided fundamentally by the IT department, which is estimating a high cost for securing the agency IT system to securely handle pdfs. That cost is compared to the cost of accepting faxes, which is significantly lower, and so a policy is issued that the agency cannot accept pdfs, and the legal guidance is offered as justification.
What is not factored in to the decision is the cost to the taxpayer. That's an externality.
So, if the taxpayers can magically make it much more expensive for the agency to accept faxes, so that it is suddenly not an externality any more -- which is what happened in this case -- then the above calculus changes, and the agency discovers that, you know what, actually we can accept pdfs. The IT department is ordered to make the necessary improvements, and it all works.
In my particular case, we were told for literally decades that we could not telework. It wasn't secure enough. Then COVID happened, and suddenly we had a telework system in place, with all the necessary Microsoft licenses purchased and servers stood up and laptops issued and VPN accounts activated, in less than three weeks, and nobody said anything about telework not being secure enough ever again. Because the original justification wasn't true. Setting up telework was more expensive, so we didn't want to do it, and we came up with reasons why we "couldn't". As soon as it was cheaper, we found out that we could do it after all.
“ It reads like an indictment of the government employee personally”
As a government employee: it often is the employee personally. Not always, but surprisingly often. There is a type of mid-level bureaucrat who just can’t be bothered to make anyone else’s life easier, even if they can. It’s just easier not to, and over time that becomes its own form of malice. The tales I could tell you about security officers basically abusing their power in order to make their own lives as easy as possible, while making everyone else’s live almost impossible…
As a government employee, enmeshed in the bureaucracy:
This is the way.
The problem is that it took Karen zero effort to say “we only accept fax”. She doesn’t care about how much effort it takes you you — in fact, as implied, it taking you a tremendous amount of effort actually reduces her effort. In order to make a dent, you have to figure out a way for the idiotic policy to impact the person making and/or enforcing it. That’s the only way it ever changes.
So after almost 50 years of hacking, I'm starting to feel it in my hands. But I don't have any wrist problems -- no carpal tunnel. What I have is tendonitis in my fingers, primarily in my middle fingers and my right pinky (from slamming Enter several million times).
I've had steroid injections into the tendon sheaths of my fingers a couple of times, which hurts like a bugger when it's done but definitely improves things after a few days. It isn't a cure, though, and my hand doctor thinks I'm going to need surgery eventually.
I have to assume that a split keyboard won't help this. Is there anything that might, short of a voice interface?
That’s certainly an opinion. I’m not convinced that it's a good one, but it’s an interesting one.
I think it’s probably important to remember two things: 1) the novel is a relatively modern invention — Don Quixote is often thought of as the first novel, and it was written in 1605, but 2) fiction clearly is not. The Iliad, for instance. In fact, what we think of as “history”, a recounting of events strongly tied to facts, is also a relatively new invention. It is my understanding that ancient authors were more interested in telling you what was true, in a spitirual, philosophical, or moral sense than in telling you strictly what happened. Obviously this is more clear when reading e.g. religious texts like the Bible, but my understanding is that it’s also true of more “straight” histories — Roman historians were not above inventing entire speeches for which there were not extant records and placing them in the mount of a Julius Caesar or whoever. So strictly speaking if you’re reading sources as old as the OP suggests, there’s no getting away from what we would call fiction.
My wife and I have an ongoing conflict of taste in matters of literature. She prefers what I consider to be absolutely depressing high literature. One of her favorites is The House of Mirth, wherein the protagonist starts out wealthy, slowly goes into debt, ends up impoverished and addicted to morphine, and ends the book by committing suicide. She says she likes these stories because they’re “more realistic”. I claim that no, they aren’t, and even if they were I read specifically because I get enough realism by waking up in the morning, thank you very much, and although I’m not averse to deep thoughts in my literature I usually prefer it with a side of likeable characters.
Anyway, my point is: to pick an example, LOTR is a book of fiction written after WWII, and although Tolkien was an expert on and was drawing from a deep pool of literary traditions that predate written language, he was also addressing modern concerns, and that’s what makes the book more interesting than Beowulf. It’s don’t care that it’s labeled “fiction”; the concepts it explores are as true, in the ancient sense, as straight Greek philosophy, and maybe even as applicable. And if you want to read for information, you’re almost certainly going to get better information by reading a modern history of Rome than by reading Polybius.
I was a grad student in Dave Akin's lab from 1994-2003. Like many labs, we had a journal club. Once a week (Wednesday, I think) somebody would give a presentation over lunch on a paper they'd read. We would get takeout Chinese and eat while discussing the paper.
On this particular Wednesday the presentation was on a failed spacecraft program. It's been a long time, but I think it was probably this paper:
which is the initial failure analysis of the Mars Climate Orbiter (1999), which famously crashed into Mars during its orbital insertion burn because JPL specifications were in metric, but Lockheed wrote code in imperial units, and as a result there was a failure to properly convert between newtons and pounds. One fact of note was that the the team responsible for spacecraft navigation had already observed anomalous trajectory data but their reports were ignored because they didn't follow program guidelines for filling out the paperwork to document the observations, so the insertion burn went ahead heedless of what the spacecraft's behavior was trying to tell them.
Ultimately, the loss of mission was a result of unclear responsibility for ownership of the orbital maneuvering software, including the mission requirements that traced to the software, the development of the software derived from those requirements, tests to validate the software, and reports from users of the software that it was behaving unexpectedly.
I was trying to be funny, and turned the statement around from "clear lines of responsibility" to "clear lines of blame".
I wrote code to do this between a C64 and a 1541 disk drive when I was in high school. It got me to the international science fair and (probably) earned me a full tuition scholarship for undergrad.
“This is why Linux now provides rseq() which is a much more enlightened solution. With restartable sequences, you actually can get rid of both the mutex and atomics, while the OS continues to fully abstract scheduling. The way it works is you advise the kernel whenever your program enters a critical section of code that you don't want interrupted. It's probably going to be maybe 10 assembly instructions tops. The first assembly opcode should be a move instruction that sets the rseq_cs field. The last instruction needs to be the thing that makes the modification to your global data structure. Think of it sort of like a really tiny database transaction. What makes it go fast, is that the bidirectional communication with the kernel happens via shared memory.”