In this episode, Amir sits down with Brent Keator, an expert advisor at Primary Venture Partners, to unpack one of the most debated engineering challenges: tech debt versus reengineering. They explore how to define tech debt, when to refactor versus rebuild, the ROI of revisiting old code, and how AI is (and isn't) changing the equation. This is a must-listen for engineering leaders navigating complex technical decisions in fast-moving environments.🔑 Key Takeaways:Tech debt isn't always bad—just misunderstood. Brent reframes it as part of the software evolution, often misjudged in hindsight with unrealistic expectations.Refactoring isn't an all-or-nothing decision. Brent recommends carving out 30–40% of engineering time for tech debt if possible, and viewing it as iterative maintenance tied to business value.Reengineering has a cost—evaluate wisely. Use the “better, faster, cheaper” test before replacing tools or platforms, and always account for hidden transition costs.AI can help but won’t eliminate tech debt. While AI improves productivity, Brent argues it doesn’t change the underlying truth: software is disposable, and architecture still needs discipline.⏱️ Timestamped Highlights:00:00 – Intro to Brent Keator and the episode focus: tech debt vs reengineering01:01 – Defining tech debt across code, products, and organizational habits02:53 – When reengineering tools goes too far or solves the wrong problem04:35 – The stigma of tech debt and how to rethink it08:55 – The cost of revisiting old code and the ROI on fixing the past11:12 – Why tech debt in engineering is fundamentally different than other domains12:44 – When to rebuild, how to evaluate tool replacements, and the abstraction advantage16:23 – Vetting open-source solutions: cost, support, and security risks18:36 – The emerging role of AI in engineering and why trust and testing still matter23:20 – Will AI help solve tech debt? Brent’s take on the future of disposable code24:46 – How to connect with Brent and final thoughts💬 Quote of the Episode:“What we write today is going to be gone tomorrow. Whether AI helps or not, we need to get comfortable with that.” – Brent Keator