After years of accumulating notes, mental models, and hard-won lessons from building software and leading engineering teams, I’ve finally decided to start writing publicly.
Why Write?
There’s something clarifying about the act of writing. Ideas that seem perfectly formed in your head often reveal their gaps when you try to explain them to others. Writing forces precision.
But beyond personal growth, I’ve benefited enormously from others who’ve shared their experiences. The blog posts that helped me navigate my first architecture decisions. The talks that showed me what great engineering leadership looks like. The books that reframed how I think about systems—both technical and human.
This is my attempt to pay it forward.
What to Expect
I’ll be writing about:
- Engineering leadership — building teams, managing complexity, making decisions with incomplete information
- Systems thinking — how to reason about complex software at scale
- Career reflections — lessons from navigating the IC to management path
- Technical deep dives — occasionally getting into the weeds on problems I find interesting
No regular schedule. No growth hacking. Just thoughts I think are worth sharing, published when they’re ready.
Let’s Connect
If something resonates—or if you disagree—I’d love to hear from you. The best conversations often start with a different perspective.
Thanks for reading.