Writing
Thoughts on engineering leadership, technical strategy, and building software teams that last.
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.
Breaking down silos between dev and ops isn't just a technical problem — it's a people problem. Here's what actually gets in the way, and how to build something that lasts.
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.