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.
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.
Surprisingly the error code drew a ton of traffic compared to anything interesting I could have possibly thought about writing.