I think your example actually proves the point. Everything your doctor said has been known and codified in medicine for close to 100 years. So while the specif

I think your example actually proves the point. Everything your doctor said has been known and codified in medicine for close to 100 years. So while the specific definitions may be missed, it's still followable for a lay person, because it's connected to concepts they get (cell, disease, antibody, intravenous, maybe even receptors.) If you asked an average adult to translate that sentence, I bet it would come close to your doctor translation, minus the side commentary on costs. Certainly a doctor in another field, say, a podiatrist or even just a first year resident, can follow along with what the immunologist said. Whereas software is such a vast body (pun intended?) That nothing translates. DevOps interns, analytics architects, experience designers, and black hats have entire worlds of jargon to decode. But people pretend all the time it's all just software and if you're good at Angular you'll be good at embedded computing or if you're good at data modeling you can pick up machine learning.