I'll also point out that the vast majority of fees paid by crypto users are paid to Ethereum, which seems fairly close to allowing us to perform a fundamental value analysis:
Post-merge, these fees would go to holders of the currency.
Not a drug I've looked into! I ended up confining my research into FDA-approved weight loss medication, so I probably missed a number of non-FDA-approved medication that also works for weight loss.
I suppose. But it's also true that you should minimize the number of debilitating medical conditions you're suffering from long-term.
Which brings us back to the thing where we end up having to choose between a chronic condition which is heavily correlated with a whole bunch of secondary health problems and reduced life expectancy, and being on a drug from which we have not (yet) observed long-term ill effects.
The back-of-the-envelope life expectancy calculations were mostly just there to point out that under most plausible assumptions, the risk/benefit calculations seem lopsided to the point where it shouldn't be a terribly difficult decision.
Whoops, sorry, I don't actually know anything about ECA. Possibly that's how it works, at least partially! I'm pretty sure it's true that stimulants are appetite suppressants, but it's also possible it has another mechanism of action having to do with non-exercise activity thermogenesis or similar.
Anyway: the way I was thinking about this is, obesity is caused by excess calories. That being the case, there's no particular reason to anticipate obese people wouldn't be getting appropriate amounts of fiber/micronutrients/etc; or at very leas...
I feel my disclaimer in the post:
>[Note: as pointed out by comments below, extrapolation to life-years saved is very speculative, since all the studies on this in humans are going to be confounded all to hell by healthy user bias and socioeconomic correlations and the like. That said, it feels like a fairly reasonable extrapolation given the comorbidity of obesity to various extremely problematic medical conditions. Be warned!]
should be sufficient to exempt me from charges of "pretending to know things."
The confidence intervals thing is prob...
It seems like given the enormous amounts of blood, sweat and treasure that have been expended in the investigation of long and short-term effects of particular diets, probably the most consistent result is that the null hypothesis prevails for almost all dietary interventions that don't modify caloric intake.
This is most dramatically illustrated by the Women's Health Initiative study, a very large-scale RCT of low-fat diets. A couple of representative results are at https://pubmed.ncbi.nlm.nih.gov/16467234/ and https://pubmed.ncbi.nlm.nih.gov/16467232/ an...
No. I compulsively use the refactor/rename operation (cntrl-shift-r in my own Visual Studio setup) probably 4 or 5 times in a given coding session on my personal Unity project, and trust that all the call sites got fixed automatically. I think this has the downstream effect of having things become a lot more intelligible as my code grows and I start forgetting how particular methods that I wrote work under-the-hood.
Find-all-usages is also extremely important when I'm at work; just a couple weeks ago I was changing some authentication logic for a datab...
I like type checkers less because they help me avoid errors, and more for ergonomics. In particular, autocomplete-- I feel I code much, much faster when I don't have to look up APIs for any libraries I'm using; instead, I just type something that seems like should work and autocomplete gives me a list of sensible options, one of which I generally pick. (Also true when it comes to APIs I've written myself.) I'm working on a Unity project right now where this comes in handy-- I can ask "what operations does this specific field of TMPro.Text...
I've found it quite useful for debugging issues in writing Azure ARM templates (declarative JSON documents describing architectural components.) "This ARM template failing with this error message" is something it's able to debug and correct easily, though it's also gotten a lot of API details wrong. It can correct itself afterwards, though, if told the new error message.
It's a very trial-and-error process, but one which proceeds rapidly.