|
|
|
|
|
by mrlongroots
30 days ago
|
|
> I think „the diagnosis” is over simplification and lots of professionals would disagree that there’s always a single one. "The Diagnosis" does not mean "one root cause". Situation: my car has some unexplained vibrations.
1. Mechanic A says that it is the engine mounts
2. Mechanic B says that it is some weirdness in how the exhaust assembly is hanging to the underbody
3. Mechanic C says that it is just my wife farting I replace engine mounts and 40% of the problem is reduced. I then drive without my wife and the remaining 60% is solved. "The Diagnosis" was: 40% mounts, 60% wife, 0% exhaust. There is always one "The Diagnosis". |
|
No, that is not true at all.
This is a kind of thinking a lot of programmers fall prey to. The real world, outside of code, is a very fuzzy and inherently analog place. There is very rarely one in any complex system having a complex problem needing a complex solution. At some point even the definition of diagnosis gets fuzzy.
The best demonstration of this in medicine is probably the DSM-5. What, really, is the difference between Narcissistic Personality Disorder and Borderline Personality Disorder and Generalized Anxiety Disorder? Can they overlap? (Yes.) How do you treat them? (It's not easy.) What about depression: how do you tell if someone has Major Depressive Disorder or Bipolar Depression? (Again: not easy.) In some circumstances the only way to tell the difference between the two is what drugs work: if antidepressants help, it's Major Depression; if mood stabilizers help, it's Bipolar Depression. It's kind of odd to define a One True Diagnosis by "well we fixed it this way, so it must have been that", with no other way to do it, isn't it? (What if both work? What if one works for a while, then the other works? What if treatment with antidepressants induces bipolar (hypo)mania? All of those happen!)
And that's just a few examples.