On: All you ever wanted to know about building a secur...

[jgrahamc]

The inclusion of the large graphic taken from a pornographic web site is not necessary (he could just write a single paragraph describing the potential to discover subscribers of porn sites) and shows poor judgement by the writer.

[gizmo686 → jgrahamc]

The style of the article was showing screenshot examples of relevant sites. That may or may not be the most productive use of screen space, however the porn screenshot fits in with the other ones.

Just to be clear, I think the inclusion of screen shots is an excellent use of screen space.

[jtheory → gizmo686]

Screenshots are useful. But it would have been trivial to keep a technical article SFW.

As-is, this is a solid article that I can't send to my team because of that one poor choice.

Here's why:

1) I don't know the personal histories of everyone I work with, and it's none of my business (they aren't expected to tell me).

2) Some people would be seriously distressed to have their boss or co-worker email them anything with remotely sexual content.

3) I can't reliably identify who these people are, and so I simply shouldn't send anything with sexual content to co-workers/employees.

Doesn't this same logic apply to just about everyone?

[yock → gizmo686]

Screenshots are great; however, that particular screenshot could have been heavily redacted for the benefit of those reading in a professional environment.