[brightball]

I’m in the middle of writing a series of security articles on my blog and a couple of people have told me that some of them are too long.

They are long because I was trying to be thorough, but more so I was trying to make sure I pre-addressed all of the arguments I knew would come (particularly in my enterprise DMARC deployment article).

I realize that what the author talks about here is part of why I do that.

[eyeareque]

I recommend posting the articles as you intended to. You’ll never make everyone happy anyway.

[catach]

Very much so. Write first for yourself. Write to your own standard of quality. A borrowed standard is one never fully understood, nor knowingly achieved.

[brightball]

I definitely did that. Just in reading this guy I realize I'm trying to logical address arguments I know will come.

Don't know that it's actually due to HN feedback or just knowing how internet discussions tend to go.

[dumpsterdiver]

Imo, as long as you organize your writing elegantly, it doesn't matter how long the final product is.

As a reader, I really appreciate the table of contents.

Maybe what your friends meant was that your piece was too long without a table of contents, from which they could jump to a place for reference, or skip it because they were already familiar with the material.

[brightball]

That's possible. Here's the Enterprise DMARC if you're interested.

I probably should add a TOC. I don't largely because it's setup to flow and I don't really want people to skip to a specific section.

https://www.brightball.com/articles/enterprise-challenges-wi...