Why I'm writing this down

Most “welcome to my blog” posts could be deleted and nobody would notice. I’m writing one anyway, because I want a straight answer for future-me about what this place is for before I start filling it with content.

The short version: I forget things. Not the big shapes of ideas, but the specifics. The difference between a nonce and a salt when someone asks me cold. The parts of a TLS handshake past the steps I touch every week. I’m not trying to stop forgetting. I’m trying to make it not matter. Put the details somewhere solid and I don’t have to keep carrying them around in my head.

Writing is the cheapest way I know to find the holes in my own understanding. You can read a paper, nod along, and walk away sure you got it. Then you sit down to explain it in plain English and find the step you skipped. An explanation that falls apart on the page was never solid in your head. It only felt solid.

I’ve spent eight years in product security, mostly around embedded systems, vehicle telematics, and the cryptography that holds those together. Long enough to be useful. Not long enough to stop being surprised. Security is a big field, and the longer I work in it the more I see sitting just outside what I deal with day to day. I’d rather keep widening what I understand than settle into one well-worn lane, and writing about the parts I’m reaching for is how I get there.

So the rule here is simple. I write about things I’ve learned, things I’m actively trying to learn, and things I have an opinion about. That last category is the fun one. Sometimes the documentation is wrong. Sometimes a “best practice” survives only because no one has checked whether it still holds. Mostly I just want to work these things out properly, write what I find useful, and hope some of it turns out useful to someone else too.

That’s the whole pitch. No content calendar, no growth strategy, no promise to post every Tuesday. Just a place to think things through and keep them where I can find them again.