Every blog starts with one of these. So, let’s do it.
The content
The conventional move is to spend 400 words explaining what the blog will cover, promising to post consistently, and not-so-subtly implying that what I share will be worth reading. But I’ll spare you… two out three.
This is a place for things that don’t fit anywhere else. Security observations too opinionated for documentation. Engineering notes too half-formed for a case study. Thoughts about words and punctuation that will delight approximately six people (which still might be an ambitious estimation).
The title
In cryptography, pseudorandom describes something generated by a deterministic algorithm that appears random and unpredictable.
My thoughts work a bit like that. There are underlying patterns — security, writing, the places they overlap — but the output will seem unpredictable. Some posts will be technical; some won’t. Some will be long; most won’t (you’re welcome). And I reserve the right to lament the use of “text” as a verb if the mood strikes.
The writer (briefly)
As a security engineer and former technical content writer, I believe both crafts are more related than most organizations treat them. About has the longer version if you’re ever curious.
The expectations
Do me a solid and keep them low. I’m an intense self-oriented perfectionist who believes a blank page is better than an imperfect one. That said, I’m working (hard) on that — ship and iterate, right? Thus, here we are.
Thanks for joining me.