Hacker News new | past | comments | ask | show | jobs | submit | 08-15's comments login

> Doctors know about Vitamin D.

Don't be so sure about that. When I first heard about the connection of D3 with the immune system, I asked a friend, who happens to be a cardiologist, about it. He said vitamin D prevents rickets, that's all. And an overdose produces arrhythmia, so be careful with the supplements. Indeed, that's the conventional wisdom found in text books.

According to the internet, a healthy immune system needs much higher levels of vitamin D than those necessary for a functioning calcium metabolism, and a D3 overdose is only bad if you have insufficient levels of vitamin K2. I don't know what to think about all of that. After all, my representative study with a sample size of one and no controls yielded no significant results.


Maybe you shouldn’t talk to a cardiologist about preventive medicine not related to heart issues………we have primary care physicians for that. Every preventative care doctor out there knows the benefits of vitamin d. It’s such a silly anecdote to bring up. And you don’t know what to think? Go read the research and make your own conclusion. I would never trust random people on the internet who make up anecdotes. It’s been proven that Vitamin D is a healthy hormone that is important to your well being. Go get it tested and then at least you will have a reason to do research.


I went to med school 10 years ago (did not complete the programme) and I'm a biochemist. Doctors definitely know about vitamin D, and if they don't then there's something wrong with them.


I was diagnosed with severe crohn's disease in the late 90s. Doctors started learning about Vitamin D and the immune system in the 2000s. My only specialist who knew about it in the 90s is now at an elite hospital. It was rare knowledge 20 years ago. Medicine is still pretty much stuck in the last century with nutrition knowledge. It's all about pushing pills for the most part. The synergistic study of different nutrients is still pretty lacking.

For example, most Drs now know about vitamin D. But do they know about A and K and the dosages and which minerals you should probably take with it when someone is extremely D deficient like in a lot of autoimmune patients? Probably not...

Do doctors know most patients with resections or digestive issues who are B12 deficient can absorb methylcobalamin sublingually? I've never met one that does.

I can go on. Most doctors understanding of B12 is still stuck in the 1970s along with most other aspects of nutrition.


The old-school, prevents rickets/400 in milk is enough, is what was taught for decades. The new-school, take a few thousand a day and it prevents winter respiratory infections is quite newer and less spread out.

Personally, I stopped having the vast majority of colds during the winter since starting D a decade ago. One or two colds since, and both were over in a day. Definitely a significant life improvement.

There are several dominant threads pushing back here on a professionally done study about the benefits. So no, the important information is not as widespread as you claim.


You may be confused. At least here in Germany, we (mostly) implement 2G: "Geimpft oder genesen." -- vaccinated or recovered. (Depending on context, "getestet", meaning tested negatively, is also fine.)

So no, "natural immunity" is not treated any differently from "artificial immunity", and it absolutely is about getting out of a pandemic without too many people dying. By the way, there is no difference. Immunity is immunity.


Indeed. That's why helmets are mandatory for motorcyclists. Helmets are to motorcycles as vaccines are to COVID. Neither guarantees that you don't die or need intensive care, but both reduce the likelihood.


I really like this comparison but it misses the main reason that this is such a huge issue: there are basically no downsides to wearing a helmet, but for some people vaccinations will cause health problems. I know that P(issues from Covid) > P(issues from Covid Vaccines) for almost all cases, but the downside is hard for people to ignore.


> Stigmatising obese people, people who drink alcohol, people who do extreme sports, people who have children late in life. Where does it end?

You sound as if you live in a weird parallel universe where we don't stigmatise those people.

It's not difficult to find people who think along all or some of these lines: Obese people are ugly gluttons, drinkers are a danger to others and themselves and have no self control, extreme sports athletes are crazy, people who have children in their forties are inconsiderate and will get retard babies.

The reason we don't get worked up about those as much as about covidiots, is that the groups you mention don't endanger anyone else. The one exception is extreme sports (think drag racing, not wingsuit flying), and that's why we require those athletes to buy insurance.


The fallacy here is the use of the word "we". The people trying their hardest to stigmatize anyone who doesn't like the COVID vaccine are the same ones saying that being obese isn't your fault and isn't unhealthy.


Nope, because according to me, if you're fat, it's because because you like sugar more than being slim, and if you're not vaccinated, it's because you can't do simple math.

Looking forward to statistics supporting your assertion.


I don't mean literally everyone. I just meant that I've noticed quite a correlation in one direction, but you used the word "we" in a way that only makes sense if there's a correlation in the other direction.


You are obviously an NF temperament, most probably the ENFP personality type.

Extraversion/Introversion is the first distinction of the Myers Briggs Type Indicator. I find it remarkable that exactly the people who get incensed at the MBTI "because everything is shades of gray and you can't sort people into neat 16 bins", are those who are at the very very end of at least two of the four scales.

> don't let over people tell you how to think and behave!

Ironic, isn't it?


INTJ last time I did it.

But then it varies depending on what mood I am in the day I do it.

That is my point - don't label people with "oh typical ENFP response!"/"You are ENFP - this is why you think what you think" It is unhelpful at best, and at worst a slippery-slope way of dismissing people's views and opinions - without extreme care and self-monitoring you risk (consciously or not) making the same snap judgements based on other aspects of people "Oh typical gender/race/religion/age response! This person is X so they alway do/think Y". Dangerous.


I will never understand the idea of "type". There are like billions people on earth and for some some reason all of them can be described as one of 16 types. Just that. There so many reasons that people do what they do and behave like they behave that you can't just simplify that to 16.


From https://web.archive.org/web/20140503013539/http://noticias.j... by way of Google translation:

"Meanwhile, the ownership of the clinic's assets was being discussed in court, and the cobalt 60 teletherapy unit was moved to the new facilities and the cesium 137 teletherapy unit was abandoned in its original place due to being seized."

Sounds like the root cause was stupid bureaucrats, but that must of course not be admitted in public.


Right, but that equipment should have been moved to the new facility before the old site was handed over to it’s new owners. If they’d done that the equipment couldn’t have been seized.

EDIT - All good points below.


In the linked article, IGR and a lawyer both claim that only CNEM could authorise the move.

And the "handover" to the new owners was very acrimonious, with the new and old owners fighting in court. What seems clear is that IGR lost access to the location and filed several complaints about the machine being left there.

If IGR was securing the machine and trying to get it moved before they were thrown out of the location and prevented from visiting it as they claim, I don't think they're to blame at all. Of course details are fuzzy on that.

---

EDIT: According to this court sentence [1], IGR never notified CNEM:

> Then, under pressure to leave the site, the IGR transferred its headquarters to another address, and ended up abandoning the obsolete Cesium-137 pump in the old building, without even notifying the CNEN or the State Health Secretariat of the fact.

> On 05/04/87, the demolition of the building began, by order of the former partner of IGR, AMAURILLO MONTEIRO DE OLIVEIRA, culminating with the almost total destruction of the original building, which left it without a roof, doors or windows, despite the existence of the aforementioned Cesium-137 pump on the site, without any warnings or notices.

---

EDIT2: According again to the court sentence, the demolition was ordered by former partner of IGR, who had to pay 100k for the whole ordeal.

> On 05/04/87, the demolition of the building began, by order of the former partner of IGR, AMAURILLO MONTEIRO DE OLIVEIRA, culminating with the almost total destruction of the original building, which left it without a roof, doors or windows, despite the existence of the aforementioned Cesium-137 bomb on the site, without any warnings or notices.

---

[1] https://jus.com.br/jurisprudencia/16292/sentenca-na-acao-civ...


The bureaucrats were acting at the behest of the landlord / property owners.


Not at the behest of The People? What a weird court.

But more importantly, "to seize" means to "take possession", doesn't it? And you need a license to possess a teletherapy machine, for the very good reason that the damn thing is dangerous. IGR had a license. The bureaucrats didn't. Neither did the new site owner, landlord, whatever you want to call them. They still took possession, by force.

Property rights are a set of rules. Nuclear safety regulations are a set of rules. These are not the same kind of rules, though. Not understanding the difference kills people. The court didn't understand the difference.


In this case, the dispute appears to have been a civil one between parties contesting control over the property: the former clinic operator and the landlord/owners of the property, the St. Vincent de Paul Society. The people had no advocate at that proceeding, and the court and authorities were unpersuaded by IGR and Carlos Figueiredo Bezerril.

Courts are normally given all but total immunity in all jurisdictions. I'd argue that the court and SVdP were criminally negligent here.

(I'm just reading these details now through the Wikipedia article. I'm interested in a more complete report, because quite clearly things were fouled up quite badly.)


In this blog post, senior engineer Rachel talks nonsense about normalization and promotes a bafflingly complicated solution as superior to a simple one, without identifying the actual fix, which appears to have happened accidentally.

In other words, with enough empathy and patience, a clueless rookie can grow into a clueless senior engineer!

Rachel usually makes more sense than that. That's why people are nitpicking implementation details.


Hah, pretty accurate and kinda funny, but could be nicer. I still make mistakes.


Meanwhile, Rachel posted an update. Apparently, the whole section about how "the system got reworked" doesn't describe the proper solution, but her own (Rookie Rachel's) attempt to fix it.

And in that context, everything makes sense.


I must be missing something, but the "solution" with the 3NF and five separate tables with their own indices seems artificial and like pointless overengineering. Isn't this solved by a single index?

Or maybe a relational DB is already overengineering. Using a hash table (some libdbm lookalike) to map (ip,helo,from,to) to (time) solves the problem, too, and doesn't have a low performance failure mode.

This doesn't change the major point about everyone having been a newbie at point, though.


Are there any libdbm-style databases that support "tuples" as keys and values, instead of plain "strings"? I've felt like I wanted them in some applications, but didn't want to stringify everything.


I'm not familiar with "libdbm-style databases", but CouchDB's map/reduce views allows you to emit any JS object as the key, like so

emit(key, value)

Eg

emit([0,"one"], 2)

And you can query by the value of the key.


DBM and similar databases are simple on-disk key-value stores. The use case is a lot like a SQLite, where you just need to put some data on disk and retrieve it efficiently later.

Can CouchDB be used in that fashion? Seems a lot more complicated, more like MongoDB than anything.


Definitely more complicated than a key value store, or sqlite, more like a distributed document database with (optional) map/reduce views (indeces) and more recently mongo-like indeces.

Best use case though, for me, is key/value durable data storage that you can sync (two ways, no need for master).

As for performance, its pretty fast, but not redis fast as data is written on disk using btree indeces. Retrieving multiple values (documents) with similar looking keys (ids) can be quite fast.


You can however cache values in 3NF better down the stack (i.e. you can cache a lookup of a string to a PK and then only use PKs down the line).


Or maybe not. It was Navy training that destroyed TMI-2.

Instead of worrying about the loss off coolant, the operators worried about the reactor "going solid", which is slang for "no steam bubble is left in the primary coolant circuit". This made sense on the small Navy reactors they were trained on, but on the large land based ones. Arguably, it never made sense to take a submarine engine and turn it into a power plant.


In April of 1986, the operators of a nuclear power plant turned of the coolant flow to their reactor under full power, just to see what would happen.

Nothing happened. The reactor just sat there peacefully doing nothing, because it was a fast neutron reactor, the EBR-2.

> they're more dangerous and still experimental

They were neither in 1986. But sure, let's build more "grid storage", which isn't even experimental.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: