I’m Trevor Oke. I came up through software development, spent seven years in cloud operations, and crossed into security a few years ago. Self-trained throughout — no cohort, no certification path that preceded the work.
Before any of that I was a soldier. The operator’s instinct that came with it never really left. I think in outcomes, not process compliance. I’m interested in what actually holds under pressure, not what passes an audit.
I also make things — leather goods, block prints, music. The maker’s instinct and the engineer’s instinct turn out to come from the same place. You learn how something works by building it, breaking it, and building it again with the failure in mind.
I write here because it’s the calibration I couldn’t get any other way. When you’re self-trained and working without a peer cohort at the right altitude, you develop positions in a vacuum. Publishing is the fix. Every piece is something I needed and couldn’t find.
The target reader is roughly me, a few years ago: technically fluent, resource-constrained, building security posture without an enterprise budget, trying to figure out what actually reduces risk versus what checks a box.
I’m on Mastodon at infosec.exchange/@trevoroke.