Consolidating hardware into fewer, more capable chips looks like an unambiguous win — until the complexity those separate components used to handle resurfaces in the software binding everything back together. In this episode, Sam Grove, Head of Software and Tools Business at MIPS, examines why hardware and software teams can't keep building in sequence, and why MIPS bet its roadmap on the open RISC-V standard instead of defending a proprietary instruction set, with host Yolandi de Weerdt. The conversation also covers how tools like MIPS Atlas Explorer help engineering teams see where hardware acceleration pays off before silicon gets committed, and why the real risk in overhauling a build process is rarely the technology — it's bringing already-productive teams along with the change. This episode is sponsored by
MIPS. Learn how these conversations drive pipeline for other AI brands — download our media kit at
emerj.com/AD1
