If you wouldn’t mind indulging me, I’m very curious how you came to be of that opinion

Ask Claude to set up a cron job to print it daily

C is "just another abstraction on top of what we already had" (Assembly). Doesn't mean it's not useful

Eating butter is good for your heart. As long as your triglycerides and HDL (AKA "good cholesterol") are low, elevated LDL (AKA "bad cholesterol") is associated with lower all-cause mortality.

Maybe in some cross sectional or cohort studies with poor adjustment models we might see such a signal? Several states of poor health drive LDL down because of those diseases (e.g. having cancer can result in lower LDL, having a heart attack can massively lower LDL), so if we look at study designs that don’t take this into consideration, it can appear that high LDL is protective because of reverse causation.

However, I’m not aware of any evidence that takes this into account showing higher LDL associated with lower ACM. What’s your evidence for such a claim?

“… higher TC and LDL-C were independently and paradoxically associated with lower risk of all-cause mortality and longer survival time in men”

https://journals.plos.org/plosone/article?id=10.1371/journal...

Yeah, this is a good example of what I’m talking about - you take a bunch of people at risk of diseases that lower LDL-c as a result of having that disease.

They actually acknowledged that reverse causation is a risk here and so ran a sensitivity analysis by excluding patients with less than 5 years of follow up (a nice way of saying “patients who died within 5 years of the LDL-c reading”), the idea being that if these results were likely being driven by reverse causation, you’d expect to see an attenuation of the results.

I’d point out that even if we didn’t, five years is a bit of a weird cutoff - plenty of LDL-c lowering diseases take much longer to kill the average person. Moot point though, because excluding those participants attenuated the result to the degree that the association with LDL-C and mortality became statistically insignificant.

Quite why the authors said “we’re aware that reverse causation is a risk factor, let’s run a test to check if it’s likely influencing the results” and then completely ignored the fact the results suggested it was influencing the findings, is anyone’s guess.

So yeah, basically huge confounder seems to be in play that likely explains the “paradox”.

Thanks I genuinely appreciate your input

Welcome! Thanks for being pleasant.

I think you got that mixed up.

I think he is being facetious

I've spent enough time around keto people to invoke Poe's law on that one.

And you’d be right. I have linked a study supporting my claim above, you’re welcome to tell me why it’s invalid.

Have done so! It’s basically just what I said - signs point to reverse causation.

At the time that’s precisely how it felt though. So much so that I personally felt it wasn’t worth it relearning everything. Had shipped several projects with AngularJS at my very first dev job, and have never written a line of Angular v2+

It confuses me when people talk about frameworks as being totally different. They solve the same problems, slightly differently. It’s not a big lift to learn a new one if you are familiar with one or two already.

That might be generally true for frontend frameworks these days, because they’ve all converged around the same ideas. But in the mid 2010s, Backbone was very different from jQuery, which was very different from Knockout, Ember, ReactJS etc. certain frameworks embraced certain programming paradigms, others embraced others.

Some of my colleagues didn’t make the jump. Those that were the most into AngularJS back then are still writing Angular apps today.

I tried this with the kind of merge conflict I'd expect it to solve automatically, and it didn't. Is it supposed to work while rebasing, or is it strictly for merges?

Thanks for trying it! Would love to know what the merge conflict looked like, if you can share the repo or a minimal repro, I'll dig into why it didn't resolve. That kind of feedback is exactly what helps us improve.

For whatever reason, there are extraordinarily few references that I come back to over and over, across the years and decades. This is one of them.

Tangentially related, there is much insight about Unix idioms to be gained from understanding the key layout of the terminal Bill Joy used to create vi

https://news.ycombinator.com/item?id=21586980

Not 'man ascii'?

Indeed, the last sentence on the page is "Use it with caution, and at your own risk."

Which is what the comment you’re replying to means by “invent”.

Yeah as an Australian I thought this would be the case and I'd have to stop using Facebook etc (because there's no way I'm uploading ID or whatever to keep using it). Turns out because I created my account over 16 years ago they're happy to assume that I'm at least 16 years old. Which makes sense but I didn't anticipate it going that way.

Hmm yeah but that's a pretty long time.

Also what we see here in EU is that some sites (e.g. porn sites who already have to use age verification) demand it periodically, probably so you don't create one and give the credentials to a minor or something.

In fact it's becoming pretty insane here, even my bank and phone provider want me to come in and show my ID every few years. As if I suddenly became another person?? I kinda snapped at them last time because of these retarded processes and I felt bad then because I know it's not the employee's fault but it's just so ridiculous. I'm getting so sick of this pervasive tracking and monitoring in society with everything we do.