caraffle

This is fear mongering at best and unbelievable. Why would a surgeon know anything about anesthesia risk? Anesthesia regurarly cancels cases due to safety concerns - there's no "protocol" or "getting in trouble" (what does that even mean), that's standard of care. "Anesthesia" is a doctor too and ultimately holds the call on if they will put a patient under or not.

IMO the best way is to just pick a project and work on it. Using application notes and datasheets lets you piece together circuits, and you pick up design patterns along the way.

It's new but not as new as the article tries to make it sound. Has been known for a while and is in use. Further, it's not going to "revolutinize" anything, it's another incremental med that has shown improvement in outcomes. Just like beta blockers and aldactone, it buys you some small clinical benefit.

Show me a printer than can print 2000dpi. Small font also causes eye strain, I say all books should be in large font.

Just because they are worse for you doesn't make it so for everyone.

This shows clear ignorance of what radiologists do, it's like a fish telling someone how to improve land transportation.

For some reason CS people fixate on radiology for automation just because it is imaging, but there's a lot of context behind it. There's a reason a radiologist/pathologist is called a doctor's doctor, and no one in the field is worried about automation.

For perspective: Training to be a radiologist is 5+1 years, your family doc trains for 3.

Probably an anemia then! Carriers still have protective effects without too much of the bad, there may have been some precipitating event during your episode.

Any chance you were screened for anemias? Carriers for sickle, thalassemia,and G6PD deficiency all have malaria protective effects and ties in nicely with yellow urine and jaundice. Hemolysis increases urobilin in urine leading to a more yellow color.

These are pretty common in african populations so I wouldn't be too surprised.

There's a lot wrong with the medical field, but this is a ridiculous argument. Programming is hard, medicine is hard. But it's in different ways - it's definitely not transposable (obviously- you switched the other way). I say that as someone who worked in FAANG software and is now in medicine.

Equating salary to mental load is also factitious. Manual laborers work harder than all of us, maybe we should switch salaries with them.

I 100% agree with the difficulty of becoming a doctor. I disagree with the gatekeeping however. Ultimately it comes down to residency positions available, and funding is government limited. We're seeing tons of new medical schools opening, acceptance of the DO crowd, and still the system is getting more competitive.

And a physical exam? Who's going to listen to your lungs and heart, check out your throat, ears, nose, eyes? Those are invaluable in diagnosing even the most common illnesses.

Of course we have treatments and symptoms for many diseases. But many diseases present the same way. In fact many symptoms are a result of immune response, so naturally they are going to be difficult to differentiate. It's not because the physician doesn't know something. Further, a web based system would limit the amount of information a physician could get and be subject to the reporting of a lay person.

Overtreatment and overdiagnosis is also a thing. How would you like receiving thousands of dollars of testing every time you visited the doc?

There will be bad docs like in any field but its presumptuous to think most don't know what they're doing.

Apparently you're not familiar with the documentation burden in the medical field. EHR's don't diagnose for you.

There is no "true" intuition in medicine, just years of study and practice leading to quick recognition of common problems like any other field.

What? Do you have evidence there's a memory problem with the code as is?

Blind language allegiances are useless. All of them have their advantages and it makes no sense to claim one is superior.

Glioblastomas are what the name implies- tumors of glial cells. Neurons aren't involved in proliferation.

B12 deficiency doesn't cause pernicious anemia, pernicious anemia is a cause of B12 deficiency, its a GI absorptive disorder (lack if intrinsic factor).

Not sure how you plan on getting into medical tech without being OK with paperwork.

The paperwork is far from useless, traceability and documentation are important. Try to learn about the medical device approval process and FDA, and you might come to like the required steps, or at the least, understand it.

When people say "cell line" they mean a proliferation of a specific subclonal population in the lab.

Cancer cells in vivo are known to have clonal evolution [1]. This paper is specifically talking about in vitro growth on a petri dish. The problem is when a biopsy is taken it includes some cancer cells and some normal tissue. The cancer cells need to be isolated, then multiplied to have enough material to work with. This paper suggests this process results in heterogenous progeny - differing in key mutations related to immunotherapy.

(disclaimer: not anywhere near an expert, software guy in bioinformatics)

[1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3367003/

This is interesting to me because it gives one a way to evaluate if they are valuing something fairly (usually in comparison shopping) like mentioned with the monitor example. Keeping this in mind reminds you to determine the value of a factor independent of other products, thus assigning a significance to you on its own and at different levels. It's also an indicator of how knowledgeable we are about the metric.

For example: One can visualize 128 colors as being not that many. Once we get into the thousands this gets more and more abstract & less important.

Another: A has a 5ms response time, B has a 10ms response time. A seems better, but on its own each doesn't seem to make much sense - lets go learn more about what this metric means.

Another : A is 5kg and B is 10kg. A might seem better but when we look at each independently we look at why weight matters. We realize both are OK - a monitor isn't going to be moving around much.

Man I hate those connectors. I don't have a problem soldering most things down to 0.4mm pitch & 0402 components without magnification, but these connectors love to bridge. Either lay down a (thin!) bead of solder paste, or try drag soldering (I prefer this).

With LVDS, make sure to keep tracks short,have some impedance control (doesn't need to be super strict), and match trace lengths. One issue I had before was a clock (90Mhz I think) that wasn't quite in sync. Ended up ordering a new board with a 8 channel inverter, and snaking the clock through a few of the the gates to get a slight delay.

I don't think it's the same. arr[n] and [arr]n works because brackets simply expand to * (arr + n) in the first case, * (n + arr) in the second.

C++ dictates if a statement can be interpreted as a declaration, it will be (see "The most vexing parse"). Universal initialization was introduced to provide another way to ensure this doesn't happen.

https://softwareengineering.stackexchange.com/questions/1336...

From what I remember, T-cells (or was it B cells?) hang out in the lymph nodes.

What you're suggesting sounds like a count min sketch, like a 2D bloom filter.