I’m not a developer slinging syntax at midnight, and I don't pretend to be an AI academic. My strength is synthesizing: looking at messy, 25-year-old legacy systems, listening to executive goals, understanding engineer constraints, and steering everyone toward what's pragmatic, high-retention, and commercially durable.
When teams are debating over-engineered clouds or chasing the newest hype cycle, I’m the calm voice in the room asking: "Does this solve our customer's pain, can we maintain it next year, and does the math work?"
I love picking the boring technology that works (like PostgreSQL and simple queues) over the latest hype that requires three new hires to maintain.
Older software pays today’s salaries. You don’t mock legacy code; you treat it with respect, isolate the brittle parts, and modernize without stopping live revenue.
Artificial emergencies burn great engineers out and produce terrible decisions. I foster steady momentum, high psychological safety, and clear priorities.
When an outage or mistake happens, I step in front of the team and take accountability. When things succeed, the team gets the spotlight. Always.