How do you get the rest of your company, your peers, your leadership, excited about something that's deeply technical, and deeply mundane?  As someone outside the tech org, how should you react when your engineering leader tells you they need a lot of resources for something that doesn't make sense? As always, we do our best to help both sides of the equation find the right answer...

What is Technical debt, and why does your engineering team keep asking for time to fix it? 

What is this automated testing your engineering team won't shut up about?  We talk about what it is, when it makes sense, and when it doesn't.