> If and only if your job is to write tedious corporate pablum I disagree. Some background: I am a cloud security engineer (been in a senior security role for

> If and only if your job is to write tedious corporate pablum I disagree. Some background: I am a cloud security engineer (been in a senior security role for approximately six years). In my experience in the security field I have found that the best security engineers specialize in one or a few specific topics (e.g. systems administration, networking, reverse engineering, etc.) and are really valuable at those few things and then have a broad enough understanding of other security concepts that they can be generally useful in other topics they do not specialize in. Some of the most interesting presentations, documentation and conversations I have encountered has been when someone covers a topic I think I know well and breaks it down to such a fundamental level that "an idiot" could understand it. Typically, the intended audience for security content like this are highly technical individuals. Those who can "dumb down" a highly technical concept to any technical skill level are usually experts about that topic in my experience. But perhaps for genius-level individuals (a group to which I do not belong), maybe it is not useful to break things down. But for me, I know I find it useful when people don't make any assumptions about my knowledge.