Podcasts about repo

Repo Jake. You will to be able to hate this movie. Impossible. Jake would make that impossible. Tune in. LinksCheck out or Ko-fi at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://ko-fi.com/batandspider⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Join our ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠DISCORD⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Get your ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bat & Spider STICKERS here⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Steve Barkett Rules t-shirts!!!⁠⁠⁠⁠⁠⁠Get a sweet Bat & Spider ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠t-shirt here⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠! All sale proceeds go to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠The Movement For Black Lives⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.Technical Adviser: Slim of ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠70mm⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Theme song composed and performed by Tobey Forsman of ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Whipsong Music⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.Follow ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bat & Spider on Instagram ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Follow ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Chuck⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ and ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Dale⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on Letterboxd.⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bat & Spider on Letterboxd⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bat & Spider Watchlist⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Send us an email: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠batandspiderpod@gmail.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.Leave us a voice message: (315) 544-0966Artwork by ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Charles Forsman⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠batandspider.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bat & Spider is a ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TAPEDECK⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ podcast, along with our friends at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠70mm⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠The Letterboxd Show⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Escape Hatch⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Will Run For...⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twin Vipers⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠The Movie Mixtape⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠The Yeti is Still Broken⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Austin Danger Pod⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, and ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Lost Light⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. ★ Support this podcast ★

Ray White speaks to Isaah Mhlanga, Chief Economist and Head of Research at Rand Merchant Bank, about the Reserve Bank’s decision to raise the repo rate by 25 basis points to 7.25%, taking the prime lending rate to 10.75%. The hike comes as South Africa’s economy contracts while renewed fuel-price pressures push inflation higher, with the SARB warning that prolonged energy shocks could trigger broader second-round inflation effects. The Money Show is a podcast hosted by well-known journalist and radio presenter, Stephen Grootes. He explores the latest economic trends, business developments, investment opportunities, and personal finance strategies. Each episode features engaging conversations with top newsmakers, industry experts, financial advisors, entrepreneurs, and politicians, offering you thought-provoking insights to navigate the ever-changing financial landscape.    Thank you for listening to a podcast from The Money Show Listen live Primedia+ weekdays from 18:00 and 20:00 (SA Time) to The Money Show with Stephen Grootes broadcast on 702 https://buff.ly/gk3y0Kj and CapeTalk https://buff.ly/NnFM3Nk For more from the show, go to https://buff.ly/7QpH0jY or find all the catch-up podcasts here https://buff.ly/PlhvUVe Subscribe to The Money Show Daily Newsletter and the Weekly Business Wrap here https://buff.ly/v5mfetc The Money Show is brought to you by Absa     Follow us on social media   702 on Facebook: https://www.facebook.com/TalkRadio702 702 on TikTok: https://www.tiktok.com/@talkradio702 702 on Instagram: https://www.instagram.com/talkradio702/ 702 on X: https://x.com/CapeTalk 702 on YouTube: https://www.youtube.com/@radio702   CapeTalk on Facebook: https://www.facebook.com/CapeTalk CapeTalk on TikTok: https://www.tiktok.com/@capetalk CapeTalk on Instagram: https://www.instagram.com/ CapeTalk on X: https://x.com/Radio702 CapeTalk on YouTube: https://www.youtube.com/@CapeTalk567 See omnystudio.com/listener for privacy information.

Ray White speaks to Isaah Mhlanga, Chief Economist and Head of Research at Rand Merchant Bank, about the Reserve Bank’s decision to raise the repo rate by 25 basis points to 7.25%, taking the prime lending rate to 10.75%. The hike comes as South Africa’s economy contracts while renewed fuel-price pressures push inflation higher, with the SARB warning that prolonged energy shocks could trigger broader second-round inflation effects. The Money Show is a podcast hosted by well-known journalist and radio presenter, Stephen Grootes. He explores the latest economic trends, business developments, investment opportunities, and personal finance strategies. Each episode features engaging conversations with top newsmakers, industry experts, financial advisors, entrepreneurs, and politicians, offering you thought-provoking insights to navigate the ever-changing financial landscape.    Thank you for listening to a podcast from The Money Show Listen live Primedia+ weekdays from 18:00 and 20:00 (SA Time) to The Money Show with Stephen Grootes broadcast on 702 https://buff.ly/gk3y0Kj and CapeTalk https://buff.ly/NnFM3Nk For more from the show, go to https://buff.ly/7QpH0jY or find all the catch-up podcasts here https://buff.ly/PlhvUVe Subscribe to The Money Show Daily Newsletter and the Weekly Business Wrap here https://buff.ly/v5mfetc The Money Show is brought to you by Absa     Follow us on social media   702 on Facebook: https://www.facebook.com/TalkRadio702 702 on TikTok: https://www.tiktok.com/@talkradio702 702 on Instagram: https://www.instagram.com/talkradio702/ 702 on X: https://x.com/CapeTalk 702 on YouTube: https://www.youtube.com/@radio702   CapeTalk on Facebook: https://www.facebook.com/CapeTalk CapeTalk on TikTok: https://www.tiktok.com/@capetalk CapeTalk on Instagram: https://www.instagram.com/ CapeTalk on X: https://x.com/Radio702 CapeTalk on YouTube: https://www.youtube.com/@CapeTalk567 See omnystudio.com/listener for privacy information.

Ray White speaks to Isaah Mhlanga, Chief Economist and Head of Research at Rand Merchant Bank, about the Reserve Bank’s decision to raise the repo rate by 25 basis points to 7.25%, taking the prime lending rate to 10.75%. The hike comes as South Africa’s economy contracts while renewed fuel-price pressures push inflation higher, with the SARB warning that prolonged energy shocks could trigger broader second-round inflation effects. The Money Show is a podcast hosted by well-known journalist and radio presenter, Stephen Grootes. He explores the latest economic trends, business developments, investment opportunities, and personal finance strategies. Each episode features engaging conversations with top newsmakers, industry experts, financial advisors, entrepreneurs, and politicians, offering you thought-provoking insights to navigate the ever-changing financial landscape.    Thank you for listening to a podcast from The Money Show Listen live Primedia+ weekdays from 18:00 and 20:00 (SA Time) to The Money Show with Stephen Grootes broadcast on 702 https://buff.ly/gk3y0Kj and CapeTalk https://buff.ly/NnFM3Nk For more from the show, go to https://buff.ly/7QpH0jY or find all the catch-up podcasts here https://buff.ly/PlhvUVe Subscribe to The Money Show Daily Newsletter and the Weekly Business Wrap here https://buff.ly/v5mfetc The Money Show is brought to you by Absa     Follow us on social media   702 on Facebook: https://www.facebook.com/TalkRadio702 702 on TikTok: https://www.tiktok.com/@talkradio702 702 on Instagram: https://www.instagram.com/talkradio702/ 702 on X: https://x.com/CapeTalk 702 on YouTube: https://www.youtube.com/@radio702   CapeTalk on Facebook: https://www.facebook.com/CapeTalk CapeTalk on TikTok: https://www.tiktok.com/@capetalk CapeTalk on Instagram: https://www.instagram.com/ CapeTalk on X: https://x.com/Radio702 CapeTalk on YouTube: https://www.youtube.com/@CapeTalk567 See omnystudio.com/listener for privacy information.

If you feel like your money is being stretched further and further these days, there is a lot happening in the economy that could explain why. Earlier today, Statistics South Africa told us that consumer inflation has climbed to 4.4%; meaning prices, overall, are rising faster than they were a month earlier. And then, just a short while ago, the South African Reserve Bank raised the repo rate to 7.5%. Now, you might hear those numbers and think, “What does any of this have to do with me?” Quite a lot. Because these decisions can eventually determine how much you pay to borrow money, how much your monthly repayments cost, how much businesses pay to operate and, ultimately, how much you have left in your pocket at the end of the month. So, at a time when South Africans are already trying to make their money go further, are we heading into another squeeze, and what should households be watching? Independent economist Xhanti Payi joins us to unpack it.See omnystudio.com/listener for privacy information.

Friendslop Games sind ein kurioses Phänomen: Spiele, die mit wenig Aufwand und noch weniger Budget innerhalb weniger Monate verkaufsfertig über den Tresen gehen - und immer wieder ein Millionenpublikum erreichen. Die oft ziemlich trashig wirkenden Spiele gehören seit der Corona-Pandemie regelmäßig zu den Topsellern und richten sich vor allem an Mulitplayer-Freunde. Lethal Company, Repo, Meccha Chamaleon und Content Warning führen die Liste der erfolgreichsten Friendslop-Spiele an und machen vor, was das Genre auszeichnet: abstruse Situationskomik, Koop-Spaß und nur grob polierte Grafik. Auch in Deutschland gibt es Friendslop-Entwickler - und Mateo Covic könnte von ihnen der erfolgreichste sein. Mit "Paddle Paddle Paddle" (ein kooperatives Paddel-Spiel) knackte er in Rekordzeit die 100.000 Verkäufe, ein Autospiel mit Schrei-Steuerung soll an den Erfolg nun anknüpfen. Nebenbei unterrichtet Mateo andere Entwickler in Game Design, kann auf mehrere DCP- und DEP-Nominierungen zurückblicken und wurde vom Forbes-Magazin für seine Arbeit gewürdigt - und all das mit nicht mal 25 Jahren. Dom hat Fragen, Mateo hat die Antworten.

Star Wars Zero Company reviewed well, hit number one on Steam, and shipped with roughly 80% of its studio furloughed and unpaid. We came out of it in different places — one of us thinks the story is fine and the mechanics are genuinely great, one of us couldn't get past the characters and the story premise — and the argument leads somewhere neither of us expected. The gap between a seven and a nine here is mostly patch work, which raises an uncomfortable question: who's left to do it?Then we go smaller. Grain Rot is ten dollars, it's a full 1.0 release in a genre that treats Early Access as a permanent address, and it's close enough to REPO that the gap is worth arguing about instead of dismissing. We break down the Living Spark system, the persistent Outpost progression that actually separates it from Lethal Company, and whether shipping finished was the honest choice or the strategically worse one. WarDogs hits Early Access the day after this episode, and after four hours of getting absolutely dismantled by it, something clicked. The interesting part isn't the guns — it's that total strangers were reviving each other and communicating, which is the thing Battlefield has promised for a decade and never delivered. The reason is mechanical, and it's a lesson the biggest shooters in the world still haven't learned.And we close on the crater. Every publisher on earth spent the last year rearranging their schedule around a single Thursday in November — Take-Two moved NBA 2K27 to avoid its own game — leaving September and October as a six-week pileup where good games are going to disappear. We talk about what that costs players with limited hours, why the Netflix trailer premiere matters more than anything in the trailer itself, and how to plan a fall when the calendar has been bent around a game that isn't out yet.Show Notes:0:57 - Housekeeping2:22 - Everyone Likes Star Wars Zero Company. Should You?50:57 - Can Grain Rot Beat Lethal Company And REPO?1:10:35 - Can WarDogs Do What Battlefield Can't?1:42:20 - What Is GTA 6 Doing To The Rest Of Gaming?2:25:50 - Upcoming Video Game Releases Become a part of the conversation! If you donate $1 or more on Patreon you can get exclusive access to the Patreon-only chat and channels on the server. Visit our website to find our social channels, check past podcasts and donate to the show.Subscribe to our YouTube channel to see all of our latest videos as they drop. Credits:"Blue Groove Deluxe" by BlueFoxMusic on audiojungle.netWoman Announcer - Ariana Guerra; Actress"Wisdom" by Super Nostalgia 64

Host: Lalo Solorzano Guest(s): Arthur O'Meara Published: September 8, 2026 Length: ~15 minutes Presented by: Global Training Center Summary When goods are damaged in transit, who owns the problem—the seller or the buyer? The answer may not be as straightforward as who owns or physically possesses the goods. In this Trade Tips episode of Simply Trade, host Lalo Solorzano welcomes longtime Global Training Center instructor Arthur O'Meara for a practical conversation about Incoterms® and one of the most important distinctions in an international transaction: the difference between responsibility, possession, and ownership. Arthur shares a real-world FCA scenario involving goods shipped from the United States to Canada that were damaged by rain while in transit. Although title to the goods had not yet transferred to the buyer, the Incoterms® rule told a different story about who was responsible for the risk at the time of the damage. To make these concepts easier to remember, Arthur introduces his RePO framework: Responsibility, Possession, and Ownership. He explains why these three concepts need to be understood separately—and why the paperwork, the parties' intentions, and what actually happens operationally should all align. The key lesson: don't wait until something goes wrong to discover what your contract actually says. Main Topic / Discussion This episode focuses on understanding how Incoterms® address the transfer of possession and risk between seller and buyer—and why that should not be confused with the transfer of ownership or title. Arthur uses the mnemonic RePO: Responsibility, Possession, and Ownership to distinguish three concepts that can transfer at different points in a transaction. Using an FCA seller's facility example, Arthur explains how risk can transfer to the buyer once the seller loads the goods onto the collecting vehicle, even though ownership may not yet have transferred. When the shipment in his example was damaged by rain on its way to Canada, understanding the agreed Incoterms® rule helped determine which party bore the risk. The broader lesson applies beyond FCA: companies should regularly compare their contracts and documentation with their actual operational practices and confirm that they accurately reflect what the buyer and seller intend. Key Takeaways • Remember RePO: Responsibility, Possession, and Ownership are separate concepts and should be addressed accordingly in the transaction. • Incoterms® do not determine ownership: They address important responsibilities between buyer and seller, including delivery and the transfer of risk, but title or ownership must be addressed separately. • Know when risk transfers: Under FCA at the seller's facility, the point at which the seller delivers the goods to the buyer's carrier can determine when risk shifts from seller to buyer. • Test your paperwork before there's a problem: Create a hypothetical failure or damaged-shipment scenario, pull out the documentation, and determine whether the written agreement matches the parties' intentions and actual operations. Resources & Mentions • O'Meara and Associates • Global Training Center • The Way Things Work: Newly Revised Edition by David Macaulay — Arthur recommends this illustrated reference as an approachable way for trade professionals to better understand mechanical and engineering concepts useful in areas such as tariff classification. • Whose Problem Is It? Scenario of Incoterms FCA (RePO) — Explore Arthur's RePO concept and an Incoterms® FCA scenario in more detail. Credits Host: Lalo Solorzano Guest(s): Arthur O'Meara - LinkedIn Producer: Lalo Solorzano

Harness Field CTO Martin Reynolds joins The New Stack to talk about what happens after coding agents start opening pull requests faster than anyone can review them. He explains how he first saw the bottleneck during early GitHub Copilot trials, the three ways enterprises are coping with the volume now, and why Harness rebuilt its Code Repository and launched AI Code Review for agent traffic. The conversation also covers GitHub's recent outages, the software delivery knowledge graph behind Harness's reviewer, and how much of the delivery pipeline should stay deterministic. Learn more from The New Stack around the latest in coding agents:AI coding agents can write code, Crafting wants to help them ship itGit real: AI agents aren't just for solo developers anymoreJoin our community of newsletter subscribers to stay on top of the news and at the top of your game.

Lapkritį netikėtu pavidalu atgimsta žymiausias G. Orwello romanas „1984“! Šįkart tragišką ir kartu viltingą dviejų žmonių meilės istoriją papasakos repo opera – režisuota ir sumanyta „Pakartot“ svečio Gabrieliaus Zapalskio. Pagrindinį vaidmenį operoje atlieka Pijus Opera, o libretą kuria Kastetas ir Svaras iš „G&G Sindikato“.Ved. Domantas Razauskas

Crypto News: Charles Schwab adds altcoins Solana, Avalanche and Chainlink to nascent crypto platform. XRP treasury firm Evernorth said its SEC Form S-4 related to its business combination with Armada is now effective, allowing progress toward a Nasdaq listing. UK to formally order Bank of England to advance stablecoin and digital money innovation.

Commercial real estate lenders and debt funds rely on warehouse facilities and repo lines to finance originations, manage liquidity, and create pathways to securitization. While these terms are often used interchangeably, the underlying structures, documentation, and risk allocation can have significant implications for both borrowers and lenders, particularly during periods of market volatility. As commercial lending activity and CLO issuance continue to rebound, market participants are closely evaluating funding capacity, margin exposure, takeout risk, and the evolving regulatory landscape. In this episode, Stephen Bush joins Dan Evans to discuss how warehouse facilities and repo lines work, key negotiation points, current market conditions, and the opportunities and challenges shaping the sector in 2026. Read the transcript here: https://www.seyfarth.com/dir_docs/podcast_transcripts/The-Property-Line_Understanding-Warehouse-Facilities-and-Repo-Lines.pdf

"If there's naked flesh, it must have lady parts, I guess." Brian and Alison read an article arguing that AI is biased against women — built partly on a report that more than half of twenty-nine nudify apps, asked to undress a photo of a fully dressed man, gave him breasts instead. Also: the Stanford resume study the article cites and the counter-studies it leaves out, and why no feminist has ever been asked to prove the definition of patriarchy. "I broadly agree that Sam Altman has not invented God. But you'd have to believe Sam Altman is behind a bunch of apps made in Korea or Estonia. She's arrived at the right sentiment by a circuitous path that makes no sense." Support the show: feedthebadger.com/support Send us a message: feedthebadger.com/justthetip Join the community: badgernation.online

The U.S. government spends roughly $2 trillion more than it collects every year and runs entirely on borrowed money — yet somehow it still turns around and lends tens of billions of dollars to other nations. How is that even possible? The answer starts with a keyboard and ends with the price of your groceries. Jay opens 300 years ago, with the Scotsman whose paper-money scheme minted the world's first "millionaires" in France — right before it collapsed — and argues the system we live under today is the very same machine, just far better at hiding the problem. From there he takes you inside it piece by piece: how Washington actually borrows, the small club of banks legally forced to buy its debt, and the single number that quietly sets your mortgage, your rent, and the entire global economy. Then comes the question that shouldn't have an answer: how a country this deep in debt can suddenly act as the world's lender of last resort — and what a string of recent, urgent requests from the Gulf and Asia may really be signaling. By the end, Jay ties the whole machine back to one thing sitting in your pocket right now. The money comes from nowhere. So where does the bill go? Citations: https://rentry.co/3sskuagz — Learn to invest alongside the top minds in commodities. Join The Commodity University today. CLICK: https://linkly.link/26yH8 Sign up for my free weekly newsletter at https://2ly.link/211gx Be part of our online investment community: https://cambridgehouse.com X / Twitter: https://twitter.com/JayMartinBC Instagram: https://www.instagram.com/jaymartinbc Facebook: https://www.facebook.com/TheJayMartinShow LinkedIn: https://www.linkedin.com/company/cambridge-house-international — 0:00 - The $2 Trillion Paradox 0:48 - A Lesson From 1716: John Law's Paper Money 2:58 - The $2 Trillion Gap: How Washington Borrows 4:07 - The Rigged Auction: Primary Dealers 5:10 - The Secondary Market: Where the Real Story Lives 5:28 - Bond Price vs. Yield: The See-Saw 6:48 - What the Fed Actually Controls 8:13 - The Keyboard: Money Created From Nothing (QE) 9:32 - The Contradiction: Currency Swap Lines 10:59 - Repo vs. Swap & the Finite Hose 12:13 - A Short History of Swap Lines (2008 & 2020) 13:15 - The Club Cracks Open: Argentina & the Gulf 14:39 - Amend, Extend & Pretend 15:13 - The Hormuz Thesis: Forced Selling Begins 17:00 - Who Actually Pays? Inflation, the Hidden Tax 19:20 - What Do You Do About It? 20:18 - The Crisis Wasn't Avoided — It Was Moved

"I feel like I'm getting spots in my vision from looking this directly at the epicenter of female thinking." Brian and Alison return to the author of My Dear Stalker, who has a new article: if you approach a woman, she rejects you, and you then stop interacting with her, that's punishing her for her boundaries. She wasn't obligated to keep him around — that would be mean. He is obligated to stay, because otherwise he hates women. Also: what happens when you ask an AI why the man should stay and it can't find a reason either, the friend who resented a man for not wanting her, and a long stretch of REPO with Gabriel afterwards. "Instead of improving my craft as a novelist, I gotta go home, open up my laptop, and write a blog on my Medium shitting on men for however long it takes me." Support the show: feedthebadger.com/support Send us a message: feedthebadger.com/justthetip Join the community: badgernation.online

Join as the crew gets a preview for an upcoming campaign and launches in to the world of CY, exploring the "rules-light, rage-heavy" cyber-punk system from Free League Publishing, "CY_BORG".

Book a call: https://remnantfinance.com/calendarEmail us at info@remnantfinance.com or visit https://remnantfinance.com for more informationFOLLOW REMNANT FINANCEYoutube: @RemnantFinance (https://www.youtube.com/@RemnantFinance)Facebook: @remnantfinance (https://www.facebook.com/profile.php?id=61560694316588)Twitter: @remnantfinance (https://x.com/remnantfinance)TikTok: @RemnantFinanceDon't forget to hit LIKE and SUBSCRIBEThe Fed cut rates and your mortgage went up. If that never made sense to you, this episode is the explanation. In part one of a two-part solo breakdown, Hans starts with the three interest rate stories dominating the macro headlines right now, the stubborn 10-year Treasury, Kevin Warsh's campaign to kill forward guidance, and Japan quietly letting its Treasury holdings roll off, and uses them as the entry point to a much bigger question: who actually sets the price of money?Chapters 00:00 – Opening Segment 01:00 – Setting up the interest rate primer 02:25 – Headline one: the 10-year Treasury refuses to fall 03:55 – Why a weak jobs report makes the stock market celebrate 06:40 – Headline two: Kevin Warsh is killing forward guidance 09:00 – Shorter statements, no dot plot, and a market that has to do its own homework 13:35 – Headline three: Japan stops rolling its Treasury holdings 16:10 – The food chain: it was never one dial 20:25 – The fed funds rate is banks lending each other reserves overnight 25:25 – The dual mandate, CPI versus PCE, and how inflation gets measured 29:35 – Reserve requirements are now zero 32:15 – IORB: the floor the Fed actually sets 37:55 – The reverse repo facility and the discount rate ceiling 39:20 – The repo market: a pawn shop moving trillions a night 42:45 – LIBOR, the 2012 scandal, and the move to SOFR 44:10 – Primary dealers and the price of the golden ticket 47:00 – What QE really is and why the Fed can't buy direct from Treasury 52:00 – Inside a Treasury auction: bids, clearing yield, and the tail 57:05 – Recap and what's coming in part twoKey TakeawaysThere is no such thing as "the" interest rate. There is a stack of them, and the Fed only has real influence over the short end. Everything between the Fed and your mortgage is a chain of institutions taking the rate handed to them, adding yield, and passing it down. The fed funds rate is not a number anybody types into a computer. It is a real market rate set between banks settling reserves overnight, and the Fed steers it with incentives rather than force. Forward guidance has been the Fed's most powerful tool, and it costs nothing to use. Saying the conditions might align for a cut can move markets as effectively as an actual cut, which is why Warsh trimming statements and abandoning the dot plot amounts to a real policy shift. The repo market, not the fed funds market, is where the money actually is. Fed funds is a small, uncollateralized club of primary dealers. Quantitative easing is the one situation where "printing money out of thin air" is literally accurate. The Fed is barred from buying new issues directly from Treasury, so the twenty-four primary dealers absorb whatever the auction does not clear and the Fed buys from them with newly created reserves. Treasury auctions price on demand, not decree. Treasury announces the quantity, buyers submit the yields they will accept, bids fill from lowest to highest, and the yield on the last dollar sold becomes the yield everybody gets.

Run That Prank Back - REPO full 450 Tue, 11 Aug 2026 14:28:28 +0000 KE91AMkMm55V0LgKEPkKPeNdawW43XcO comedy SHMS Shenanigans! comedy Run That Prank Back - REPO Catch up on what you missed on The Steve Harvey Morning Show. 2024 © 2021 Audacy, Inc. Comedy https://player.amperwavepodcasting.com?feed-link=https%3A%2F%2Frss.a

"Once he gets grey, once he gains a few pounds, God forbid he gets sick — she's out the door like a greased rat out of an aqueduct. And she'll have half his money on the way out." Brian and Alison read a Medium feature on the manosphere, a place where misogyny wears a suit and the influencers are "polished, sham-rich men in Lamborghinis," while playing REPO. Also: which income quintiles the marriage collapse actually reaches, the article author's promise that the fight is against the structure of patriarchy rather than men, and whether that survives finding patriarchy in a man standing on a bridge. "If you can find patriarchy in a man who's about to jump off a bridge — where can you not find it?" Support the show: feedthebadger.com/support Send us a message: feedthebadger.com/justthetip Join the community: badgernation.online

✔️ BTC daily✔️ Get ready for a BTC pump!✔️ People are calling Bitcoin "dead" at $60K✔️ BIP-110 Update ✔️ Giaccomo resigns from ocean board ✔️ Boltz has renewed its PGP-signed warrant canary✔️ ZEUS infrastructure is temporarily offline ✔️ Coldcard Hack Part V: Bitcoin red team update ✔️ NVK deleting blockclock posts ✔️ Repo setup to steal passwords, seeds and private keys ✔️ Vulnerabilities in the trezor firmware?✔️ Wesatoshi test successful!✔️ Coldcard things winding down ✔️ Sources:► https://x.com/superbitcoinbro/status/2084836866508103866► https://x.com/bitcoinarchive/status/2085054718032621838► https://x.com/gordongekko/status/2084985782813577621► https://x.com/LukeDashjr/status/2084946156304420881► https://x.com/monitorsitch/status/2085049606598214079?s=20► https://x.com/giacomozucco/status/2084782560291311992► https://bitcoinsignal.net/bip110/► https://x.com/bitcoinnewscom/status/2085006825808654737► https://x.com/zeusln/status/2085113369367871605► https://x.com/callebtc/status/2085024458012586286► https://x.com/JuanSGalt/status/2085102236179333442► https://bitcoinmagazine.com/business/bitcoin-red-team-finds-85-critical-flaws-across-390-open-source-repos-after-coldcard-exploit► https://x.com/callebtc/status/2085101769500377193► https://x.com/callebtc/status/2085318442488348811► https://x.com/raw_avocado/status/2085011012370022457► https://x.com/jrakibi/status/2084947141202768295► https://x.com/spacebull/status/2084744945278300652► https://x.com/flaccyboi/status/2085062061969571910► https://x.com/lunymoon13/status/2083957228122354112► https://x.com/zerocipher002/status/2084892341551177771► https://x.com/we_satoshis/status/2085034468935450918► https://x.com/tavcannallc/status/2084971976674705701► https://x.com/francispouliot_/status/2084827076482200060► DONATE TO HELP KEONNE AND BILL https://www.change.org/p/stand-up-for-freedom-pardon-the-innocent-coders-jailed-for-building-privacy-tools✔️ Check out Our Bitcoin Only Sponsors!► https://archemp.co/Discover the pinnacle of precision engineering. Our very first product, the bitcoin logo wall clock, is meticulously machined in Maine from a solid block of aerospace-grade aluminum, ensuring unparalleled durability and performance. We don't compromise on quality – no castings, just solid, high-grade material. Our state-of-the-art CNC machining center achieves tolerances of 1/1000th of an inch, guaranteeing a perfect fit and finish every time. Invest in a product built to last, with the exacting standards you deserve.► Join Our telegram: https://t.me/theplebunderground#Bitcoin #crypto #cryptocurrency #dailybitcoinnews #memecoinsThe information provided by Pleb Underground ("we," "us," or "our") on Youtube.com (the "Site") our show is for general informational purposes only. All information on the show is provided in good faith, however we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability, or completeness of any information on the Site. UNDER NO CIRCUMSTANCE SHALL WE HAVE ANY LIABILITY TO YOU FOR ANY LOSS OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF THE SHOW OR RELIANCE ON ANY INFORMATION PROVIDED ON THE SHOW. YOUR USE OF THE SHOW AND YOUR RELIANCE ON ANY INFORMATION ON THE SHOW IS SOLELY AT YOUR OWN RISK.

Sponsored by Blocks: Save at least 20% on your AWS costs with AI-powered optimization and enterprise discounts. Get your free Cloud Check at https://blocks.cloud/alphalist?utm_source=alphalist&utm_medium=podcast&utm_campaign=blocks-podcast-2026 Aike Hillbrands co-founded and killed two companies before Kombo, now a Y Combinator-backed HR integration platform with $10M+ ARR and a $25M Series A. Along the way, his team built something almost by accident: a company-wide AI brain made of a GitHub repo, a Cursor agent, and a Slack channel, built in two hours, that replaced how the whole company gets answers. In this episode, Aike explains why files and grep beat MCP tools and vector search for agent reliability, walks through Simon Willison's "lethal trifecta" of AI security risks and how a public Slack channel acts as a guardrail against it, and makes the case for why AI won't commoditize enterprise HR integrations anytime soon, despite that being Kombo's own bet. Topics covered: - How Kombo went from Notion AI to a Git-based company brain - Why files and grep beat MCP tools and vector search for agent reliability - The architecture: per-customer summary files, cross-linked support tickets, BigQuery CLI, Slack integration - Simon Willison's "lethal trifecta" and practical mitigations - Why a public Slack channel works as a security guardrail - The buy-vs-build question for internal AI tooling - Why enterprise HR API integrations resist commoditization by AI

Charles Spicer describes how, as 1939 began, the diplomatic situation worsened due to the catastrophic appointments of Henderson and Ribbentrop. Henderson, the "arch-appeaser," fed Chamberlain's natural tendencies and suppressed reports that might upset Hitler. Conversely, Ribbentrop had become irrational and vitriolic toward the British, feeling socially snubbed. Despite accurate intelligence from Christie and Conwell-Evans flowing to Halifax, the Foreign Secretary vacillated between their warnings and Henderson's appeasement. Although the Fellowship's activities were suspended after the invasion of Prague, it remained a vital conduit for information that the official British embassy in Berlin failed to provide. (11)1940

The Voidcat vigil continues. Supergirl has officially dropped, and the cope is here. Also REPO.

# Show Notes: Vibe Coding and Real World Problems: Why AI Still Needs a CTO **Guest:** Anuraag Jain, CTO, Executive Coach and Author **Website:** [growthvariable.com](https://www.growthvariable.com) **LinkedIn:** [Anuraag Jain](https://www.linkedin.com/in/anuraagjain) --- ## About This Episode Anuraag Jain is a 30-year tech industry veteran who started as an Oracle DBA in India without an engineering degree and became a CTO in under nine years. He was the first developer hired at Betfair, where he built the betting exchange engine behind one of the era's biggest fintech IPOs, and served as CTO at The Hut Group (THG) during their run as the UK's fastest-growing tech company. In this episode, Bhairav and Anuraag talk honestly about vibe coding: what it can do, where it breaks down, and why thirty years of building things under pressure still matters in an AI-assisted world. --- ## What We Cover - How two non-traditional hires found their way into tech and why that background shaped how they build - The early days at Betfair: manual bet settlement, shoestring infrastructure, and recovering 36 hours of betting data from server log files at 2am - What scaling really means when you have no safety net - The 80/20 rule for vibe coding: what AI handles well and what still requires human judgment - Security blind spots in AI-generated code and why even experienced engineers get caught out - The hidden cost of running AI tooling against a large code base - Repo to Pitch: the open source tool that turns a code base into a full pitch deck and documentation suite - RepoWatch: how to track exactly what AI has changed in your code, commit by commit - *Prompt Engineering the Subconscious*: the book that connects AI prompting to mindset and reached the UK top 50 - What the fractional CTO market actually looks like right now, and the three types operating in it - Practical advice for anyone trying to break into tech or move toward a CTO role today --- ## Key Takeaways - AI can handle roughly 80% of what used to require a developer. The remaining 20% is the domain logic that requires someone who actually understands the problem. - The AI does not know which parts of your code cannot be touched. Unless you tell it, it will modify anything, and you may not notice until something breaks. - Vibe coding a product does not make it production-ready. Security, scalability, and edge-case logic still need human attention. - Building something real, however small, is still the best way to develop the judgment the CTO role requires. The tooling available now means there is no excuse not to. --- ## Links - Anuraag Jain on LinkedIn: [linkedin.com/in/anuraagjain](https://www.linkedin.com/in/anuraagjain) - Growth Variable: [growthvariable.com](https://www.growthvariable.com) - Repo to Pitch (open source): [growthvariable.com/repotopitch.html](https://www.growthvariable.com/repotopitch.html) - RepoWatch: [growthvariable.com](https://www.growthvariable.com) - *Prompt Engineering the Subconscious*: [book.growthvariable.com](https://book.growthvariable.com) --- ## About the Atom CTO Podcast The Atom CTO Podcast, transitioning to Bits, Bytes and Business, features conversations with founders, CTOs and entrepreneurs about building technology businesses in the real world. Hosted by Bhairav Patel. Subscribe wherever you get your podcasts.

Open Source draufschreiben und digitale Souveränität dazu sagen, fertig? Leider nicht. Gerade jetzt, wo Behörden, Unternehmen und Politik verstärkt über freie Software, Public Money, Public Code und europäische Unabhängigkeit sprechen, wird ein Problem immer sichtbarer: Open Washing. Produkte wirken offen, klingen nach Open Source und versprechen Kontrolle. Schaut man genauer hin, fehlen oft genau die Freiheiten, auf die es ankommt.In dieser Episode sprechen wir mit Johannes Näder von der Free Software Foundation Europe darüber, was freie Software wirklich bedeutet und warum die vier Freiheiten der entscheidende Maßstab sind. Wir klären, wie Open Washing funktioniert, warum Begriffe wie Source Available, Open Core oder souveräne Cloud schnell in die Irre führen können und weshalb digitale Souveränität ohne freie Software nicht funktioniert. Dazu schauen wir auf konkrete Beispiele aus der Praxis, von Bitwarden über ArangoDB bis hin zu öffentlichen IT-Projekten, und diskutieren, worauf Entwickler:innen, Verwaltungen und Beschaffungsstellen achten sollten.Wenn du wissen willst, wie du Open Washing erkennst, welche Red Flags es bei Lizenzen, Repositories und Enterprise-Modellen gibt und warum dieses Thema für Open Source, öffentliche Beschaffung und Europas Tech-Zukunft so relevant ist, bist du hier genau richtig.Bonus: Nach dieser Episode wirst du vermutlich nie wieder ganz entspannt auf eine Pricing-Page schauen.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Send Us an Email to Chat!This week we have our baby boy Ty back, and we are watching Repo! The Genetic Opera! What a time for Pride!Support the show

The Voidcat vigil continues. "Women suck" by: A womanAlso REPO. Since Mia the Void Cat has warped back into the abyss from whence she came, so we are going to try to have some fun to decompress from all the BS we deal with every day. So we will play the horror comedy game, REPO. We will also be reading an article about men leaving the workforce! Women most affected! Tune in!

Welcome to Dev Game Club, where this week we start a new series on 2005's Psychonauts. We stay in the same year as our last game, and dive into a little of the prehistory of the game before diving into the game proper. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary. Sections played: Coach Oleander's Brain Issues covered: making something for someone else to own, spinning off from LucasArts, staying true to their persona, being a more open studio, documentaries about the studio, the possibility of the studio closing, how the game starts, a super stylistic game, clear identity, bringing individuality to each character, asymmetry, offending the efficient developer, hand-crafting everything, impeccable writing and voice acting, themes coming through later, trailblazing, an indie scene in San Francisco, changing guards at publishers, drawing on psychology for its setting, a cohesive and pure game, exploring two tutorial areas, customizing buckets of figments of imagination, building engine game and studio together, crunch-tastic development, a variety of action and platforming primitives, an underimplemented feel and polish, fighting the camera, systemic cameras that have trouble covering everything, a big swing, asymmetric multiplayer modes, mutators, an internal mail alias, voice over IP, what do you need to support an MP game post-launch, inventory tetris, risk to return to get a loot item, a vestigial element of games, forcing hard choices or loops, re-examining genre "defaults," informing our own work, Octavia's gadget system, giving more agency to the player, a shifting meta, a wide tunnel of known options.  Games, people, and influences mentioned or discussed: Splinter Cell: Chaos Theory, Tim Schafer, Grim Fandango, Full Throttle, LucasArts, Microsoft, Ed Fries, Majesco, 2015, Metal of Honor: Allied Assault, Infinity Ward, Call of Duty, Jason West, Vince Zapella, Nihilistic, Infinite Machine, Zombies Ate My Neighbors, Phantom Menace, Dean Sharpe, Kalani Streicher, Broken Age, Unreal Engine, Kiln, Two Player Productions, Scott Campbell, Disney, Warner Bros, Studio Ghibli, Peter Chan, Day of the Tentacle, SW: Republic Commando, Beyond Good & Evil, Monkey Island (series), Spyro, Super Mario (series), Illumination, Braid, Celeste, Choice Provisions/Gaijin Games, Super Meat Boy, Team Meat, World of Goo, Crystal Dynamics, Prince of Persia: Sands of Time, Ocarina of Time, Ashton Herrmann, Unreal Tournament, Quake, Duke Nuke'em, Hunt: Showdown, Repo, Peak, Matthew, Outlaws, Aliens vs Predator, Starcraft, Matthew, Diablo, Animal Crossing, Resident Evil (series), Harley Baldwin, Halo, DOOM (1993), Maas, Project: Octavia, Troy Mashburn, Thief (series), Kirk Hamilton, Aaron Evers, Mark Garcia. Next time: more Psychonauts! Twitch: timlongojr and twinsunscorp YouTube Discord DevGameClub@gmail.com 

The Voidcat vigil continues. Women are now just telling us they take pleasure in men's pain. What a shocker. Also REPO. Since Mia the Void Cat has warped back into the abyss from whence she came, so we are going to try to have some fun to decompress from all the BS we deal with every day. So we will play the horror comedy game, REPO. We will also be reading an article about men leaving the workforce! Women most affected!

This episode unpacks the jaw-dropping surge in vulnerabilities unearthed by AI, revealing how Microsoft shattered its own patch records while adversaries and defenders race to outpace each other. The conversation gets real about whether AI is fixing our broken software or just making attacks easier for everyone. Rootkits found in more than 400 ArchLinux User Repository packages. The US government requests Anthropic to remove Mythos and Fable. CISA responds to AI-driven attacks with new patching requirements. NPM to switch to more secure install defaults. Will it help. Our listeners react to last week's PHP commentary. June shows that AI has arrived for vulnerability discover Show Notes - https://www.grc.com/sn/SN-1083-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to Security Now at https://twit.tv/shows/security-now. You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Sponsors: meter.com/securitynow canary.tools/twit - use code: TWIT joindeleteme.com/twit-biz zscaler.com/security adaptivesecurity.com

This episode unpacks the jaw-dropping surge in vulnerabilities unearthed by AI, revealing how Microsoft shattered its own patch records while adversaries and defenders race to outpace each other. The conversation gets real about whether AI is fixing our broken software or just making attacks easier for everyone. Rootkits found in more than 400 ArchLinux User Repository packages. The US government requests Anthropic to remove Mythos and Fable. CISA responds to AI-driven attacks with new patching requirements. NPM to switch to more secure install defaults. Will it help. Our listeners react to last week's PHP commentary. June shows that AI has arrived for vulnerability discover Show Notes - https://www.grc.com/sn/SN-1083-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to Security Now at https://twit.tv/shows/security-now. You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Sponsors: meter.com/securitynow canary.tools/twit - use code: TWIT joindeleteme.com/twit-biz zscaler.com/security adaptivesecurity.com

This episode unpacks the jaw-dropping surge in vulnerabilities unearthed by AI, revealing how Microsoft shattered its own patch records while adversaries and defenders race to outpace each other. The conversation gets real about whether AI is fixing our broken software or just making attacks easier for everyone. Rootkits found in more than 400 ArchLinux User Repository packages. The US government requests Anthropic to remove Mythos and Fable. CISA responds to AI-driven attacks with new patching requirements. NPM to switch to more secure install defaults. Will it help. Our listeners react to last week's PHP commentary. June shows that AI has arrived for vulnerability discover Show Notes - https://www.grc.com/sn/SN-1083-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to Security Now at https://twit.tv/shows/security-now. You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Sponsors: meter.com/securitynow canary.tools/twit - use code: TWIT joindeleteme.com/twit-biz zscaler.com/security adaptivesecurity.com

This episode unpacks the jaw-dropping surge in vulnerabilities unearthed by AI, revealing how Microsoft shattered its own patch records while adversaries and defenders race to outpace each other. The conversation gets real about whether AI is fixing our broken software or just making attacks easier for everyone. Rootkits found in more than 400 ArchLinux User Repository packages. The US government requests Anthropic to remove Mythos and Fable. CISA responds to AI-driven attacks with new patching requirements. NPM to switch to more secure install defaults. Will it help. Our listeners react to last week's PHP commentary. June shows that AI has arrived for vulnerability discover Show Notes - https://www.grc.com/sn/SN-1083-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to Security Now at https://twit.tv/shows/security-now. You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Sponsors: meter.com/securitynow canary.tools/twit - use code: TWIT joindeleteme.com/twit-biz zscaler.com/security adaptivesecurity.com

This episode unpacks the jaw-dropping surge in vulnerabilities unearthed by AI, revealing how Microsoft shattered its own patch records while adversaries and defenders race to outpace each other. The conversation gets real about whether AI is fixing our broken software or just making attacks easier for everyone. Rootkits found in more than 400 ArchLinux User Repository packages. The US government requests Anthropic to remove Mythos and Fable. CISA responds to AI-driven attacks with new patching requirements. NPM to switch to more secure install defaults. Will it help. Our listeners react to last week's PHP commentary. June shows that AI has arrived for vulnerability discover Show Notes - https://www.grc.com/sn/SN-1083-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to Security Now at https://twit.tv/shows/security-now. You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Sponsors: meter.com/securitynow canary.tools/twit - use code: TWIT joindeleteme.com/twit-biz zscaler.com/security adaptivesecurity.com

Penny and Midge discuss the goth-flavored rock n' roll horror cult movie musical of our generation: Repo! The Genetic Opera. Join the conversation on the Ghouls Night In discord! Follow the ghouls on Instagram at @ghoulsnightinpod Cover art by Alex Zimdars

The Voidcat vigil continues. There Is No Middle Anymore. Being Different is a Crime. Also REPO. Since Mia the Void Cat has warped back into the abyss from whence she came, so we are going to try to have some fun to decompress from all the BS we deal with every day. So we will play the horror comedy game, REPO. We will also be reading an article about men leaving the workforce! Women most affected!

R.I.P. Anthony Stewart Head. Our love for you simply can not be expressed by any means other than sharing the episode where Jeremy goes on and on about your raw sexuality for like half an hour.Fear Level: Spoopy with a side of eTrigger Warnings: Director: Darren Lynn BousmanWriters: Darren Smith Terrance ZdunichStars: Alexa Pena-Vega, Anthony Stewart Head, Paul Sorvino, Paris Hilton, and Sarah Brightman and Nivek Ogre (Kevin Ogilvie)Repo: The Genetic Opera is a horror musical goth opera about a guy who repossesses organs, his sick daughter, a family full of underused character actors, and one very screamy grave robber. It's...a lot...but somehow also not enough. It is super weird though.Topics of Discussion:-Your favorite Spy Kid and Watcher/Librarian-Corpse battering rams-a little glass vial-a little glass vial-a little glass vial-GRAAAAAVES!-"You're at Nightmare Before Christmas and I need you at Rocky Horror Picture Show"-Tough guys don't spit blood, they just fall over dead-Have you heard of Sonny Corleone? No? GOOD!-MS Paint comic interludes-Literal mean puppet-We're on a string of movies that don't handle sex workers well. Oof.-Emily talks about Skinny Puppy-God, there's just so much potential here that you're not using.-We brainstorm half a dozen better versions of this movie using the same pieces they have here and and just arranging them differently-I say again, THE RAW SEXUAL ENERGY OF ANTHONY STEWART HEADRecommendations:-Evil Dead: The Musical-Carrie: The Musical-The Toxic Avenger: The Musical-Spiderman: Turn off the Dark-Natasha Pierre and the Great Comet of 1812-Zipperface: The Hobo Musical-Courtney Crumrin-The Crow-City of Lost Children-Skinny Puppy videos-Romeo + Juliet-Moulin Rouge-Phantom of the Paradise-Within Temptation- Black Symphony-Malice Mizer videos-Pink Floyd: The Wall-Bioshock-Deus Ex-Ghost in the Shell: Standalone Complex-Buffy Once more with feeling-The Rocky Horror Picture Show-Anna and the Apocalypse-LabyrinthFollow our guests:Joey BraccinoTwitter: @joeybraccinoPodcast: Talking ComicsFollow us on twitter @proghorrorpodFollow Emily on twitter @megamothEmily's Website: Megamoth.netFollow Ben on twitter @benthekahnPre-Order Ben's new book, Renegade Rule.Follow Jeremy on twitter @jrome58Visit his website at JeremyWhitley.comRSS Feed: https://feeds.transistor.fm/progressively-horrifiedWebsite: https://progressivelyhorrified.transistor.fm/Join our Patreon at: patreon.com/progressivelyhorrified to support the show, get bonus episodes, early access to upcoming episodes, and a cool Progressively Horrified t-shirt.Come back next week to hear about Attack the Block!★ Support this podcast on Patreon ★ JOIN JEREMY'S ZOOP CAMPAIGN AND HELP MAKE GREAT COMICS! https://zoop.gg/c/slayTake our listener survey: http://bit.ly/progressivelyhorrified-surveySign up to support Progressively Horrified on Patreon for as little as $5 a month and get bonus episodes! https://www.patreon.com/c/progressivelyhorrified Hosted on Acast. See acast.com/privacy for more information.

This week on PREVIOUSLY ON… Jason and Rosie cover the latest trailers from Disclosure Day, House of The Dragon season 3, and X-Men ‘97. Then they talk about ‘Obession’ breaking box office records, Steam Deck price hikes and then a recap of Cannes’ Film Festival, is it in its flop era? THEN! be sure to stick around for the end of NEWS to hear a wonderful interview with Terrance Zdunich and Darren Lynn Bousman, Creator and Director of REPO! The Genetic Opera, for its 17th anniversary 4k remaster. Follow Jason: IG & Bluesky Follow Rosie: IG & Letterboxd Follow X-Ray Vision on Instagram Join the X-Ray Vision DiscordSee omnystudio.com/listener for privacy information.

The new AIEWF website is live! CFPs close in 2 days and we will run our first New Engineer Orientation this weekend, get your tickets booked ASAP as they -will- sell out. Take the AI Engineering Survey and get >$2k in credits and free AIE WF tickets!One of the central tensions in the agents industry is that even while there are major decacorn agent labs like Sierra, Decagon, Notion and Cursor being built up, it is also true that it has never been easier to DIY agents, with a plethora of agent frameworks like LangGraph and Pydantic and Flue, and managed agents from Anthropic and Gemini and Amazon. There has been a wave of companies building their own background agents from Shopify to Stripe to Paradigm to Razorpay, and even Cognition's friends Ramp have built their own coding agent with other friend Modal.You'd think Cognition might feel a bit threatened, but they're not - even after all this, they were way oversubscribed for the $1B Series D they just announced:Walden Yan, coiner of context engineering and Chief Product Officer/Cofounder of Cognition, invited OpenInspect's Cole Murray to talk about why the Devin is in the Details.Full conversation live on the pod today: In retrospect, async agents were the most AGI pilled bet you could make in 2024 - the models weren't good enough yet to vibecode, and people didn't trust AI enough to let it rip, nobody (including early Cognition) was sure about the form factors. Now it is obvious:* The first wave of AI coding tools made the developer faster but remain heavily in the loop. Copilor and Cursor's tab autocomplete are prime examples However, the workflow was still heavily centered around and bottlenecked by the developer's local workflow: a developer in an IDE, watching the model, accepting or rejecting changes, and pushing code one interaction at a time.* The second wave was local agents: Claude Code, Windsurf, Cursor's agents pane: first one and increasingly many terminals all running concurrently.* The current Age of Async Agents points to a different future focused more on agent orchestration which drives end-to-end development.According to previous guest Steve Yegge, there are finer-grained 8 levels to agent adoption, but we have collapsed it into three.As Cursor's Michael Truell put it in The third era of AI software development:Cursor is no longer primarily about writing code. It is about helping developers build the factory that creates their software. This factory is made up of fleets of agents that they interact with as teammates: providing initial direction, equipping them with the tools to work independently, and reviewing their work.The agent should not sit solely inside the developer's flow. It should be setup to work in the background so that you can give it a task, a repo, a machine, a shell, a browser, tests, memory, and review loops to go do the work somewhere else.In less than a year, the sentiment has shifted from avoiding multi-agent systems:to suggesting approaches that actually work:From coining “context engineering” to building the infrastructure behind Devin's 7x PR growth and jump from 16% to 80% of commits across Cognition repos, Walden Yan has had a front-row seat to the background-agent shift. In this episode, Cognition co-founder and CPO Walden Yan joins swyx alongside Cole Murray, creator of OpenInspect, to unpack why everyone is building their own Devin, what changed after the December 2025 model inflection, and why “spec to pull request” is now becoming a real production workflow.We go deep on the architecture of background agents: harness-in-the-box vs out-of-the-box, why Devin separates the “brain” from the machine, why repo setup is still one of the hardest problems, why Docker is not always enough, and how full VMs, snapshots, scoped secrets, GitHub bots, Slack integrations, and video-based testing all fit together. Walden and Cole also dig into memory, MCP limitations, multi-agent orchestration, AI code review, SRE auto-triage, PMs shipping code from Slack, Windsurf 2.0, hybrid frontier/sub-frontier systems, and the real failure mode of uncontrolled vibe coding: your codebase regressing to your worst engineer.And as agents eat software… and software eats the world… you can draw the conclusion on what is next:We discuss:* Why the engineering world is waking up to background agents and cloud agents* The December 2025 model inflection that made spec-to-PR workflows practical* Devin's 7x merged PR growth and rise from 16% to 80% of commits* Why Cole built OpenInspect as an open-source background-agent system* The economics of $20/seat agent products and why monetization is tricky* What Cognition actually sells beyond Devin: infra, onboarding, integrations, and adoption* Harness in the box vs out of the box, and why architecture matters* Why Devin separates the brain from the machine for security and permissions* Repo setup, scoped secrets, Docker Compose, and agent-ready dev environments* Why full VMs matter when agents need to run real applications and test them* Android, macOS, Windows, nested virtualization, and machine-specific agent work* Why testing is much harder than “computer use”* Screenshots, video verification, and the “I know it works” merge moment* GitHub UX, Devin Review, AI reviewers, and agents responding to PR comments* Why MCP alone is not enough for first-class Slack and enterprise integrations* Memory, Knowledge, skills, Claude.md, and why retrieval is still unsolved* Devin's auto-generated memories and the challenge of memory pruning* Always-on agents as permanent PMs for issues, tickets, and product areas* Sub-agents, meta-Devin management, and what multi-agent systems actually add* Why pure auto-merge vibe coding breaks down after about two weeks* AI code smells, lint rules, reward hacking, and Semgrep for agent-written code* GitAI, inline context, and preserving the “why” behind code changes* Local testing, mock servers, older codebases, and preparing companies for agents* Windsurf 2.0 and the handoff between local foreground agents and cloud background agents* SRE auto-triage, support workflows, and agents as first responders* PMs, marketing, and non-engineers creating pull requests from Slack* AI agent budgets, $1k-$5k per engineer spend, and hybrid frontier/sub-frontier systems* The rise of autonomous coding factories and who Cognition is hiringWalden Yan* X: https://x.com/walden_yan* LinkedIn: https://www.linkedin.com/in/waldenyan/Cole Murray* X: https://x.com/_colemurray* LinkedIn: https://www.linkedin.com/in/colemurray/* OpenInspect / Background Agents: https://github.com/ColeMurray/background-agentsTimestamps00:00:00 Introduction00:00:43 Why Everyone Is Building Their Own Devin00:01:57 Devin's 2025 Ramp: 7x PR Growth and 80% of Commits00:03:49 OpenInspect and the Rise of Open-Source Background Agents00:07:59 What Cognition Actually Sells Beyond Devin00:09:56 Background Agent Architecture: Harness In vs Out of the Box00:12:08 Separating the Brain from the Machine00:14:07 Repo Setup, Secrets, Docker, and Full VMs00:19:13 Why Testing Is Harder Than Computer Use00:22:40 Video Verification and the “I Know It Works” Merge Moment00:23:19 GitHub UX, Devin Review, and AI Code Review00:25:42 MCP, Slack, and Enterprise Agent Integrations00:28:59 Memory, Knowledge, and Always-On Agents00:36:16 Sub-Agents, Multi-Agent Orchestration, and Meta-Devin00:43:55 Vibe Coding, Auto-Merge, and Codebase Decay00:48:38 Agent Infra, VPCs, Cloud Providers, and Fast VM Restore00:52:25 AI Code Smells, Reward Hacking, and Code Review Systems00:56:10 Making Codebases Agent-Ready00:58:30 Windsurf 2.0 and the Local-to-Cloud Agent Handoff01:01:15 SRE Auto-Triage, PMs Shipping Code, and Agent Use Cases01:04:32 Agent Budgets, Hybrid Models, and Autonomous Coding Factories01:06:51 Hiring at Cognition and OpenInspect Consulting01:07:45 OutroTranscriptIntroduction: Walden Yan, Cole Murray, and Context EngineeringSwyx [00:00:00]: All right, we're in the studio with Walden Yan, co-founder of Cognition, CPO.Walden [00:00:08]: Happy to be here.Swyx [00:00:09]: Which is a cool title. And coiner of context engineering.Walden [00:00:15]: Although I think there are many people who'd used the terms in various ways beforehand, but I did find that people, both internally and externally, enjoyed the upgrade from prompt engineering or model wrapping into maybe a more thoughtful way to build agents.Swyx [00:00:33]: For those who haven't caught up on that, I have on screen the Don't Build Multi-Agents post, which you should go read on and we might refer to, and Cole Murray, who created OpenInspect.Cole [00:00:43]: Great to be here.Swyx [00:00:43]: So let's talk about it. Everyone is building their own Devins. What's going on?The December Shift: From Handholding Models to Autonomous PRsCole [00:00:51]: So I think the engineering world is waking up to this idea of background agents, cloud agents, whatever you'd like to call it. And I think we saw a shift around the December timeframe of 2025, where the models Opus 4.5 and GPT 5.2, they reached a capability where we moved away from handholding the model and being able to actually more or less autonomously drive the model. And what I mean by that is that we could pretty much go from a specification to a completed pull request, assuming the spec was good enough, with very little friction. And that paradigm alone, I think, changed a lot of how we interact with agents, and opened this world where background agents became more practical.Swyx [00:01:41]: I think for Cole, everyone experienced this in December, but I feel like there was just this increasing ramp, right? There was this moment which was, I think, Sonnet 3.7, where, You guys rewrote Devin in one night or something. So describe 2025 or how it felt from your side.Walden [00:02:01]: In retrospect, we always thought it was ramping up, but then even now, over the last three, four months from today, it's been ramping up even faster. So it's almost funny to be talking about how, big of a leap Sonnet 3.7 was, and honestly, a lot of it was stripping out parts of Devin that were no longer needed with that jump in of intelligence. But I also just think that a lot of the recent leaps, especially, you look at, models like Opus and the latest GPT models, they are reaching levels of autonomy where people are actually finding that they actually can just be hands-off. And people who were once debating, “Oh, do I need to be in the weeds with my model in the IDE? Can I just completely move it off into the cloud?” That's a more serious conversation, and we've seen that in all of our growth charts. Internally there's this funny graph where our usage has, of PRs, our merged PRs, has grown 7X since I forget what it was called.Swyx [00:02:57]: I think Dev, maybe tweeted that. Yes.Walden [00:03:01]: it grew like 7X over, the last, I think it was, two months, three months, something like that. And then you see our engineering headcount growth. It's, gone up by, 10% or something.Swyx [00:03:11]: We were, we were afraid To release this. So this is Devin commit percentages on all Devin repos, was 16% in January and now 80% in March.Walden [00:03:25]: It's a big shift right now. And so it makes sense that a lot of people are now thinking about, buying Devin, but also maybe, trying to build their own and there's Lots of I have a lot of fun building Devin, so I can see why other people would want to build their own cloud agents as well. Matt, well, maybe it's good to hear, what initially inspired you to try to build OpenInspect?OpenInspect: Ramp, Cloud Agents, and Open SourceCole [00:03:49]: OpenInspect came about, through primarily my clients observing how they were using tools like Claude, OpenAI's Codex at the time, and seeing some of the friction that they were having with it. Primarily the Claude was being used through Slack, and a big issue they ran into was that the sessions that were launched were specific to whoever called it via Slack. And so if a PM was the one who invoked the session and they would then go to pass context to engineering can't see the session. And that in itself was a deal breaker because the PM, “Hey, engineering, can you jump in?” But there's nothing to jump in on unless they're copy-pasting out or the single response that came back. And so seeing some of these problems, I had built a similar architecture internally, just to experiment with, test out different ideas as this trend of moving off of localhost was starting to become, And as Ramp released their blog post, I had a lot of the pieces for this already in place, and just thought it would be funny to, see what Claude could do just purely from the blog post. And on my X account, there's actually a thread of where I live tweeted, going through thisCole [00:05:14]: comparing GPT and Claude as both of them are going through it.Swyx [00:05:17]: On the announcement thing or something else?Cole [00:05:19]: right after it got released. We can put it in the show notes. Yeah, it was helpful that I had already knew how to verify the system. I knew what I was looking for. I think Ramp did a great job of really illustrating, the technical aspects of how to build something. It was much more than just like, “Hey, we built a great system.” It was, “And here's how you can build it too.” And so, I resonated a lot with that, just with the problems that I was already seeing, and I thought that, looking around, I didn't really see anything in the open source community that, met this type of system. I think there's a lot that run, in localhost like Superset, Conductor, and many others.But nothing that was actually running in the cloud. And so, I built it, and I thought it was interesting to just open source it and allow anyone to then have a foundation that they can mix and match on top of.The Business of Background Agents: Open Source vs. DevinSwyx [00:06:16]: So literally after Devin was launched was, there was OpenDevin Which became All Hands. I don't know if you tried that orWalden [00:06:22]: I was going to say, one of the things that interested me a lot with OpenInspect was, you didn't try to go make it then something you monetize. There are a lot of, I think, these open source projects would then go and really try to, raise VSwyx [00:06:36]: That's why no OpenDevin. Yeah.Walden [00:06:38]: yeah, and how did you think about that? I thought that was very interesting.Cole [00:06:44]: I thought, and just what I had seen across my clients, was that having a background agent system is going to become a critical infrastructure within their company. And so because of that, I think that I wanted to open source it so that they could fork it and put in whatever customization they wanted. To that question though, I get asked all, “Oh, are you going to raise? Are you going to turn this into a service?”Walden [00:07:08]: I'm sure you've gotten offers.Cole [00:07:09]: but primarily I don't want to do that for a few reasons. One, I think that I don't want to compete for, $20 a seat. I think that is just a really difficult business. I think it's very easy to copy the main pieces of it. Again, I built this fairly quickly. And I think because you are not owning, I guess, the entire stack, it's hard to monetize. You have money being made at the sandbox layer with Daytona, E2b, many other players. You have money being made at the model layer. And you sit in this weird in-between gray area where what are you actually selling? You're selling, I guess, the infrastructure. You're selling, the integrations maybe.Swyx [00:07:55]: let's ask the guy. What are you What are you selling?Walden [00:07:59]: Well, yeah, there's multiple layers to this in practice, and actually it's funny you mentioned the infrastructure, ‘cause when we got started building Devin as well, we had to go figure out how to make the infrastructure as well because,Swyx [00:08:10]: You had to build this two years before everyone else,?Swyx [00:08:15]: Including, the model sideWalden [00:08:17]: It was not, it was not very polished at the start, when we just built it off of raw VMs from cloud providers like EC2, the boot up time was so slow, I think, And especially then, turning off the machines, saving them, and then to be able to bring them back up again when the, when you want Devin to wake up again later. It would just be out cold for like 10 minutes because that's just how long these systems took. They were not built for this repeated down and up usage. And so we actually had to go do all of that. And as a result now, one thing we offer when we go and sell Devin to people is, you don't have to worry about all the compute side of things. We'll make it work. We'll make it work in your cloud if you want it to. But aside from the product, and I want to go into the agents and the tuning of the intelligence part later, but I think a big part of what we do at Cognition as well is to just make sure that your company learns and uses and adopts these coding agents. ‘Cause I think for especially the largest enterprises in the world, you find that there is a lot of people who want to move over to using AI for their day-to-day workloads. But because of the way projects are planned, because, not everyone is literate in using AI in these ways, having a team of engineers who can actually go in and onboard you, set up all the integrations you need, the automations you need to really get to that level of, leverage with AI, is super helpful. And so We do that. We show thought partners to the customers that we work with as well.Swyx [00:09:56]: So let's talk about, architectural stuff. I think that's always, that is something that was the topic of conversation between the two of you. Is this, the mental model that you want to start with or something else? I'll just leave the floor open to you guys.Agent Architecture: Harness in the Box vs. Out of the BoxCole [00:10:11]: I think, maybe we can start here as just a general what are the pieces of a background agent system. And then maybe we can go into some of the nuances of, Decisions that you can make.Swyx [00:10:22]: But I guess I also Like, what, maybe what Walden is saying is the agent is like in this open code box, I guess. Right? This is infra, and then there's, that's the agent. And you had this discussion about whether you put the agent in here or in Out externally. Can you tease that out?Cole [00:10:39]: In a background agent systems, you have a decision to make of where the agent is actually going to run. This is typically described as the harness in the box or out of the box. With running the agent in the box, you're making some trade-offs by doing that. The negative trade-off you're making is primarily security. Because the agent is running in that box, unless you otherwise design it, all of your secrets need to go into that box as well. And given the nature of AI, it can be unpredictable, and you could very easily end up accidentally exfilling your secrets, or other unintended behavior. Now, the out of the box is the idea that we are going to have the actual agent running not directly in the sandbox, and we will have, quote-unquote, the brain of the agent running in some type of worker, control plane. That sandbox then is going to serve as the hands where the brain is basically operating and making tool calls into that environment to manipulate it. I guess other trade-off that you're making between the two systems is that, in my opinion, running it out of the box is much more complex because, you have state that has to be managed, whereas if you're running it in the box, all of the state of that agent is actually in the box, and yes, it's you could persist it elsewhere, but it's all localized and you have less concerns to worry about.Walden [00:12:08]: I think a lot of that, what you mentioned, is why we actually from the start built Devin to what we called separate the brain from the machine. The other thing that this allows you to do is reuse any existing infrastructure you have for dev boxes Perhaps. And so you don't have to worry as much about making a new type of dev box that has all the dependencies the brain needs, as you mentioned, the secrets the brain needs as well. One thing that we've seen some customers run into is, you have a GitHub app and you want Devin, your agent, whatever, be able to interact with GitHub through this application, but then you have different users with different actual permissions. If they are all interacting through the same GitHub app and there's no actual, separation between the system that decides, what it does and the actual secrets on the machine, then you run into an issue where, okay, it's hard to do the separation. But in practice, with Devin, it's much easier because we just say whatever you put on the machine, that is, the scope of basically what the user is free to do, what the agent is free to do. So only put the most scoped secrets on that machine, and then the brain is fully not accessible from the machine. So you don't have to worry about messing with the, any of the most secure parts of the brain if the user is free to do whatever they want with the machine.Swyx [00:13:31]: I was going to just bring, I have this, chart from OpenAI, where I don't know if this is, in the box, out of the box. That is something that they do use to describe it. And then also recently Anthropic did, managed agentsSwyx [00:13:44]: Which is, this is their thing. I don't know. It's all, it's all variations of the same pattern, right?Cole [00:13:49]: So this would be out of the box.Swyx [00:13:51]: Which, is preferable for them because it's less work?Cole [00:13:56]: I would say it's more work.Swyx [00:13:58]: It's more work?Cole [00:13:58]: But it, in my opinion, it is the better architecture of the two. It's just, you're taking on a bit of complexity by doing that.Repo Setup, Docker, and VM-Based Development EnvironmentsWalden [00:14:07]: One thing I've not seen a lot of other players do well is how do you manage what's actually on the box? And this can be complex for many reasons. Let's say you have a big repository that's changing and updating a lot with changing dependencies. How do you make sure that the working environment of the agent actually stays up to date, has all the credentials it needs to, let's say, run the app and test it, and all the things you want your autonomousSwyx [00:14:34]: So a repo setup.Walden [00:14:35]: Exactly. So in, internally At Cognition, we call this repo setup.Cole [00:14:39]: The hardest part ofWalden [00:14:40]: It's been a perennial problem since the start of the company, of how do we help people get this set up? Because not everyone just has, working cloud environments working out of the box. And do you find this to be a common problem withSwyx [00:14:53]: How do you solve it?Walden [00:14:53]: Your clients?Cole [00:14:54]: This is a very common problem, and through my consulting, this is a lot of what I help teams do. A lot of teams don't really have great developer environment setups, if any. A lot of the times it's, “Go talk to Bob and get the secrets,” and that obviously doesn't work when the agent needs to actually set this up. And so a lot of that, most teams are using Docker Compose or some type of microservices. And so for theSwyx [00:15:19]: Even in prod?Cole [00:15:20]: Not in prod. With the OpenInspect, you are using this primarily to interact, and make code changes. There is other use cases, but you can hook, whether through CLI, MCPs, other tools, you can then hook that into your production systems primarily for, SRE type use cases. But you are not, necessarily, trying to test your prod internal microservice through the system.Walden [00:15:48]: And you mentioned Docker Compose. I think one direction we saw some of our friends take early on was, using Docker containers as the level of abstraction for their models. There's lots of reasons, I think, why Docker containers are not great. One thing is, Docker container's not really a true security boundary, for one. But the other is, if you are running real applications, a lot of times those applications use Docker, and then you have to think about Docker in Docker, which is, really weird. And so I think part of, the really hard challenge of getting VMs to work, why did we do that? Well, it was because we realized that you actually needed, full VMs to be able to do these types of things. And especially nowadays where there's actually value in running the application and clicking around and sending you screen recordings of these things. The value just, keeps adding on top of that. But it is a decision I see people run into when they try to build their own systems, is, “Oh, do we, in addition to this, do we put the agent in the machine or out of the machine? Do we use Docker? Do we use something else?” What do you recommend people nowadays?Cole [00:16:57]: I think Docker is a good solution for maybe not running the agent, but running your infrastructure, because that is more or less the same setup your engineers are probably already using. If they're not, then I don't know what they're using. But they're probably already using Docker Compose.Swyx [00:17:14]: I've always had a small candle for web containers. I don't know if you guys have tried them before.Swyx [00:17:19]: To me, they were, supposed to be like Docker Light.Cole [00:17:22]: Is it?Swyx [00:17:22]: I don't know.Cole [00:17:22]: No, I haven't tried it. But yeah, I think any environment that you've set up that is a good experience for your developer naturally lends itself to being easy to set up for the agent. And once you figure out that local developer story, you've more or less solved the agent in a sandbox, environment setup. OpenInspect does have hooks as well, where you can, run a setup SH script that will pre-install everything. You can then pre-snapshot that build so it starts instantly, and then there is a second hook to actually then, restore the state of the sandbox when it comes back. And so you can already have all of those microservices running and basically get the same experience that you would on your machine within the sandbox.Testing Agents: Computer Use, Screenshots, and Real App WorkflowsWalden [00:18:08]: Another thing that we've been thinking a lot about is like Different VM service offerings. Have you had customers where they needed like macOS specific VMs or like Windows specificWalden [00:18:20]: VMs?Walden [00:18:22]: There are like many technologies in the world that only work on specific types of machines, right? If you're building a.NET application that has to run on Windows or like, maybe more commonly if you want to build iOS or macOS Does that workSwyx [00:18:32]: Does Commission supportSwyx [00:18:33]: Choices like that?Walden [00:18:35]: The fundamental architecture we do, because we do the separation, it does support, but the actual work in progress is happening right now on these. Another thing that we've actually recently added support now for, it's in beta, is doing Android development. To do that, we needed to support, I think, nested virtualization within our machines because the VM itself is like a, is a virtualized Firecracker instance, and then you had to then run another Android emulator inside. And there's like weird performance issues that like, it, which is why it's like still in beta. We have to think through these problems, but it unlocks a lot for anyone who wants to do Android development.Swyx [00:19:13]: I was trying to find like a reference video for the testing thing. I couldn't find it, but I think you worked on the testing, capability. Why call it testing and not like computer use or I don't know, it's, what's the general Category of problem?Walden [00:19:26]: I think that when people think about the ability of an AI to run your app and test it, I think they actually over-index on the computer use part of it because computer use in my mind is the literal, okay, you want what button you want to click. Can you emit the right coordinates to go click that button? I think testing is actually a really interesting likeWalden [00:19:48]: Problem-solving, challenge for these AIs because if you wanted to do arbitrary testing, imagine you make a change that spans the frontend and the backend, maybe, even some other like even more deeply nested service. To actually test that change, we have to reason through what-- how do you first run these applications to orchestrate with each other with the right version of the code? Then, okay, how do I trigger the feature or how do I make the thing actually happen? And this can get arbitrarily hard, maybe you have to be an admin. Maybe a certain thing has to be feature flagged on. Maybe, you have to like run two sessions and then send us a very specific word into one of them to trigger a specific behavior. And figuring out how do you do that requires a lot of code base context, requires, a lot of orchestration that we've specifically done. And in some cases, we found that you actually, no one frontier model can actually do this full end-to-end task itself.Walden [00:20:42]: We've seen cases where we actually had to orchestrate different frontier models together to solve this problem together. That is where we spend most of our time when we think about this testing problem, not so much the computer use part. Computer use for what it's worth has gotten a lot better with recent models and it's made that part of the job certainly easier.Swyx [00:20:58]: Especially with like even 4.7, that they released yesterday, apparently like way better in terms of the vision stuff, which is going to be encompassing computer use.Walden [00:21:08]: Having evals for all these as well is something that like takes a while to build up. And having the evals be right is tricky as well. Do you ever see like, clients who are building their own agents have to start standing up evals to make sure things don't regress?Swyx [00:21:25]: Not so much evals in the traditional sense, but specific to the testing part that has just gone in. I just added support for screenshots And in theory you can also do video. I need to put in a plugin to do that. But they do show up natively, and it was a very heavily requested feature, especially after Cursor's recording came out. I think that was very enlightening for everyone of like, “Oh, this is a very good feature to actually have.”, I think with Devin you guys have had this for a while.Swyx [00:21:57]: Oh, yeah. See how screenshots work. Yeah, I don't know if there's anything, super and not obvious. It's like once what feature to build, you can just prompt it and it Will mostly work.Walden [00:22:09]: I think to Walden's point, though, the computer use is a subset of the larger testing problem, and I think that's very specific to the code base that you're working and it's not something that, out of the box that you could just solve it. The-- you do need the code base context to actually know how to test it. And I think in the case of a background agent system, you fortunately do have that code base locally that what is changing and could then inspect it and use that to drive the model.Swyx [00:22:40]: For those who haven't seen it before, this is an example of how it works. You, after the PR is done, you click testing approved, and then it sends you back a video. What I really like is that it labels, It's very small here, but it actually labels what it's testing. And then it-- and then you actually see the cursor and everything. So I don't know, yeah, the engineering in this, just Whatever you want to show. ‘cause this is like, this is one of those like, oh, few of the AGI moments, right? ‘cause Once I look at this, I actually don't I wish I can just merge inside Of Slack instead of going to GitHub ‘cause I don't need to see the code. I know it works.Walden [00:23:19]: Maybe a new feature in Cursor. Yeah, the annotations at the bottom was also a big difference for me when I, when I added those.Swyx [00:23:27]: It's just like, what am I looking at? What are you trying to demonstrate?Walden [00:23:30]: Exactly. There's a surprisingly long tail of small details that ends up making a big difference for this end metric of like how fast do you actually merge the code in. One experience that we spent a lot of time tuning early on was what is the right experience on GitHub for these tools. Because I think, most tools out there when you build the agent, you'll think about, oh, it'll create the PR for you. We try to take that a step further and say, “Oh, what if we actually made sure you could interact Devin, with direct Devin directly on GitHub?” And so we made sure that you can comment on GitHub, and Devin would actually receive those comments and address them back. But there's actually quite a bit of tuning you have to do here because you can imagine that actually like-We recently have Devin Review, for example. Devin Review will post comments on his own PR And then Devin has to then goGitHub Workflows: Devin Review, Comments, and PR AutomationSwyx [00:24:23]: He answers his own comments, which is Really loopy. So like, yeah, I like that it just updates here that it's, that I have commented But usually it's just me saying like, “Hey, merged, fix any merge conflicts.”Walden [00:24:37]: The, so when Devin fixes his own comments, you might be scared that, oh, maybe I'll infinite loop. But we've put a lot of work into making sure it doesn't, both by making sure that the comments are high signal, but also that the agent is thoughtful about what comments it immediately goes and tries to fix, and what comments it's like, “Wait a second, I think you're wrong.” Actually, that's one of my favorite moments is when Devin tells me that I'm wrong, when I try to get it to do something different. But tuning that behavior, actually makes a big difference in terms of how useful the actual GitHub experience is.Cole [00:25:06]: I think to touch on that as well, I think having the AI reviewer integrated into the system is a critical part of this background system. OpenInspect does have that. It has a GitHub code reviewer that you can control the prompt. It does do comments as well. It doesn't do them automatically yet. The capability is there, but it's not fully used.Swyx [00:25:27]: So you have to ask for it?Cole [00:25:28]: you do, yeah. You can tag it on GitHub, and then whatever you named your, GitHub bot, it will then follow up on it. It will then, if you have merge conflicts or whatever you have asked it to resolve, it will then resolve it, but it doesn't do it automatically yet.Integrations: Slack, MCP, and First-Party Agent InterfacesWalden [00:25:42]: Well, I'm curious, what is, the most common thing that people end up requesting, that they still need on top of OpenInspect when you help them go implement it?Cole [00:25:52]: I think a lot of it comes down to actually integrating it into the company. It's one thing to have the background agent system set up, but if it isn't actually integrated into your larger ecosystem, it isn't that useful. It is useful to be able to kick off sessions, but what we really want to be able to do is hook it into all of our other systems, whether that is the production database with read-only credentials, the logs, a Confluence or internal knowledge-based system. I think that is where I see the huge leap for companies, and that can be a challenge for companies as well who are maybe not familiar with exactly how to approach it, especially if they're in environments that have more compliance type things where, access control can be pretty big and how do you deliberately think about these problems, I find to be, one of the problems that comes with a system like this.Walden [00:26:46]: The thing we found is So, MCPs, obviously it has been like this, really big explosion of, oh, you can go, integrate it with all these different things. But to actually get the integration right and the and get the right experience, oftentimes we found that we had to go build our own ad hoc things. I think Slack is a great example of this. You could give your agent a Slack MCP and okay, it can post messages back to you on Slack. But we actually use Devin like a coworker in Slack, and that's how it's been built from the ground up. But to do that, you actually need to, support webhooks that come back, right? And then Devin has to respond in a natural way and then hopefully don't spam your threads too much and annoy the people in your company. So you got to tune that experience just right. Especially when there's a lot of back and forths, we find that we actually have to go beyond the simple MCP integrations in these places.Swyx [00:27:39]: I just pulled up the MCP marketplace. I know this is a Fair amount of work. Is the answer to eventually take first party control of all the top MCPs? Is that theWalden [00:27:48]: I would love a world where you could have something that's more expressive than MCP. That, goes both ways, not just a set of tools, but a proper system that interacts back and lets it Have the right experience with all these interfaces.Swyx [00:28:03]: So there actually is sampling in the MCP spec, but nobody Uses it, right?Walden [00:28:07]: And so I think that's the other part is, actually we found that when the MCP spec starts to get too complicated, it starts to lose its original promise of Being like a simple one-step connect. Now then we have to go figure out how to support all these different variations of things and It starts to look a lot like just building the first party integrations in a lot of these cases now.Cole [00:28:29]: I think it matters, too, how critical it is to your company, right? If this is something that nearly every session is going through, it probably makes sense to own it so that you can make optimizations on top of it Versus just whatever is off the shelf.Swyx [00:28:43]: Awesome. Other than MCPs, what else, sorry, well, I don't know if that's Narrowing in too much on, integrations. But what else? What other elements of building OpenInspect or Devin that you guys really sink on?Memory and Knowledge: What Agents Should RememberCole [00:28:59]: I think, a problem that comes up very frequently is this idea of memories or knowledge base.Swyx [00:29:05]: Oh, boy. How do you solve it?Cole [00:29:08]: so not solved yet, is the short answer.Cole [00:29:11]: it's something, there's a open issue for it, someone asking about it.Swyx [00:29:16]: There's, I, D Wiki hasn't indexed anything about memory yet.Cole [00:29:20]: how I'm seeing it solved across my clients is primarily through skills. I find that skills can be a good gap within that or updating Claude MD, but I think memory as a whole is a pretty unsolved problem, and it is why I've been hesitant to add it. I think there is parts of memory and that can be addressed, but I think as a whole it's a very difficult retrieval problem.Swyx [00:29:44]: Oh my God. RAMP didn't write anything about memory? I see zero search results.Walden [00:29:50]: No. Memory can be quite tricky to get right because it's the retrieval, but also the generation of the memories that can be really tricky. You don't want it to just like Remember very specific details.Swyx [00:29:59]: Walk us through the Devin memory journey because I know there's been a journey.Walden [00:30:03]: the first version of memory that like stuck around for a while was A system we have called Knowledge. And the idea was we wanted it to pick up things over time and not need the user to be proactive about teaching Devin things. So, okay, any time you remind Devin, “Wait, no, that's not quite the way you're supposed to use Git”Like, we actually want Devin to say, “Hey, do you want me to actually just remember this for the future?” And for you to just basically quickly approve or reject and for it to build up over time. ‘Cause I find that, 95%, I think, or some crazy stat like that of the memories that Devin has are all through these auto-generated things. Very few people actually just want to sit down and write big docs on Here's how you're supposed to work with the technology, et cetera. The generation and the retrieval has been something that we've been trying to tune a lot over the years. Generation, you don't want it to remember something like, if you asked one time to like, “Oh, please open as a draft PR,” you don't want to be like, “Oh, everyone forever now should get their PRs as draft PRs.” But you do want some, conveyor. Maybe you want to say like, “Oh, Cole generally likes, things to be created as draft PRs.” Same with retrieval, if you have thousands of these memories, how do you actually make sure they're retrieved at the right time? And that can be quite tricky to do right without exploding the context with a bunch of useful yeah, useless information. Surprising amount of just, eval work to just make sure that, memory is, remains a reliable system as new models come and go.Cole [00:31:31]: Do you have anything that you could share on, memory pruning? And like the temporal aspect of memory?Swyx [00:31:36]: Deleting and forgetting?Walden [00:31:39]: The, today, the, So the things they could do is it could edit memories. And so if your memory used to say like, “Oh, Cole likes to open everything as like a draft PR,” then you can imagine, “No, don't do that.” And then it'll say, “Oh, do you want me to update the memory to be Cole now want everything as, open PRs?” I think that at the same time we don't know if this is going to be the final version of the system. Whatever we have here will probably, translate into the new system that we'll be coming up with. But I think one big difference between two years ago and today is these agents are really good at using anything that resembles a file system natively. And so part of us are, is thinking, “Oh, should we rebuild memories to feel more like a file system that we let the agent navigate on its own?” That's been an interesting exploration. Also similar ideas in the scale space.Swyx [00:32:35]: I am pulling up OpenClaude's memory thing right now. So memory, OpenClaude has like this like daily memory journal thing, right? And you can I mean, that is a file system you can grep through and is a source of truth. I don't know if it's the best. It's probably super noisy, but at least, if you lose something you can discover it or you can apply some, forgetting algorithm to, more ancient memories that don't get recalled again or something. I don't know.Walden [00:33:01]: One thing we've been trying to do to push the boundaries of how you use agents at your company is letting an agent basically have a very similar file, a memory.md or something, and just like be your permanent PM for a specific set of issues maybe. So we have like some Slack channels internally, maybe a Slack channel dedicated to, a specific product like DeepWiki maybe. And you can imagine that, or you want a Devin that never stops, it's just always awake, but it has this like memory dock that it can just maintain for itself about, okay, what are like the number one priorities of what we have to fix and prioritize? Who is responsible for some upcoming work? Maybe they'll even Devin will even tag you on some recurring basis. And so it's been an interesting move to see, okay, how can we actually use Devin for more than just engineering? Can we actually upstream above the engineering process and maybe it's just Devin creating tickets, which then maybe some humans do, but then maybe other Devins do.Swyx [00:34:00]: One of my more fun automations is go research competitors and just suggest stuff to me on a weekly basis. That's the automation. I can't find it right now, but basically it just like, “Look at competitors and suggest things.” “And here are three things that you've suggested that I don't want any more of,” and you just stick that in the prompts. But like I wish actually So for like when I, for example, when I reject a PR, I wish that it updated memory so that I can then just not have to go up, go back and update the scheduled, sync, but anyway, feature request.Walden [00:34:31]: what? We might change it soon. I guess OpenInspect, in the time you've been around, has there been anything you tried to implement but then you had to like undo and like do a different way?OpenInspect Architecture: Webhooks, Control Planes, and Agent StateCole [00:34:41]: Nothing yet, but something that is on my mind. The initial way that I built it was that each of the integrations lives as its own package. And so you have The Slack bot, which is what's handling the webhooks, and then is basically interacting with the control plane. As I'm seeing the system starting to be more integrated, specifically with the GitHub bot integration, I'm considering bringing that all into the central control plane because especially now I want to start, And a request that I'm getting is the ability to monitor, the actual, pull requests being merged, as well as just tracking ofSwyx [00:35:19]: What do I have open?Cole [00:35:21]: What do I have open? How many of these are getting merged? How many comments are showing up? To just understand the health of the system. And so in the case of a GitHub app, you only have one webhook. And so then it's a question of do I put that webhook in that GitHub bot package? That's weird. It doesn't really make sense to live there because that package is more for like the code reviewer. Or do I like centralize it? So that's something that's on my mind of, making that decision. I think the other one we touched on earlier is the harness in the box versus out of the box. I think long term the architecture will eventually come back out of the box. Some of the newer tools that I've added are calling back into the control plane so that you don't have the secrets in the sandbox. And so I think long term I probably will pull the actual, agent out of the box, but I think for now it's fine.Subagents and Multi-Agent Systems: When Parallelism Helps or HurtsSwyx [00:36:16]: Just, a quick question on pulling the agent out of the box. I'm One thing I'm very bullish on this year is agents calling other agents or spawning sub-agents or Whatever you want to call it. Does that make it harder or easier? I can't tell. Because if the harness is in the box, you can just spin up more boxes. If the harness is outside the box, then you're, it's less easy because you are, you have a unicorn pet of a, of a harness that's, living outside the box.Cole [00:36:45]: In theory it would be the same way, right? Whether, one agent has launched many, sub-sessions within it, OpenInspect, for example, can launch sub-sessions and actually create other environments and then monitor them. In the case where it is out of the box, that would basically just be an additional session that's running. And so that session is also running outside of the box. It's running in your worker plane, wherever you're running this. And then you really just have to think about how does your top level agent then interact with it. I do think it can be more complex, just ‘cause again, you have now a more difficult architecture. But I think if you figured it out once, it's probably fine.Swyx [00:37:26]: Well, then I'm just, throwing it open to you in terms of, I call this like meta Devin management. Which is like the, Devin's calling Devins or Devin scheduling Devins or querying trajectories or anything like that. What have you built or unshipped, anything?Cole [00:37:46]: I think one of the surprising things we've seen is that a lot of the ways that, these, separate agents work with each other, and you want them to, parallelize their work, has still mostly followed the same manager sub-agents regime. And a lot of people I think are excited about this world where you have swarms of agents that, talk with each other all over the place. We've actually given Devin an MCP so they can just go arbitrarily message other Devins And create new Devins, et cetera. But I guess, it somehow creates, a really chaotic world in that sense. And so we've still found that most practical use on a day-to-day basis has been one single Devin.Cole [00:38:33]: Figuring out how to segregate the work and get, have other Devins work on it in, a relatively isolated sense, each with their own boxes Not sharing machines, so there's, a very little room for conflict is the regime that you have to create today.Swyx [00:38:50]: I'll call out, the experiments from Cursor, right? This is Wilson Lin's work on Single agent to multi-agent, and you're obviously famously on the side of don't build multi-agent. But they went through the whole thing, only to arrive at, this Which is exactly what Devin has, I think.Cole [00:39:08]: I think there will be a revision to that post at some point AboutSwyx [00:39:12]: Tell us about itCole [00:39:12]: I think multi-agents were very much not at all possible a year ago. You do see more multi-agent experiments today, but you can argue, are they really multi-agents, or are they just just, tool calls,? There are people who, will create sub-agents to go look for XYZ file, XYZ implementation. Has really nice context management benefits because all of the tool calls and tokens that it spends then get collapsed back to just the answer for the main agent. There's a lot of benefits to doing this. We basically have Devin do this with Deep Bookie, make a call out to Deep Bookie, give you back the results, but that feels like a tool call,? It's not like these, two collaborators actually talking back with each, back and forth with each other. But I think the thing that gives me the most bullishness that multi-agents might actually be possible is actually what I said earlier about Devin will actually sometimes tell me I'm wrong and push back, and I think that demonstrates a level of maturity and communication today that makes a multi-agent world possible. One, can two agents who have seen different information come back to each other and actually figure out who is right, what is the correct implementation? They're not just, yes men. Claude, I guess is like, used to just say, what is it? “You're right,” or,Swyx [00:40:25]: “You're absolutely right.”Cole [00:40:26]: “You're absolutely right.” Yeah.Swyx [00:40:28]: The Have you seen, did you seeCole [00:40:29]: The age is overSwyx [00:40:30]: The Codex app troll in Topic? This is the Codex app. Inside of Settings, there's a little, there's a little Easter egg, right? So if you go to, the Themes or Appearance, right? There's all these, color codes, and the top is absolutely, and it's the Topic's colors. Which is such a troll. Anyway.Model Behavior: Pushback, Adversarial Prompts, and Agent SkepticismCole [00:40:53]: I love that Easter egg. Did you discover that yourself?Swyx [00:40:54]: No, it was, someone was, tweeting about it And I was like, I was like, “Is this true?” Because, sometimes people just tweet stuff to, get a rise out of you. But yeah, there you go, in Topic colors.Cole [00:41:06]: Yeah. So yeah, we're out of this regime where, it just says you're absolutely right, and they can have real conversations and real back and forths.Swyx [00:41:13]: You can prompt it as well to be more adversarial or whatever. Yeah. Okay. Yeah, that, I mean, to me, that is more intelligence, right? That is not just something that's, a dumb tool, it's actually pushing back on you I think. Yeah.Cole [00:41:24]: when you mentioned, of course, the blog posts. There was one blog they had where they fed a swarm of agents together and built a browser.Swyx [00:41:34]: That was I think that was the one.Cole [00:41:36]: You can have, likeSwyx [00:41:37]: I think it's the same oneCole [00:41:37]: Creation of it. We found a surprising success of, don't do a swarm or anything, just have one Devin, it does its own context management. Just let it keep running for a while and give it some crazy tasks. I think we asked it to, rebuild, a Windows OS system. And it managed to do it just like, going on for long enough. It'sSwyx [00:41:55]: Was this Andrew's thing?Cole [00:41:58]: there were lots of demos that we ended up not posting, ‘cause at some point we'd just be posting way too much a bunch of, Demos. But I love that because it shows that I think the multi-agent thing still has, a bit of exciting sexiness to it, which is maybe still beyond still, the actual delta it adds to the capabilities of these systems. But it's absolutely the future. I think we're heading in that direction and we can see the progress being made there already.Swyx [00:42:25]: If I were to, make one super minor pushback because I don't feel that confident about it yetCole [00:42:33]: Go for itSwyx [00:42:33]: But I've had Ryan Lopopolo from OpenAI on the pod And he's a super slop cannon, right? Oh my God, that's my coding agent being done. I downloaded this, Peon Ping. I don't know if you guys have heard this. It takes like-, sound packs from popular games like, Command and Conquer and Warcraft, and then it plays it whenever it's done. And so it's like, “Work,” or whatever, “At your command,” or something. Anyway, what I got from the Cursor code base and from Ryan's thing was that there's a slop cannon approach where you try to loosen the single agent's, bottleneck, and I feel like that is, probably an, a very important thing to try to figure out. I don't think anyone's, really solved it. Because then you just have more reviewer slop on top of the agent slop To try to wrangle it all. Ryan will probably very strongly object that I say that he hasn't solved it, but he thinks he's He thinks he's completely solved it. But I think it's still I think it's, very important, ‘cause, that is a bottleneck, right? I feel Devin is slow sometimes Because I'm like, well, yeah, this is very readable and very sensible, but also it is slower than it could be if I just, I want a button to just say, “Just ramp this up 1,000 next parallel, in parallel and just, see what happens,”? And I don't know if that's, feasible at some point in the future.Code Review, Entropy, and AI SlopWalden [00:43:55]: I And we've also run experiments internally where we've basically tried to build entire products, true products that we knew we would eventually ship, but for now, let's try to see if we can do it just by purely, vibe coding on top of each other, auto merge, no code review at all. And then there's this benchmark of how many weeks can you go onto this for Before you say, “We have the trashiest code base.”Walden [00:44:18]: “Let's actually rewrite it from scratch.”Swyx [00:44:19]: Start a new factory, yeah. What'd you find?Walden [00:44:21]: I think we found that the state-of-the-art in December was you can probably, run this for about two weeks. By the end of those two weeks, you'd find that, hey, you want to, change the color of a button. Well, it turns out this button is implemented in, 10 different places, and they, have All these different variations, and oh, you forgot one of them, and actually it's a slightly different color in one spot. And you're like, “Okay, this is too much to work with. Let's actually try to do code review at the same time.” And make sure that we're on top of our software, actually cleaning it up a bit And making sure it's done in a scalable way.Cole [00:44:54]: I think building on that, the idea of, you don't have to look at code, I think is generally a bad idea. And the meme that I have for thatWalden [00:45:03]: What timeline, all right, is Do you think that statement will be true on?Cole [00:45:06]: I think probably for a while it'll be true that you should continue to look at your code. A problem that I see a lot of teams run into that I work with who are embracing AI native, AI first coding, is The meme that I have is that your code base regresses to your worst engineer, because that engineer who is, very gung-ho about AI and is not auditing their code, their pattern starts cementing into the code, and now the AI is referencing their patterns. And so now their if/else block that, is 20 if/elses back and forth, the AI is seeing that as the pattern of how things are done and starts to then exponentially grow this slop. And I find to your point, a pretty good approach to that is having scheduled cleanup, whether by humans or through systems, that are looking for duplication. They then address that. You'll end up with like 12 helpers for how to format a date. And you need to address that, because otherwise it will continue to sprawl.Swyx [00:46:09]: Within balance, I think it's fine to have some duplication, and then sometimes To have garbage collection, right? Yeah. The What I've been, talking about with a lot of engineering leaders is that you want to be very strict about the boundaries between modules, and it's your job as an architect, as a CTO, whatever, to say like, “Okay, here's the hard contract between you guys and you guys. Whatever you do inside this black box is your business. You do whatever. But between these guys, let's be, really damn clear, and any movement must be signed off by a human or me,” or. Then, and like that's that. I don't know if you have any other modifications or advice.Walden [00:46:44]: Well, I guess generally on the topic of, where humans can be useful, I found that ‘cause, some of these, really deep infra problems, sometimes just having a human that just has, really deep expertise can make a big difference. I've actually seen this come into play when actually building agents. So we've had a few friends now, try building their own coding agents, and I think one same problem that I recurringly heard a lot of them run into was this problem of like, “Oh, Grep is really slow on our agents' machines.” And so a lot of them, I assume because they're using AI and they themselves don't have, super deep infra background knowledge, say, “Okay, we're going to go build our own custom Grep index. It's going to be really fast,” and use that as a way around this problem. When we ran into this problem About like, maybe like a year and a half ago when we were, in the early days of building Devin, we obviously didn't have AI then. We just asked our, how to, how to do this. You can just swap out a new Grep index, so.Infrastructure Details: Grep, File Systems, and SandboxesSwyx [00:47:45]: What do you mean you hand-coded Devin? What?Walden [00:47:48]: It's like, can you believe we hand-wrote this code? And we had, our infra people who are really amazing, they were looking into it and they're like, “Oh, what? We realized that actually the root cause of this problem is actually super simple, but like fine-grain detail,” which is that a lot of these virtual machines actually underlying them don't use real file systems. They use these, network file systems where things are actually cached over the network actually in S3. So when you're Grepping, you're actually making network calls Every time you're doing these things, and that's why Grep is extremely slow on these machines. And so again, goes back to, what is all of the crazy infra work that we had to do to actually get these machines working. If you try to do this yourself, there are tons of small details like this, and so we had to eventually go swap out that network file system. ButSwyx [00:48:35]: I think there's a write-up about it, right? Silas did one about the virtual file system.Walden [00:48:38]: Oh, that was a whole other thing. TheSwyx [00:48:39]: Oh, that's a different thingWalden [00:48:40]: The BlockDev file storage formatSwyx [00:48:42]: I'll bring it upWalden [00:48:42]: Which is, a file system format that we built so that the VMs could be spun up and down very quickly. Basically, the intuition behind this is-Imagine you have, a terabyte of disk, and your agent only, wrote, a hundred lines of code on top of that disk. How long does it, say, take to, save and re-bring up that disk? And most systems, because you're not optimizing for this case, it's just, on the order of a terabyte of work because you have to Save all of that and bring it back up. In our system, we try to build a file system that incrementally builds on top of each other. So every time you save and bring the machine back up, you're only doing work that is proportional to effectively the diff in the file system. And so this, shaves off a lot of time in the boot-up process of Devin. I think we This is actually now outdated. We have a newer system inside of Devin. But yeah, there's a lot of tiny details you have to get right here to actually get the day-to-day experience of Devin to be good.Swyx [00:49:39]: It's, not technically agents, but it is agent infra, and when you sell an agent as a company, you sell agent plus agent infra.Walden [00:49:46]: At least the way we do it be And the other The nice thing about having the agent infra being done together is, you We get to deploy Devin in whatever environment we want now. We don't need to wait for some underlying infra provider to also go and support VPC or on-prem or FedGovCloud, for instance. So we can actually go and figure out, okay, since we own the infrastructure, how can we get that set up for you?Cloud Providers: Modal, Daytona, and Enterprise SandboxesSwyx [00:50:12]: Whereas you're Cloudflare dependent.Cole [00:50:15]: so Cloudflare runs the control plane. The sandboxes, Modal is supported. A contributor just added Daytona. E2B is on the roadmap, and I think there's an abstraction in place that if any contributor wants to add a new provider, they can add that in.Walden [00:50:32]: Well, what are, How are the customers you work with Do they generally try to then go set up a contract with another one of these third-party providers? Do they try to do the VMs in-house?Cole [00:50:44]: most of them I see using Modal. I think Modal has a greatWalden [00:50:48]: Shout out Modal.Swyx [00:50:48]: Shout out Modal.Cole [00:50:50]: I think Modal has a great offering. It captures all of the sandbox pieces you need, snapshots being a pretty big piece of that, and given that they also offer GPUs, I think it's a pretty nice offering as a whole.Swyx [00:51:04]: no debate there.Walden [00:51:07]: Modal is great, especially, I think their container offering is, the most natural, and so especially if you are willing to, forego, the full VM requirements Modal is, a really vast place you can spin something up on.Swyx [00:51:20]: Is there a point So Modal's very Python, and I feel like most workload, has really shifted to JavaScript. I don't know if you guys Get the same feeling. So, okay, when I started Landspace and IE and all these things, I was like 50/50 Python and JS, right? That's roughly. I think that's wrong now. I think JS has won. I don't know if you guys Like, I Maybe I'm overstating it, and maybe for cognition, there's, C# and Java and what have you. But for, new greenfield apps, do you feel that Do you get that sense? Does it matter?Cole [00:51:52]: I think that most of the libraries that I see in this space are Python native first, especially in theCole [00:51:58]: Observability space. That said, I think that there is a pretty big appeal of having your entire system in one language. Especially when you have both your frontend and backend communicating, you can have one central type Which is very nice.Swyx [00:52:11]: That's my case against Modal, which is Then you have to run JS. You can run JS inside Modal. It's just, one extra step That, isn't native to the runtime. I don't know ifWalden [00:52:22]: I don't knowSwyx [00:52:23]: Reviews. Do you have numbers? I don't know.Walden [00:52:25]: the one thing I don't like about Python is whenever AI, whenever it writes Python, it always does, the weirdest patterns, andSwyx [00:52:32]: Oh, because it's, mixing two and three or what?Walden [00:52:34]: I think it's something mixing two and three, yeah. The I don't know if you see this. It always tries to do, has attribute on objects as likeCole [00:52:41]: Oh, my God.Walden [00:52:41]: But it's like But that you shouldn't be doing that. It should error if there wasSwyx [00:52:45]: Because it's training on library code?Cole [00:52:47]: I think it's more of, likeCole [00:52:48]: From what I've seen, it's more of, a reward hacking mechanism where it doesn't want to basicallyWalden [00:52:54]: It'll never error.Cole [00:52:54]: It doesn't want the code to fail. And so it Even when it knows it has the attribute, it'll call getattr on a, and for a lot of my clients who have moved towards more autonomous coding, we've put that in as a lint rule That if you do getattr, your pull request is going to fail.Slop Signatures: Comments, Backwards Compatibility, and TypesSwyx [00:53:12]: Ooh, this is a fun topic. Can you tell me more about this? What else is a sign of AI coding that you have to put guards in?Walden [00:53:21]: So we were talking just before this about Opus 4.7. One of the things this new model likes to do is it writes lots of comments. Not like, it'll, comment every line, but it'll write, paragraph, PRDs, on top of every function. But I will say, to its credit, these aren't slop, descriptions like they were before. “Oh, here's what this function does.” It's like, “Oh, here's actually the r

See omnystudio.com/listener for privacy information.

The repo market is $16 trillion globally and most people have never heard of it — until the plumbing breaks. Craig Burchell of FalconX and Matteo Pandolfi of Pareto explain how it works and why bringing it on-chain is the next big unlock for DeFi. --- Heads up! If you haven't yet, be sure to subscribe to Bits + Bips, since the show will migrate there in a few weeks. Follow us on ⁠⁠⁠⁠⁠Apple Podcasts⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠YouTube⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠Spotify⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠X⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠Unchained⁠⁠⁠⁠⁠ and wherever you get your podcasts. ---- The repo market is $16 trillion globally and it is, as Craig Burchell puts it, the oil that makes everything go. It is also almost entirely absent from on-chain finance — and that gap is creating real problems for RWA liquidity, stablecoin swap desks, and DeFi protocols trying to manage redemption queues. Steve Ehrlich sits down with Craig Burchell, head of lending at FalconX, and Matteo Pandolfi, CEO of on-chain credit infrastructure provider Pareto, to map exactly how repo works, what broke in 2019, why it translates extremely well into onchain finance. Matteo puts a $1 trillion figure on where on-chain repo gets in five years. Craig gives you one reason it gets there and one very honest reason it might not. Host: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Steve Ehrlich, Head of Research at SharpLink and Host of Bits + Bips: The Interview - https://x.com/Steven_Ehrlich Guest: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Craig Burchell — Head of Lending, FalconX; previously Head of Lending at Membrane Finance. @_CraigBirchall ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Matteo Pandolfi — CEO & Co-Founder, Pareto (on-chain credit infrastructure). @pan_teo_ Learn more about your ad choices. Visit megaphone.fm/adchoices

The Voidcat vigil continues. There Is No Middle Anymore. Being Different is a Crime. Also REPO. Since Mia the Void Cat has warped back into the abyss from whence she came, so we are going to try to have some fun to decompress from all the BS we deal with every day. So we will play the horror comedy game, REPO. We will also be reading an article about men leaving the workforce! Women most affected!

See omnystudio.com/listener for privacy information.

Cynthia and Daniel discuss the 2026 romantic comedy People We Meet on Vacation, starring Emily Bader and Tom Blyth. Should you expect to get tons of free stuff in New Orleans just for being honeymooners? Is it still romantic to get your crush's flu virus? Why don't more movies do this good a job of justifying characters kissing in the rain? And most importantly: does this movie give endorphins? Cover art by Paul Saunders, theme song written and performed by by Ali Lipman. Support LRR: http://Patreon.com/loadingreadyrun Romantic movies give us endorphins - even when they suck. Each episode, Cynthia and Daniel (Fight the Future with Dan and Paul) talk about a romantic comedy or romantic drama, digging into both the plot and the romance, and answering questions like: What happens the day after the end of the movie? Which romantic gestures are endearing (ooo!) and which are just creepy (eww!)? Will the couple make it? And does this movie, regardless of quality, deliver the happy-making endorphins we could all use right now? Support LRR: http://patreon.com/loadingreadyrun Merch: https://store.loadingreadyrun.com Discord: https://discord.gg/lrr Twitch: https://www.twitch.tv/loadingreadyrun Check out our other channels! Video Games: http://youtube.com/LRRVG Tabletop: http://youtube.com/LRRTT Magic the Gathering: http://youtube.com/LRRMTG Comedy: http://youtube.com/LoadingReadyRun Streams: http://youtube.com/LoadingReadyLive

Repo fails spiked to more than $415 billion. Treasury bill prices are jumping. Prices. US bank dealers are using their record government bond holdings at the same time foreigners are deploying huge amounts of their reserves of the same instruments. Treasuries bonds are all over the shadows and it has nothing do with interest rates or the Fed, except the Fed is providing a lot of the data. What does it all mean? The answer -a critical part of it - can be found in Nigeria. Eurodollar University's Money & Macro Analysis----------------------------------------------------------------------------------What if your gold could actually pay you every month… in MORE gold?That's exactly what Monetary Metals does. You still own your gold, fully insured in your name, but instead of sitting idle, it earns real yield paid in physical gold. No selling. No trading. Just more gold every month.Check it out here: https://monetary-metals.com/snider----------------------------------------------------------------------------------https://www.eurodollar.universityTwitter: https://twitter.com/JeffSnider_EDU

3. Guest: Jeremy Zakis. Jeremy Zakisanalyzes recent developments in cricket, starting with English player Ollie Pope'spublic defense of his team's "internally devastated" reaction to their Ashes loss. More significantly, Zakis reports on a critical global shortage of cricket ballslinked to geopolitical instability in the Middle East. Because the essential tanning and hardening process is centralized there, supply chains from Asia have been disrupted,. This has forced English teams to ration balls, receiving only 50% of their usual quota. Zakis warns that this crisis could eventually impact the Australian season, highlighting modern manufacturing vulnerabilities,. (3)