[sl1ck731]

I tried doing what the OP described, become some interesting blogger person, but threw in a 2 or 3 line article about some mundane error I had with a tool one day mixed in with all the other wordfluff.

Surprisingly the error code drew a ton of traffic compared to anything interesting I could have possibly thought about writing.

[kaycebasques → sl1ck731]

You stumbled upon a technical writing best practice. Always include the exact error code and message in documentation because people often search for that exact string.

[bookofjoe → kaycebasques]

Analogous: supply a link rather than tell someone to look it up.

[DrScump → sl1ck731]

and/or the exact text of the message. A vague search is fine if there are few matches,but there's a lot of cruft out there.