Apple rather slickly has each update of each recent iOS be specific to a phone. ONE physical phone. Probably to prevent the skeleton key scenario.
Each "copy" (not really an appropriate word here) of the update is unique (I don't know the details) which makes it hard to just use the same binary to on every phone. Each "copy" only works on one phone.
Just a few thoughts:
There is a real advantage to back in the day: parametric statistics needs calculus but a lot of modern statistics
are more simulation-based so that could be stressed. Easier to understand (or at least less difficult) and usually
more accurate. Parametric statistics can wait.
Some appropriate subset of "How to Lie with Statistics" might be apropos early on and throughout the time spent.
It's practical information in life, gives a deeper understanding and is relatively fun. Care needs to be taken that this
isn't taken as "All Statistics Lie".
Consider bringing in language teachers for help. The words in statistics often have a subtle (or huge) difference
from common usage and they may be able to help with that. I had a mathematics background when I started statistics
and wasted a lot of time in early days because "variable" meant something different than what I was used to.
I've been doing UNIX since about 1974. I started out on research version 5 on a PDP-11, because that's the only architecture UNIX ran on in those days. v6 was the version that was much more widely distributed to academics, and v7 was the even more widely distributed update that led to the BSD derivatives.
v5 was pretty damn raw. There were no shell variables. "ed" was still written in assembler. Etc. Uphill through the snow both ways. Still, it was FAR better than any of the vendor OSes, no matter what people say about RSX-11. So I founded the first UNIX User's Group Software Distribution Center, purely so I could get my hands on all that goody-poo software. I also produced the very first T-shirt with a UNIX demon on it, for the Urbana, Ill. UNIX meeting - the first national meeting of UNIX users. I gave one to Ken Thompson, one to Dennis Ritchie, and kept two for myself. I still have them. If you've ever seen early USENIX T-shirts with a PDP-11 with pipes, demons, pitchforks, and a barrel labeled NULL, well, that was me (art by Phil Foglio to my design).
RealNetworks has a service, "RealTime", that works across most platforms for doing just this kind of thing. The use case explained to me was a family sharing video where much of the family is Windows but also there is a Unix person, a few Apple-or-nothing, and another few "Android All the Way".
Since this indeed describes my extended family, it was helpful.
> No company would want to give north korea or isis a reason to actively target undersea cables.
It might give them MORE reasons but, given my understanding of their agenda, those two (at least) already have reasons
to want a capability of targeting undersea cables.
A bit more in the sensor department might at least give warning that something is about to be damaged
and info about the thing doing the damaging.
Letters of Marque and Reprisal, as I've heard it. And "reprisal" is certainly closer to the mark (no pun intended).
It might be worth looking at INGRES (not INGRESS) and their business history.
They've managed to stay in business as long as Unix has had commercial databases (albeit with a close call every decade or so) and currently are in a similar position to yours but are still standing and still innovating. Many lessons in tech company survival, some of them of the "don't do that" variety to be learned there.
Sadly, the people that know the name tend to think of Ingres as what it was way back in the 70's-80's, not what it is, so the company is called "Actian" these days.
I wonder if sleep apnea is considered dementia in this context?
Sleep apnea is highly correlated with obesity at that age and it can give the sufferer a disturbingly
similar experience to senile dementia when severe and untreated.
A competent epidemiologist would control for the "They die before they develop dementia" effect.
Given this is a peer reviewed study I think it hugely likely they controlled for that.
Having gone through some hand nerve damage over the years I found it useful to have more than 1 keyboard;
having my hands in different positions during the day has proved useful to preventing further problems.
Most of my typing is done on a Unicomp Model M, which is very much an IBM Model M. I type most
reliably there although the I can type longer at the Kinesis models and probably would be almost as fast if there
if I really devoted the effort to it.
I find the clickety-clack of Model M type switches cheerful and I need all the happy thoughts possible when
debugging Ansible scripts.
I probably wouldn't inflict that on people in an open office.
Unix wasn't the the only OS written mostly in a portable language. Among the others was Primos. In the early days it was Fortran 66 (e.g. if-then but no if-then-else) Writing a screen editor in Fortran was an interesting experience.
Later on they used PL/1 subset G.
I saw the incident from my back yard. I was out there working on a Mr. Protocol column when I heard a particularly loud single-engine plane take off. What caught my attention was a sound I've only ever heard in the movies: the engine stuttered once, then stopped dead. I got up and looked to see if what I'd heard was really true, and saw the plane, with prop not moving, bank sharply in a 180 degree turn and start gliding back to the airport. I listened for a crash, since he was rather low, but didn't hear one. I'm glad he made the golf course and missed the neighborhood. (Look at a map: it's pretty obvious that the sole purpose of the Penmar Golf Course is to catch planes that don't make it. It happens often enough that I've wondered if they have course rules for playing around temporary obstacles with wings.)
Does fiction include about 50% of the technical documentation available?
Two things helped me so far:
1) A Sleep Study
I thought I was sleeping well because I fell asleep easily and stayed asleep. Nope: That
was my body trying to make up in quantity what the sleep lacked in quality. I thought my problem was
caused by too many electronic distractions (yeah some, but not most of it).
You don't get enough deep and REM sleep, you don't have focus and your ability to remember new things takes a BIG hit.
My problem was ridiculously easy to treat and I deeply regret spending several years not realizing I was being fuzzier than
I needed to be for want of a couple slightly uncomfortable nights wired up.
2) Turning off the router at night
Also helpful: I put my home router on a timer. 10pm, BANG! No internet on anything but my phone, which is OK to use
for short periods as an internet device and keeps me in touch if need be. Nonetheless it's much easier for me to decide to close
my eyes now. That probably only works because my phone screen isn't very big.
Too much of everything is just enough. -- Bob Wier