I recall someone was analyzing the refractive index of various tissues in order to tighten the target area for multi beam radiation therapy. Particularly for brain cancers. By hitting from multiple angles the dosage in surrounding tissues is lower, and by calculating how the head lenses the beam you reduce the high dose area in the middle, like a 3d Venn diagram.
But I don’t remember is whether that experiment became SOP or not.
Seems not in this case. But I believe the use case was deep brain tumors, like the hippocampus, where any beam alignment problems could be life altering.
There was also a study that showed that chemotherapy efficacy was enhanced by fasting before treatment.
It seems that when calories are scarce, healthy cells turtle up while cancer cells keep consuming, so fasting reduces absorption rates in healthy tissues and thus collateral damage.
Healthy cells CAN turtle-up, whereas cancer cells engage in unregulated reproduction. Also, some cancer cells can only consume glucose. Which, in a fasted state, would mean that the majority of energy would be in ketones(if the individual were metabolically healthy), starving the cancer cells to death.
Because the cancers cells adapt! (fast reproduction and high mutation rate of the cancerous cells make that process quicker than antibiotics resistance)
Please don't throw around random "a study that showed" about cancer treatments and chemotherapy. If you really think it needs to be shared, share the study and while you're at it, check in with a good oncologist or knowledgeable friend too. In my ~10 years of enduring chemo and other treatments, the amount of garbage you have to wade through from "well meaning" anecdata like "wheat grass" or "smoke huge bongloads" or "don't eat sugar" makes an already horrible process worse.
And yes I checked this with my onc at MSK. Dietary glucose in particular -- if you cut out enough sugar to starve cancer cells you would be doing lots of damage elsewhere as well.
Some years later, I interviewed at Knight Capital, just a couple of weeks before their blowup. (Dreadful interview at which I did dreadfully, being asked to write C _over the phone_ by a supremely uninterested engineer. Quite a red flag in retrospect.)
At this point about 80% of my interaction with AI has been reacting to an AI code review tool. For better or worse it reviews all code moves and indentions which means all the architecture work I’m doing is kicking asbestos dust everywhere. It’s harping on a dozen misfeatures that look like bugs, but some needed either tickets or documentation and that’s been handled now. It’s also found about half a dozen bugs I didn’t notice, in part because the tests were written by an optimist, and I mean that as a dig.
That’s a different kind of productivity but equally valuable.
I wonder if the bad traffic overwhelmed the good traffic enough that it's simpler to pick out some of the good traffic from the bad and replay it rather than spot all of the bad traffic.
Honestly, since I'm never really in a position to see much of that money, at this point I'd be more concerned about my coworkers. And while that typically correlates with the amount of money you either have or receive, they're often out of balance one way or the other.
reply