The guy certainly sounds ridiculous.
Having said that, I've seen people with limited knowledge really mess things up. They know just enough to think they have the whole picture, and they ask short, pointed questions that really need a more thorough knowledge base to answer correctly.
For example:
"My building meets code, so I'm "safe", right"? (or, it's "earthquake-proof" or "fire-proof", right?)...
A true engineer's answer would discuss the nature of risk, maximum probable loss, and even the very definition of the word "safe". Further discussions may include nuances about what is considered "safe" for different kinds of users (children vs. adults). You may need to clarify the safety issues of furnishings within the building, etc.
But if you give a long answer in a public hearing, then you're a boring windbag who can't get to the point.
If you give a short answer ("trust me, I'm the expert"), you come across as rude and condescending.
Anything in-between these two extremes, if not carefully nuanced, can look like you're weaseling or hiding something.
The short versions usually involve one of two responses:
1. Explaining that engineering often involves complex and interactive variables, like solving a Rubik's cube, and then ask if they want to set up a separate hearing to get a fully informed briefing -- (almost no one takes up my offer).
2. Defining the trust required in deferring to a professional.
In my example about 'earthquake-proof', I try to answer with a short analogy: "My car is probably more earthquake-proof than any building, but if the ground opens up underneath it and it falls into a giant fizzure, it may stay in one piece, but I've still got big problems down in the bottom of the pit. No one can guarantee safety against forces of nature - -all we can do is minimize risk, and build it as if it is our own loved ones are going to live there. I can tell you that when the next big quake hits, I hope I am in THIS building that we're talking about."