I think Dan's blog is largely pitched at other professional educators. All professions develop their own technical vocabulary.
As an analogy, I recently enjoyed an article about the implementation of the v8 garbage collector by Jay Conrod: http://jayconrod.com/posts/55/a-tour-of-v8-garbage-collectio...
Here's a sample paragraph:
"Distinguishing pointers and data on the heap is the first problem any garbage collector needs to solve. The GC needs to follow pointers in order to discover live objects. Most garbage collection algorithms can migrate objects from one part of memory to another (to reduce fragmentation and increase locality), so we also need to be able to rewrite pointers without disturbing plain old data."
I think the article is an excellent piece of technical writing, but it would also be reasonable to say "the professional compiler engineer dialect of English is not very approachable to the layman."
That said, good communicators need to be able to change their presentation based on the audience, and it's too bad that the people at the meeting you mention couldn't find a common vocabulary.
If you want to see something by the author of this post that is pitched at the layman, he made a very nice TedX presentation a few years ago:
http://www.ted.com/talks/dan_meyer_math_curriculum_makeover?...
On the other hand, only maybe 1% of the population has to suffer thru garbage collector theory in CS classes, and of that 1%, maybe only 0.0001% ever implement a GC "in the real world" and can understand that post. There just aren't that many GC programmers and there are a lot of humans in the general public. In that case jargon is perfectly acceptable, even expected. Also the core of a programmers job is rarely making public presentations.
We compiler guys do that on purpose in order to keep our salaries high!
The professional educator dialect of English is not very approachable for the layman. To many people it sounds like somebody throwing out $10 words to make the arguments sound more intelligent.