A cure for cancer: how to kill a killer

Re:A cure for cancer: how to kill a killer by vectorEQ on Wednesday November 07, 2018 @07:15AM (#18398618)

killing things is bad mkay. prevent instead of cure. solve the root cause.

" “The tidal wave of data is still teaching us fundamental concepts about the interaction of the human immune system and human cancer.” "

So, if they still learning fundamentals. -> impact of actions based on inaccurate or incomplete knowledge, is unknown.

in programming this kind of practice would lead to bugs / undefined behaviour etc. - imagine what kind of shit that would mean for human health...

It'd be nice if they had cancer prevention studies instead of cancer cure studies. kthx

[ Parent | on HN ]

Re:A cure for cancer: how to kill a killer by nradov on Wednesday November 07, 2018 @08:45AM (#18399023)

Many of the DNA mutations which cause cancer are essentially random and impossible to prevent. The human body is not a simple deterministic computer system.

[ Parent | on HN ]

Re:A cure for cancer: how to kill a killer by conjectures on Wednesday November 07, 2018 @09:56AM (#18399497)

If this were true, all I could express would be gratitude biologists don't think like programmers.

[ Parent | on HN ]

Re:A cure for cancer: how to kill a killer by adrianN on Wednesday November 07, 2018 @08:50AM (#18399047)

Often the alternative to trying a treatment that you don't fully understand is death.

[ Parent | on HN ]

Re:A cure for cancer: how to kill a killer by AnimalMuppet on Wednesday November 07, 2018 @07:48AM (#18398738)

While we're still trying to sort out the root causes, a lot of people are dying. So we're trying to stop them from dying, even while trying to find root causes. (Society as a whole can work on more than one thing at once.)

[ Parent | on HN ]

Re:A cure for cancer: how to kill a killer by bananadonkey on Wednesday November 07, 2018 @08:07AM (#18398833)

When dealing with a software bug you have to reproduce the issue before you can definitively "fix" it.

[ Parent | on HN ]

Re:A cure for cancer: how to kill a killer by Koshkin on Wednesday November 07, 2018 @08:48AM (#18399032)

Not true. (It is often possible to understand the cause by just looking at the damn code.)

[ Parent | on HN ]

Re:A cure for cancer: how to kill a killer by barry-cotter on Wednesday November 07, 2018 @09:34AM (#18399334)

Humans, and every other life form have an undocumented, undesigned self executing specification that consists entirely of the most reticulated, self referential spaghetti code compatible with successful reproduction and it’s not just riddled with Heisenbugs, they’re core parts of the machinery of how everything works. We’ll get there eventually but it’s going to take an exceedingly long time.

[ Parent | on HN ]

Re:A cure for cancer: how to kill a killer by asdff on Wednesday November 07, 2018 @01:13PM (#18400957)

You are looking at human readable and annotated code, not what is compiled for the computer to run. Imagine finding bugs by looking at binary. DNA is more complex than 1 or 0, it could be ATCG. There are 3.2 billion nucleotides in the human genome, and we are still a long way from understanding the nuances of the DNA 'programming language.'

[ Parent | on HN ]

Re:A cure for cancer: how to kill a killer by qubax on Wednesday November 07, 2018 @09:24AM (#18399266)

Maybe for superficial bugs in small toy programs. But a real bug in any sophisticated program requires a bit more than looking at the code most of the time. User feedback, log/trace data, performance data, system events data, memory dumps, etc.

Of course the bug could be in proprietary software your code is using. How would you fix that by purely looking at your own code?

[ Parent | on HN ]