I was a sysadmin (at uni, in the early 2000s) and I am an SRE today (at Google).
The two jobs are nothing alike, at all, whatsoever.
Sysadmins are support roles. Their functional role is to provide a healthy substrate to run the application layer on top of.
SREs work at the application layer itself. If the system can't scale due to internal architecture, an SRE would be expected to propose a new, scalable design. That would be in addition to maintaining the substrate.
To be clear, there is also nothing inferior about performing a support role. No org can succeed without support.
But the two roles are not the same, and if a job's set of responsibilities don't include shared ownership over application layer architecture, then it can be a great job but it's not an SRE role.
It has been 10 years since I left Canonical (on good terms), but what popey describes (hi popey) about the intentional lack of human review in the Snap store sounds very Canonical to me.
I agree with all the recommendations - add human gates. Yes, it's expensive, but still far cheaper than the unbounded reputational damage that just occurred around the untrustworthiness of the store (hi Amazon).
Full body scans are a common preventative measure in Taiwan.
My parents (expats, living in the US for over 50 years) flew back and got routine scans (MRI, PET, CT) in February for about $1000 USD total.
Similar to this story, they found a tumor on my dad's pancreas. A biopsy confirmed it, and he had surgery in August. They caught it at stage I. We're very lucky.
The latency from February til August was entirely convincing the US medical system to take his Taiwanese images seriously. They finally gave up and went back to Taiwan to get the procedure done.
I'm getting older myself and will absolutely be paying for any sort of imaging available.
This should be more broadly available to everyone. I'd be happy for more of my tax dollars to go to preventative care rather than rear guard action.
Real world usage is you only get to use ~70% of the stated range on a road trip, so we're really talking about 350 miles of range, which is, as you say, what most people actually want.
Why 70%? You obviously don't run the battery to zero, 10% is a common amount of buffer to leave. And then when you DC fast charge, the rate of charging drops dramatically around 80%, so people don't charge to full.
These are for ideal conditions, add in any sort of weather and the range drops again as you run a heater, etc.
Living in the Bay Area, driving to Tahoe in the winter without a mandatory recharge should be the gold standard.
It's not an unusual use case, "only" about 180 miles, and yet there aren't any EVs that can do it confidently because going uphill in the cold with aerodynamic-destroying ski rack is really hard.
A car with 500 miles of fair-weather range could probably do it?
The two jobs are nothing alike, at all, whatsoever.
Sysadmins are support roles. Their functional role is to provide a healthy substrate to run the application layer on top of.
SREs work at the application layer itself. If the system can't scale due to internal architecture, an SRE would be expected to propose a new, scalable design. That would be in addition to maintaining the substrate.
To be clear, there is also nothing inferior about performing a support role. No org can succeed without support.
But the two roles are not the same, and if a job's set of responsibilities don't include shared ownership over application layer architecture, then it can be a great job but it's not an SRE role.