Just putting it here in case anyone has to do it (I hope no one ever needs it): it is NOT painful at all.
I was told “it’s like a grenade explodes in your spine” by a (stupid) friend, it caused me to refuse to do it for the first time, which if I went through with it, things would’ve been very different for me, I would’ve been diagnosed days faster.
Again, it’s NOT painful at all, they use Lidocaine, you’ll feel way less than when they draw blood from your arm.
If it’s needed, don’t hesitate.
This seems to have not always been the case so where did things go wrong with Time Machine? Was there a particular MacOS release that broke everything?
Also what is really the gold standard in terms of backups? On Linux land I never had a great system. All I did was manually copy my drive every 6 months to a few external disks using clonezilla and gparted. This was tedious and not very user friendly.
Recently I learned of ZFS with its CoW approach and support for snapshots & it has piqued my interest. However while it may be a strictly superior way of doing backups its still not very user friendly. I have to budget time to learn it, set it up and of course its absolutely hopeless to expect my non-technical friends/family to figure it out.
Ultimately I'm seeking a tool that has good enough UI / UX that even my non-technical friends & family can use but supports incremental backups / snapshots along with detecting + auto correcting data corruption issues.
Does such a thing exist? Who are the big contenders in this space?
Advice seems to be 'only use it with external drives' and then every time you plug the drive in it wants the password.
Once or twice a year it gives a verify error (i imagine this is because a plug gets pulled halfway through a backup on one side or the other), and I just have to go find the last verified date, zfs rollback, and then re-verify. Afterwards it picks up where I left off, and the historical backups are preserved.
Wish it didn't require this extra effort in the first place, but much better than having to nuke and pave every time.
Even better, it's working great over Tailscale so I can even use it remotely. Only big hiccup I ran into was figuring out some ZFS setting about quota vs refquota (something like that) to have the Time Machine's (artificial) space limit match the ZFS quota so that Time Machine would prune the oldest backups appropriately (otherwise the ZFS snapshots took up an unpredictable amount of space and Time Machine would unexpectedly get out of space errors before hitting its space limit).
For people who use helix and want the full IDE experience, why not Zed, or maye even VSC/JetBraind IDE (come to think of it, how's fleet doing?).
If i need something simple I fall back to nvim, and if I'm missing features I sometimes boot up WebStorm (or if a colleague wants to navigate through something)
EDIT: for context I'm a hobbyist who use n/vim for 12 years or so before switching to helix for the last couple of years. There are several things about nvim behavior that I still miss quite a bit and still feel more natural, but the instant startup of helix vs a second or two for nvim configured to a similar level of functional makes it totally worthwhile for me.
What? It's simple enough that it's taught to EMTs with ~160 hours of education (I'm a paramedic and EMS instructor and evaluator):
Temperature <96.8 or >100.4
Heart rate >90
Respiratory rate >20
WBC count > 12000
Add confirmed or suspected source of infection. Simplified, each additional match increases the suspicion.
The issue, as described later, is not that it's hard to spot, or the SIRS criteria tool didn't flag it, it's that the doctor didn't do their job or document correctly.
"VS were ordered and not taken"? What kind of ER is this?
I am nowhere near as good as our worst radiologist (who is, frankly... not great). It's not even close.
Up until that point, I’d never had any heart-related issues, nor does anyone in my family. Just two days before being admitted to the hospital with a suspected heart attack, I came down with food poisoning. It wasn’t pleasant, of course, but I thought it was nothing unusual—something a couple of days of rest and hydration would normally resolve.
Since my bloodwork at the hospital matched the expected results for a heart attack, and I underwent surgery, the doctors understandably focused on treating the immediate problem rather than identifying the underlying cause (I’m eternally grateful to the team and staff at St. Vincentius-Kliniken. I truly don’t think I’d be here without them).
That said, I’m glad to see this area receiving more attention. Hopefully, it will lead to further studies and the development of better strategies for prevention and treatment.
Most people assume that "heart attack" is a distinct clinical entity, but the majority (~80%) of elevated troponin levels are not exactly what comes to mind when people say "heart attack," but will often be described to patients as a heart attack (sometimes out of ignorance and others out of convenience, as the actual explanation for what is going on takes a lot more time and effort).