Software engineer, Scrum Master, and pragmatic problem-solver. I write about development, DevOps, career growth, and finding balance in tech — plus recipes that actually work when you need fuel for a late-night build.
Craft, leadership, agile practice, and the quieter work of staying whole while you're doing all three.
Modern practices, automation, and tools that make coding more efficient and teams more productive.
Navigate tech with insights on leadership, advancement, and building meaningful professional relationships.
Strategies for Scrum mastery, agile transformation, and creating high-performing development teams.
Mental health, work-life balance, and sustainable habits while thriving in a tech career.
Making distributed teams actually work — home office setups, async communication, and staying connected.
Honest reflections on life, identity, growth, and the messy stuff that shapes who we become.
I was in an architecture review a few years back. Fifteen people on the call, half of them senior engineers. Someone proposed a caching strategy that I knew would fall apart under concurrent writes. I'd hit that exact failure mode six months earlier on a different project. I had the scars and the postmortem to prove it.
Read full article↝
The last few pieces — clicking through opens the reader.