"Woo Wars" - What is "Woo"?

[IdaBriggs]

122. ROFLMAO!!!

This might be a "you say potaTOE and I say potaTA" situation, and maybe you have been gifted with users the likes of which I've never met who provide perfect specifications ---



Or maybe you are just in a feisty mood and want to argue semantics. As I said, when code doesn't do what I expect it to do, my analysis always starts with WHY. Sometimes it turns out to be programmer error (don't tell - it happens!), and sometimes we discover the user "forgot" to tell us about possible options (because they happen so rarely) and sometimes somebody who didn't know what they were doing put in crap code before fleeing for greener pastures.

It is all okay.

My original point with the analogy is that physicians aren't trained for that type of problem solving; when patients "miraculously" get better, they stop coming to the doctor's office, and no one makes a note saying "hey, Joe was supposed to die two years ago and he didn't - anybody check into that to see if he did anything we might be able to repeat on someone else?"

You might think they do, but they don't. And if Joe does come back and say, "well, I started fill-in-the-blank" he will get patted on the head in a condescending manner, called "lucky" and ushered out the door so his doctor can get to the next patient.

People get busy, and who has time to investigate stuff like that?

But it doesn't invalidate the fact Joe didn't die - it just means they haven't gathered and analyzed the data. Researchers in the proverbial "ivory tower" probably don't even know Joe exists, while the clinicians are still going to reach for the "proven" procedures EVEN IF THEY HAVE A HIGH PERCENTAGE OF FAILURE because honestly, they have no accurate/reliable data or education about "Joe" - he has already moved on with his life.

I am NEVER going to med school, but I understand system design. I have also spent the last six years learning about these issues. Frankly, medical politics makes corporate politics look simple!