A bit about me
I've spent the last several years working across AI, data, and security. Those used to be three separate jobs. These days they keep bleeding into each other, which makes the work more interesting and a lot harder to plan for.
A few things I've picked up along the way:
- I've built and shipped AI features, and learned that a demo working once tells you almost nothing about whether it will hold up in production.
- I've worked with data pipelines and analytics: cleaning messy data, chasing numbers that didn't add up, and finding out that "the data is wrong" usually means "our assumptions were wrong."
- I've done security work, including threat analysis and hardening systems. The part that stays with me is how little margin there is: an attacker only has to get it right once.
I'm not an expert in any of these. All three fields move fast enough that what was good advice two years ago is now the thing people warn you about. That's part of why I still like it.
Why I'm here
To share what I learn.
I've gotten a lot out of other people's posts over the years, especially the ones where someone explained something they'd just figured out. At some point I noticed I'd been reading all of it and writing none of it.
So that's what this account is for. I'll write about problems I actually run into in AI, data, and security work: what happened, what I tried, and what worked or didn't. I'll also write about mistakes, since those posts were always the ones that helped me most.
If one post saves somebody an afternoon of debugging, that's enough for me.
If you work in AI, data, or security, or all three, I'd like to hear what you're working on. Comments are open.
Top comments (0)