01
Context, not pressure
Engineers deliver better when they understand the why. I share business context, not just tickets.
Leadership & Impact
What I believe about leading engineering
Faster teams, clearer decisions, product that actually moves the needle.
I've worked with tech leads who knew everything about code and nothing about people. I chose a different path. I lead with clarity, context, and one conviction: the team should do the best work of their careers here.
02
Quality as a contract
Performance budgets, observability, and tests aren't nice-to-haves. They're the contract that keeps the product reliable.
03
Grow leaders
I mentor engineers so they won't need me. The best compliment is when someone from my team becomes a tech lead.
04
Deciding beats perfecting
Perfect architectures don't exist. I prefer to decide fast, document the trade-off, and iterate with data.
05
Engineering serves the product
Technology that doesn't solve a user or business problem is a hobby. Engineering exists to create value.
06
Measure before optimizing
I don't optimize on intuition. Lighthouse, WebPageTest, analytics — numbers decide, not opinions.
The best code is the code the user never notices — because everything just works.