Earlier quoted context omitted.
And this is why we can't have nice stories. I felt for the author as I got deeper into the faq, and recognized this pattern of cynicism, then decided the author was so generous and thorough, not out of obligation (make the emails stop!), but because that is the type of detailed person he is -- and good at dinner parties too!
Writing stories for a technical audience is tricky. I've been doing it for going on 10 years now, and I'm still not very good at it. A critical rule, however, is to omit detail, (a reader is unlikely to question an explanation they make up themselves) and most importantly, to omit details you know to be wrong . (It is impossible to nitpick a statement that is never said) An odd feature of our campus network at the ti…
It's also a reason why short business emails are better than longer ones. You can always go more in depth. It takes skilled restraint to touch on only the most relevant details without losing the larger point.