Your (a) and (b) do not nearly cover the scope of possibilities here. They don't even address the (more realistic) situation suggested video: You don't have to

Your (a) and (b) do not nearly cover the scope of possibilities here. They don't even address the (more realistic) situation suggested video: You don't have to be an idiot to have a less-than-complete understanding of the technical underpinnings of a project on which you're making decisions and to make suggestions that are impossible and, potentially, quite stupid from the point of view of someone versed in the tech. You also don't need to be undervaluing someone's skill set to see their lack of understanding of a project's limitations and requirements as a detriment and impediment to your progress; it is, and acknowledging it as such does not require being a jerk, nor does it necessarily make you a jerk. If you're saying "man, what an idiot you are" to people who suggest things that aren't possible, feasible, or sensible, then yeah, you probably have some growing up to do (of course, most of us do anyway). But that's not the same as addressing someone else's very real problem before it makes your responsibilities intractable.