This is a learning journal. I’m writing as I learn, not after I’ve figured everything out.
Why this exists
Most technical blogs post polished solutions to solved problems. That’s useful, but it skips the messy middle — the failed attempts, the confusing documentation, the moment something finally clicks.
I’m documenting the actual learning process: experiments with cloud infrastructure, working with AI coding tools, trying new DevSecOps approaches. Some posts will be “here’s what worked,” others will be “here’s what I’m trying to understand.”
What I’m focused on
Right now I’m working with:
- Cloud infrastructure — AWS, serverless patterns, CDK, infrastructure as code
- AI-assisted development — Claude Code and how AI tools change workflows
- Security tooling — SAST/DAST, supply chain security, shifting security left
The common thread: I’m building things, breaking them, and writing down what I learn.
Format
Posts will be short and focused. If I can’t explain it clearly in 500 words, I don’t understand it well enough yet. Code samples when relevant, but not for decoration.
No “stay tuned” promises. If I write something useful, you’ll see it here.