Writing

Two decades in, the technical stuff is seldom the hard part. Here's what actually matters — the things no bootcamp, certification, or job description will tell you.

Crisis is inevitable in software. What separates good leaders from bad ones isn't whether crises happen — it's whether they had a plan, communicated clearly, and learned from it afterward.

Innovation isn't a process you bolt onto a team — it's a culture you build deliberately. Here's how to think about both the operational and interpersonal sides of making it real.

At some point, every software engineer faces the fork in the road: stay an IC and move toward Principal, or step into management. Neither is wrong — but the transition is harder than most people expect.

Technical debt is inevitable. Ignoring it isn't a strategy — it's a slow tax on everything your team builds next. Here's how to identify it, prioritize it, and actually get buy-in to pay it down.

I've been working remotely for 8 years — most of them leading distributed engineering teams. Here's what actually makes remote teams work, beyond the surface-level advice.

EI is one of the most overlooked traits in engineering leadership. If you've ever had a manager who couldn't understand why the team was unhappy — that's what a lack of emotional intelligence looks like in practice.

Servant leadership isn't a buzzword — it's a practice born from watching engineers be treated like a means to an end. Here's how I stumbled into it and what it actually looks like day to day.