Thoughts on engineering leadership, technical strategy, and building products that last.
I spent an hour saying 'I don't know' on a digital whiteboard. Here's what went wrong and how I'd approach it now.
The best answer to this question isn't a technology. It's a follow-up question. Here's why that matters and how to use it.
Most candidates treat this as a warm-up. Hiring managers treat it as signal. Here's how to use it.
The question isn't whether to fix tech debt. It's whether fixing it right now will create more value than anything else you could do with those engineer-hours.
Most teams skip architecture reviews because they feel slow. The cost of that decision compounds in ways that don't show up until it's too late to fix cheaply.
20 years of building software, leading teams, and sitting across the table from candidates. Here's what I'm doing with all of it.