[quickthrower2]

The flip side is imagine a project manager did this to a programmer or architect. The programmer would constantly need to explain why the blog post they read dated 2013 about how hadoop makes everything faster is wrong, or how that AI paper is bullshit and designed to get someone grant money. Or how someone else’s experience with Azure was great because they just shifted all their Windows stuff to it. So that could kind of stuff get frustrating for the expert.

[abecedarius]

It's interesting to imagine doctors understanding humans and their pathologies nearly as well as programmers understand the systems they work on. My guess is that'd amount to an incredible upgrade.

(Yes that level of understanding is often quite poor in absolute terms.)

[Workaccount2]

But that's part of the issue, I'm not reading a blog post from 2013, I'm reading recent studies in top shelf medical journals with clear conclusions.

I may not understand the minutia of the study, but if the conclusions are "60% of people with X showed the underlying cause Y", and my doctor is saying "I have never heard of any possible association with Y, and Y has no possible connection anyway" then I feel pretty confident that the doctor is out of touch.

Rather the doctors take should be "Please send me the studies and I will review them with my actual medical knowledge" or really "I need to review the literature on this patients illness so I can be up to date while treating them for it"