Earlier quoted context omitted.
I think it is measure of time, for author it looks simple to put everything in few words instead of having long explanation, I find this typical in IT, where my coworkers all the time trying to compress explanation in fewest words possible. Maybe laziness or type of optimization, but usually back fires as other people ask you multiple questions, arising from their own point of view.
[flagged]
I know many people who would consider themselves non-technical, yet who certainly take the time to learn complex concepts. Some of those are indeed technological concepts.
> I try to give short simple examples because when I try to tell people the truth their eyes glaze over and their brain turns off while the nerd talks his techno jumble.
The short simple examples you give are also truthful, correct?
Perhaps the additional information you'd like to explain simply isn't needed for the other person's goal.
A great way to have both technical and non-technical people's eyes glaze over is detailing all kinds of minute details before describing some of the high-level goals or giving context as to why you're getting so deep into the details. As you mention, simple examples can get a lot across, and can be a springboard to more questions being asked, to allow the other person to decide what depth of knowledge they would like to know.
The non-technical person you're talking to may very well have the patience to learn the deep technical truth you'd like to explain, but they may have no reason to know it. In the scenario you're thinking of, you're doing the technical work, not them, correct? So why would they need to know deep technical details? A basic outline, with some corner cases pointed out, is likely all they need. Not because they don't have patience to learn what you're explaining, but because they have other things that are more important to their or your organization's success.