# AI giveth and AI taketh CPU Page: https://stenobird.com/podcast/the-stack-overflow-podcast/ai-giveth-and-ai-taketh-cpu Text version: https://stenobird.com/podcast/the-stack-overflow-podcast/ai-giveth-and-ai-taketh-cpu.md Podcast: [The Stack Overflow Podcast](https://stenobird.com/podcast/the-stack-overflow-podcast) Published: 2026-05-08T04:00:00+00:00 Episode link: https://rss.art19.com/episodes/5a107299-d079-43fc-94c3-94470ce52551.mp3?rss_browser=BAhJIg90cmFuc2NyaWJyBjoGRVQ%3D--952c5701c84ad333c69d5faa668f8177091704f0 Audio file: https://rss.art19.com/episodes/5a107299-d079-43fc-94c3-94470ce52551.mp3?rss_browser=BAhJIg90cmFuc2NyaWJyBjoGRVQ%3D--952c5701c84ad333c69d5faa668f8177091704f0 Processing state: processed JSON: https://stenobird.com/v1/public/podcasts/the-stack-overflow-podcast/episodes/ai-giveth-and-ai-taketh-cpu Duration seconds: 1931 ## Resource Recorded on the floor of HumanX, Ryan is joined by AMD CTO Mark Papermaster to discuss AMD’s silicon strategy for AI borne of their long history of heterogeneous CPU/GPU computing, how chipmakers are dealing the wide range of AI workloads from training to inference, and the paradox of agents both eating up all the compute and helping AMD accelerate chip innovation.  Episode notes:   Want to learn more about the topics Mark and Ryan discussed in this episode? Check out the AMD Advanced Insights podcast , a monthly show hosted by Mark. Connect with Mark on LinkedIn .   See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info . ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/the-stack-overflow-podcast/episodes/ai-giveth-and-ai-taketh-cpu/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/the-stack-overflow-podcast/ai-giveth-and-ai-taketh-cpu.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.