After forcing myself to learn and adapt to some note-taking system, I too didn't find it useful for me yet. But i keep pushing myself through because I still believe that there must be some value that I could take from taking notes. Just I didn't find a system that suits me well...? One thing that i find the real benefit/value from all this learn and adapt is "writing as a way to think" (is it by feynmann?). When doing complicated work, writing really help to ease your cognitive load and help you find the gaps in your line of thought. But, I couldn't find a suitable method when dealing with general/every day note-taking. I still have that "graveyard for thought" problem when writing general notes
The source article[1] suggests that (in my own words) it may have to do with several kins that were brought together and tried to seal their bond by assembling a fictive individual from several deceased relatives. Or that an original important burial site was disturbed and they tried to restore the body.
Incidentally, my Windows installations never self destruct, and I have used the product on several versions in the last 25+ years (since W95). My Linux installations however have, for example by standard updates.
HTTPS when used in the ubiquitous manner it is now always strikes me as unnecessary complexity and tedium, and reasonings like yours addressing them with even more complexity and tedium.
It happened that the last S changed from "stupid" to "secure".
If I use HTTPS I can safely enough connect to my home services through an open cafe Wifi, for example
I’ve been using caddy for a year which does everything for you. Basically nginx/haproxy but with https built-in via LE, no fiddling about with cert files and brittle LE scripts, also supports subdomains equally easily.
How bad is the HN hug of death btw? My laptop can serve 200k QPS per core. I can't imagine HN is that much more intensive? Are 1vCPU VMs just that much worse?
Yes, they are much worse than bon-fide actual single cores on most recently purchased laptops. But also, the HN hug of death mostly happens with tiny non-static sites that are sloppily hosted. If you're serving static assets it's hard to "hug of death" a Casio watch.
M3 at work, Acer Swift 3 at home. Both are comparable in that regard. You can do 200k QPS of actual work (a little protobuf parsing, a little old-school ML, handling the networking, a little HTTP1.1 parsing, ...), more if you just want vanity metrics, just by wrapping something like uSockets [0] and not doing anything to explicitly pessimize the system.
You can do better with a hand-crafted solution, but most projects don't need anything fancier.
