Podcasts about modular

In this episode, Corwyn Melette shares his insights on real estate development, affordable housing, and building a legacy through strategic investments. Discover how he balances community service with business growth and the importance of systems and leadership in scaling success.   Professional Real Estate Investors - How we can help you: Investor Fuel Mastermind:  Learn more about the Investor Fuel Mastermind, including 100% deal financing, massive discounts from vendors and sponsors you're already using, our world class community of over 150 members, and SO much more here: http://www.investorfuel.com/apply   Investor Machine Marketing Partnership:  Are you looking for consistent, high quality lead generation? Investor Machine is America's #1 lead generation service professional investors. Investor Machine provides true 'white glove' support to help you build the perfect marketing plan, then we'll execute it for you…talking and working together on an ongoing basis to help you hit YOUR goals! Learn more here: http://www.investormachine.com   Coaching with Mike Hambright:  Interested in 1 on 1 coaching with Mike Hambright? Mike coaches entrepreneurs looking to level up, build coaching or service based businesses (Mike runs multiple 7 and 8 figure a year businesses), building a coaching program and more. Learn more here: https://investorfuel.com/coachingwithmike   Attend a Vacation/Mastermind Retreat with Mike Hambright: Interested in joining a "mini-mastermind" with Mike and his private clients on an upcoming "Retreat", either at locations like Cabo San Lucas, Napa, Park City ski trip, Yellowstone, or even at Mike's East Texas "Big H Ranch"? Learn more here: http://www.investorfuel.com/retreat   Property Insurance: Join the largest and most investor friendly property insurance provider in 2 minutes. Free to join, and insure all your flips and rentals within minutes! There is NO easier insurance provider on the planet (turn insurance on or off in 1 minute without talking to anyone!), and there's no 15-30% agent mark up through this platform!  Register here: https://myinvestorinsurance.com/   New Real Estate Investors - How we can work together: Investor Fuel Club (Coaching and Deal Partner Community): Looking to kickstart your real estate investing career? Join our one of a kind Coaching Community, Investor Fuel Club, where you'll get trained by some of the best real estate investors in America, and partner with them on deals! You don't need $ for deals…we'll partner with you and hold your hand along the way! Learn More here: http://www.investorfuel.com/club   —--------------------

Plus: Qualcomm to acquire AI software firm Modular in $3.9 billion stock deal. And Zoox debuts redesigned robotaxi for large-scale production. Julie Chang hosts. Learn more about your ad choices. Visit megaphone.fm/adchoices

In this reactor deep dive, Chris Keefer is joined by Navid Badie, Chief Nuclear Engineer at Candu Energy Inc, to explain the inner workings of the distinctive CANDU reactor. They trace how Canada's decision to use natural uranium led to heavy-water moderation, horizontal pressure tubes, separate coolant and moderator systems, and the ability to refuel continuously while operating. Navid breaks down the reactor's fuel channels, steam generators, online fueling machines, and the remarkable operating experience behind a technology that has completed nearly a million online refuelling operations.The conversation also examines CANDU safety and longevity: large inventories of water, natural thermosiphon cooling during a station blackout, and the engineering behind reactor refurbishment. Chris and Navid discuss pressure-tube metallurgy, robotic inspection and maintenance, cobalt-60 and other isotope production, and why locally manufacturable natural-uranium fuel can offer importing countries greater fuel-cycle sovereignty. A technically grounded introduction to one of the world's most unusual and capable reactor lineages.Listen to Decouple on:• Spotify: https://open.spotify.com/show/6PNr3ml8nEQotWWavE9kQz• Apple Podcasts: https://podcasts.apple.com/us/podcast/decouple/id1516526694?uo=4• Overcast: https://overcast.fm/itunes1516526694/decouple• Pocket Casts: https://pca.st/ehbfrn44• RSS: https://anchor.fm/s/23775178/podcast/rssWebsite: https://www.decouple.media

Bloomberg reported that Qualcomm is nearing a deal to acquire Modular, an AI software startup known for the Mojo programming language and an inference engine for cross hardware deployment. The reported move aligns with Qualcomm's push to expand on device AI on Snapdragon platforms, including PCs that meet Microsoft's Copilot Plus NPU requirements. Competitive pressure from Nvidia, Apple, Intel, and AMD is driving chipmakers to pair silicon with software to lower developer friction. Recent AI transactions such as Databricks' acquisition of MosaicML and investments in Anthropic show a broader consolidation of tools and compute. Regulators in the United States and Europe have increased scrutiny of AI deals, raising interoperability and licensing questions. Founders and IT buyers should evaluate portability, licensing, and performance baselines as potential ownership changes develop.Learn more on this news by visiting us at: https://greyjournal.net/news/ Hosted on Acast. See acast.com/privacy for more information.

OpenAI amplía Daybreak para cerrar vulnerabilidades con IA y presenta GPT-5.5-Cyber. Qualcomm se acerca a comprar Modular para competir con Nvidia también en software. Nvidia anuncia 35 superordenadores de IA en Europa, Oracle reconoce recortes ligados a la IA y una enana blanca podría explicar señales de radio repetitivas desde el espacio.Puedes seguirnos en YouTube en https://youtube.com/olivernabani y puedes unirte al Discord Mashain en https://olivernabani.com/discord

In this episode, real estate investor Erik shares his journey in land development, modular homes, and building strategic relationships to grow his business. We explore opportunities, challenges, and key insights for aspiring investors.   Professional Real Estate Investors - How we can help you: Investor Fuel Mastermind:  Learn more about the Investor Fuel Mastermind, including 100% deal financing, massive discounts from vendors and sponsors you're already using, our world class community of over 150 members, and SO much more here: http://www.investorfuel.com/apply   Investor Machine Marketing Partnership:  Are you looking for consistent, high quality lead generation? Investor Machine is America's #1 lead generation service professional investors. Investor Machine provides true 'white glove' support to help you build the perfect marketing plan, then we'll execute it for you…talking and working together on an ongoing basis to help you hit YOUR goals! Learn more here: http://www.investormachine.com   Coaching with Mike Hambright:  Interested in 1 on 1 coaching with Mike Hambright? Mike coaches entrepreneurs looking to level up, build coaching or service based businesses (Mike runs multiple 7 and 8 figure a year businesses), building a coaching program and more. Learn more here: https://investorfuel.com/coachingwithmike   Attend a Vacation/Mastermind Retreat with Mike Hambright: Interested in joining a "mini-mastermind" with Mike and his private clients on an upcoming "Retreat", either at locations like Cabo San Lucas, Napa, Park City ski trip, Yellowstone, or even at Mike's East Texas "Big H Ranch"? Learn more here: http://www.investorfuel.com/retreat   Property Insurance: Join the largest and most investor friendly property insurance provider in 2 minutes. Free to join, and insure all your flips and rentals within minutes! There is NO easier insurance provider on the planet (turn insurance on or off in 1 minute without talking to anyone!), and there's no 15-30% agent mark up through this platform!  Register here: https://myinvestorinsurance.com/   New Real Estate Investors - How we can work together: Investor Fuel Club (Coaching and Deal Partner Community): Looking to kickstart your real estate investing career? Join our one of a kind Coaching Community, Investor Fuel Club, where you'll get trained by some of the best real estate investors in America, and partner with them on deals! You don't need $ for deals…we'll partner with you and hold your hand along the way! Learn More here: http://www.investorfuel.com/club   —--------------------

Learn more at TheCityLife.org

In this episode, we sit down with the co-founder and CEO of Urban Jungle Project, a company rethinking how nature can live inside our cities, from green rooftops and living facades to forgotten urban spaces turned into climate-proof ecosystems.We talk about urban heat, biodiversity, 3D-printed jungle blocks, smart plant monitoring, and why the cities of tomorrow may need to look a lot less grey.Let's dive in.Shownotes:The Urban Jungle Project (https://www.theurbanjungleproject.com/en/) Daan Grasveld (https://www.linkedin.com/in/daangrasveld/)Sony Music Entertainment (https://www.sonymusic.com/) Picnic Supermarkets (https://jobs.picnic.app/en/about-picnic)Ebben Tree Nursery (https://www.ebben.nl/en/)Nos (https://nos.nl/)TU Delft (Delft University of Technology) (https://www.tudelft.nl/en/)Timestamps:00:11: Intro01:41: Dan's professional background03:10: Spark for the project05:43: Pivot from energy to nature07:04: Global urbanization challenges08:35: Urban Heat Island effect12:12: Benefits of green roofing14:28: The business case for nature15:48: Launching the first pilot19:45: Founder and partnership dynamics21:54: Choosing heart over head26:55: Embracing generalist leadership29:37: Advantage of organic growth37:59: Modular and lightweight tech39:57: Sensors and maintenance care42:47: Overcoming growth constraints44:47: Measuring biodiversity and impact51:21: Future company vision52:18: Closing and contact info

Preview for Later Today: Amelia Bruno discusses modular electro-spray thrusters about the size of a postage stamp. Utilizing green monopropellant and solar power, this compact technology allows small satellites, like CubeSats, to change orbits or planes efficiently. It offers an affordable propulsion solution for universities and researchers exploring space using modular, scalable components.1962

Key TakeawaysThe biggest value-add opportunity in self-storage isn't always raising rents—it's adding units. Expanding a facility can create significantly more value than operational improvements alone.Look for excess land when buying self-storage. Vacant land, truck parking, RV storage, or underutilized areas can often be converted into additional storage units.Modular storage containers allow you to expand in phases. Instead of investing heavily upfront, operators can add units as demand grows, reducing risk and vacancy.Simple site designs often outperform maximized layouts. Customer experience, ease of access, safety, and traffic flow can be more valuable than squeezing in a few extra units.Small business customers are often the best tenants. Contractors, HVAC companies, home stagers, and other service businesses tend to stay longer and expand into additional units over time.Unit mix matters. Offering a combination of different sizes can help attract a broader customer base and maximize occupancy.Appearance affects leasing. New, well-maintained units create a better customer experience and can command stronger demand than older, worn containers.Run the numbers before expanding. In Tyler's example, a relatively small capital investment in additional units had the potential to create hundreds of thousands of dollars in additional property value.Think beyond cash flow. Every dollar of NOI created through expansion can dramatically increase a property's value through cap rate compression and future refinancing opportunities.The best self-storage deals often have hidden expansion potential. What looks like excess parking, RV storage, or unused land today may become the highest-return portion of the investment tomorrow

The government has spent €1.3 billion on modular buildings for schools in the past five years. One TD told the Public Accounts Committee that these modular prefabs, were not conducive to teaching or learning, that they were "a blight on communities across this country” and should not be seen as a permanent solution to classroom space.John Boyle, the Irish National Teachers Organisation General Secretary and Eoin Dolan, Principal of Mother of Divine Grace National School in Finglas joined Ciara and Shane to discuss their function.

Stephan Bredell – CEO and co-founder, Platō Coffee SAfm Market Update - Podcasts and live stream

Woah even more games-------------------------------------------------------Follow Modular on twitter: https://twitter.com/TheModularMediaFollow Modular on Bluesky:https://bsky.app/profile/modularmedia.bsky.socialFollow Modular on Tumblr:https://www.tumblr.com/modularmediaAll Modular Media Links:https://linktr.ee/TheModularMediaHub-------------------------------------------------------------------Co-hosted by Chris Gaston: https://www.youtube.com/@BoingoRider https://bsky.app/profile/boingorider.bsky.socialhttps://twitter.com/boingo_rider https://boingo-rider.tumblr.com/https://discord.gg/H83j5PGCo-Hosted by Cody Burke:https://www.youtube.com/@snowburke83https://twitter.com/snowcone83https://snowburke.tumblr.com/https://www.instagram.com/never_robot/https://www.twitch.tv/snowcone83Co-Hosted by Buster Corp: https://www.youtube.com/@BusterCorphttps://bsky.app/profile/bustercorp.bsky.socialhttps://twitter.com/BusterBluey3https://busterscorp.tumblr.com/Co-Hosted by Simeon Scotthttps://simeonslinks.carrd.co/

We talk to Patrick Heyn, VP of Marketing for Q-SYS about what we can find at their booth at C8737 in the Central Hall. We also discuss the latest addition to their RoomSuite Modular System and providing a top-to-bottom collection of solutions for meeting spaces.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Amy Lokken shares insights on self-respect, self-confidence, and navigating heavy seasons of life, especially for women and caregivers. Amy Lokken is the founder of The Amy Factor™ andcreator of The Sophisticated Caregiver™ and designer of Müd Modular™. She serves as Private Counsel to high-performing women navigating heavy seasons, helping them live and lead in a way that makes their self-respect visible. With a background in industrial design, psychology, spatialintelligence, and decades of experience shaping environments and professional presence, Amy brings a distinct perspective to leadership, credibility, and theunseen weight many women carry while still showing up for everyone else. Her work centers on the belief that self-respect is not aluxury. It is the standard. And when a woman's standards remain intact during pressure, transition, caregiving, grief, or change, her credibility, steadiness, and leadership become unmistakable. Amy's philosophy is simple: Self-Respect Is the Standard.Credibility Is the Result. Grace Is Strength.GET IN TOUCH WITH AMY:https://theamyfactor.com/amy-factor/ https://theamyfactor.com/the-sophisticated-caregiver/LinkedIn

there may have been some game announcements or something idk-------------------------------------------------------Follow Modular on twitter: https://twitter.com/TheModularMediaFollow Modular on Bluesky:https://bsky.app/profile/modularmedia.bsky.socialFollow Modular on Tumblr:https://www.tumblr.com/modularmediaAll Modular Media Links:https://linktr.ee/TheModularMediaHub-------------------------------------------------------------------Co-hosted by Chris Gaston: https://www.youtube.com/@BoingoRider https://bsky.app/profile/boingorider.bsky.socialhttps://twitter.com/boingo_rider https://boingo-rider.tumblr.com/https://discord.gg/H83j5PGCo-Hosted by Cody Burke:https://www.youtube.com/@snowburke83https://twitter.com/snowcone83https://snowburke.tumblr.com/https://www.instagram.com/never_robot/https://www.twitch.tv/snowcone83Co-Hosted by Buster Corp: https://www.youtube.com/@BusterCorphttps://bsky.app/profile/bustercorp.bsky.socialhttps://twitter.com/BusterBluey3https://busterscorp.tumblr.com/Co-Hosted by Simeon Scotthttps://linktr.ee/simeonscott

Tony Martens, co-founder of Plantible Foods, joins Neal to walk through the company's eight-year arc - from a free greenhouse in San Marcos to a commercial-scale rubisco protein facility in West Texas. They get into the science of duckweed and why rubisco is both the most abundant and most bioavailable protein on the planet, the modular “crawl, walk, run” scaling philosophy that kept Plantible from getting buried under capex, and how landing in El Dorado, Texas lifted the surrounding county's median household income by 62%. Plus: why the Taco Stand in Encinitas remains the most-mentioned spot on the pod.Key Topics* Why our food supply chain hasn't been updated in 3,000 years* How rubisco from duckweed competes with eggs, dairy, and meat* The “crawl, walk, run” approach to commercial scale-up* Why avian flu volatility is driving bakery and egg-replacement demand* Modular agriculture vs. billion-dollar capex projects* Living on the San Marcos farm in RVs through COVID lockdown* Lifting a West Texas county's median household income by 62%* Where Plantable products are showing up on shelves todayLinks & ResourcesPlantible Foods Connect on LinkedInTony MartensNeal Bloom This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit risingtidepartners.substack.com/subscribe

On this week's episode, NK News Senior Analytic Correspondent Colin Zwirko discusses a busy week of developments in North Korea. He examines Pyongyang's latest missile test of a new modular launcher and tactical cruise missile system, as well as what these weapons could mean for military planning near the inter-Korean border. He also talks about satellite imagery suggesting North Korea's Choe Hyon-class destroyer may be undergoing final testing near Nampho ahead of possible deployment. The episode also looks at signs Pyongyang may be preparing to welcome a foreign leader visit amid reports of a possible Xi Jinping trip, and at how North Korea's first large-scale solar farm aims to address energy shortages. About the podcast: The NK News Podcast is a weekly podcast hosted by Alannah Hill exclusively for NK News, covering the latest developments in and around North Korea. Each episode breaks down the week's news cycle with NK News journalists, analysts and expert guests.

Zoning codes run to 3,000 pages, contradict themselves, and change without warning — and right now, they're the single biggest reason most housing projects never leave a napkin.Recorded live at World of Modular 2026, this episode brings in Avi Kaufman, co-founder and Chief Real Estate Officer of FutureLot, to unpack what it actually takes to answer "what can I build here?" across 30,000 US jurisdictions. Avi started with a light-bulb moment during refugee resettlement — a carriage house behind a main house, housing a family no one knew could be housed there — and built a platform to make that question answerable at scale. **What we get into:** - The pre-feasibility gap: more housing projects die from discouragement than from bad economics — nobody's counting the permits never filed - Massachusetts alone has 200+ definitions of "gross floor area." Multiply that across 30,000 jurisdictions and you understand why builders stall - FutureLot's traffic-light system (green/yellow) tells builders whether a project clears each zoning criterion before a dollar goes to plans - Why the homeowner-builder conversation is broken — and how a shared interface changes "let me drive by" into a real-time answer at any US address - The tension between local zoning control and the tyranny of whoever has time to show up to meetings - What a customer who lives in the tool 4–5 hours a day looks like — and why that feedback loop is the product **Chapters:** - 00:00 — Intro: What FutureLot does - 00:50 — Origin story: Afghanistan, carriage houses, and untapped housing potential - 02:01 — Why zoning data, not building? - 03:35 — What real estate taught Avi: visuals and ease of use aren't nice-to-haves - 04:30 — Product walkthrough: the builder experience - 07:14 — The homeowner interface and what 8 minutes of dwell time means - 09:10 — Connector, not replacement: the role of FutureLot in the stack - 10:38 — 30,000 jurisdictions and the data complexity behind one screen - 12:11 — Two years in: the regulatory maze is worse than you think - 14:00 — Should we standardize zoning? The tension between local control and paralysis - 15:19 — AI + human review: how the sauce gets made - 16:28 — Trust mechanisms: overrides, alarms, source citations - 18:42 — The customer as collaborator: ground truth flows both ways - 20:30 — Roadmap: 50-state coverage, multifamily, lot splits - 21:07 — The inflection point: why now feels different- 22:18 — Find FutureLot **Find FutureLot:** - [futurelot.com](https://futurelot.com) — free account, 3 property searches - [avi@futurelot.com](mailto:avi@futurelot.com) - [YouTube](https://www.youtube.com/@FutureLot) - [Instagram](https://www.instagram.com/tryfuturelot) - [LinkedIn](https://www.linkedin.com/company/futurelot) - [X / Twitter](https://x.com/futurelot) - [Facebook](https://www.facebook.com/futurelot/) **Most Podern:** - [Spotify](https://open.spotify.com/show/3zYvX2lRZOpHcZW41WGVrp) - [Apple Podcasts](https://podcasts.apple.com/us/podcast/most-podern-podcast/id1725756164) - [Instagram](https://www.instagram.com/most.podern) - [YouTube](https://www.youtube.com/@MostPodern)

Analysts Don Kellogg and Roger Entner unveil insights from Fiber Connect 2026 on data centers and material shortages, and discuss AT&T's new Build-A-Plan rollout as well as their legal fight to sunset legacy copper networks in California. 00:00 Episode intro 00:25 Fiber Connect data center insights 02:51 AI video is driving network requirements 04:41 AT&T's new Build-A-Plan rollout and implications 07:40 Will the plan expand in the future? 08:27 AT&T sues California to sunset copper and DSL 11:00 Satellite has become a reliable backup 12:28 Regulators should embrace the future 13:16 Episode wrap-upTags: telecom, telecommunications, wireless, prepaid, postpaid, cellular phone, Don Kellogg, Roger Entner, Fiber Connect, AI, network, data centers, BEAD, fiber, data, video, DOCSIS 4.0, AT&T, Build-A-Plan, Mint, multi-line, convergence, DSL, California, copper, FCC, satellite, Starlink, T-Mobile, regulation

The big beasts arise as we talk EVE Frontier, MapleStory Universe and how Wemade's approach bests Ubisoft. [00:34] Jon attended EVE Fanfest 2026 in Iceland. What are his takeaways?[02:40] Why EVE Fanfest works beyond being just an event for players.[05:05] EVE Frontier is EVE Online if made from scratch now.[06:46] In Cycle 6 (out 25th June), EVE Frontier finally becomes more of an actual survival game.[09:28] Modular shipbuilding replaces fixed ships.[10:40] EVE Frontier is a game that rewards players who improve their manual gameplay skills. [11:55] “This is a game that makes EVE Online feel cuddly.”[13:58] Does EVE Frontier need non-EVE players?[15:30] The fundamental approach is blockchain as a unified API.[16:38] Why some CCP/Fenris developers want to work on EVE Frontier, not EVE Online. [17:38] How EVE Frontier is using AI for coding and prototyping.[19:10] Nexon is talking about MapleStory Universe, MSU 2.0 and VIBE IP.[22:11] MapleStory Universe did $31 million in revenue in year 1. [23:22] The real KPI for MSU 2.0 is the revenue third-party devs make. [25:55] Average EVE Fanfest attendee had played 7,900 hours of EVE Online. [30:50] Legend of Ymir has released the ability to mint and trade character NFTs.[32:00] Legend of Ymir NFT character trading was $77,000 on day 1. [34:40] Ubisoft is shutting down Champions Tactics' web3 features on 27th May. [36:00] Ubisoft's blockchain problems are a minor part of much wider issues for the company. [39:00] Champions Tactics was beautifully made, but too narrow in its addressable audience. [42:29] Wemade is iteratively learning. Ubisoft is scattergun, lacking learning loops. [44:30] The post-crash shape of blockchain gaming is now becoming apparent.

The newspaper comic strip didn't go extinct — it evolved. But if your work doesn't keep up, your career may be fossilized! From Reddit-ready square comics to vertical-scroll storytelling, they explore how creators are adapting to phones, social media, and changing reading habits while keeping the heart of the comic strip alive. Topics covered The evolution of newspaper comic strips Why horizontal strips existed in the first place How phones changed comics formatting Square-format comics on Reddit and social media Vertical-scroll storytelling Why readers won't rotate their phones Charles Schulz and the flexible-format origins of Peanuts Newspaper syndication vs. modern web distribution YA graphic novels as the next evolution for newspaper strips Lincoln Peirce and the success of Big Nate books Why comic strips are still thriving online Modular comic formatting for webcomics The launch of The Comic Scout  Dave Kellett's Hugo Award nomination anticipation Tips for maintaining visual consistency in comics Workflow advice for newer cartoonists   You get great rewards when you join the ComicLab Community on Patreon$2 — Early access to episodes$5 — Submit a question for possible use on the show AND get the exclusive ProTips podcast. Plus $2-tier rewards.If you'd like a one-on-one consultation about your comic, book it now!Brad Guigar is the creator of Evil Inc and the author of The Webcomics Handbook. He is available for personal consultations. Dave Kellett is the creator of Sheldon and Drive. He is the co-director of the comics documentary, Stripped.

In ep 174 of “How Do You Say That?!” sponsored by britishvoiceover.co.uk, Toby Ricketts joins Sam and Mark in a special as-live episode from the One Voice Conference 2026 in Stratford upon Avon. We talk about commmercial scripts that seem a bit abstract, and do a four handed script that plunges us into a sci-fi crisis! There's a studio/hotel bedroom audience of voice actors, and it's all on video too - so make sure you check our YouTube channel to see us in action - https://www.youtube.com/@howdoyousaythatThe wildcards are chosen by our audience - and there's real peril from ten thousand feet, a real-estate nightmare, and an unusual bird sighting!Our question this week comes from Ben Wake in the audience, asking about accents you wear like a glove.Get involved! Have you got a Wildcard suggestion that we should try or an idea for the show? Send it to us via Mark or Sam's social media or email it directly to podcast@britishvoiceover.co.ukScript 1Hey. The Earth moves. We respond.Macro to micro. Systems rebuild, forms transform.The world's being reshaped. Constantly.Make sustainability real.Fifty years. One mission:Turn imagination into reality.Where science meets craftsmanship—Endless R&D. Relentless breakthroughs.From chemical to physical. From supplier to partner.We don't follow. We lead trends.Physical foaming with jet-speed expansion. Efficient and integrated.Elevating material performance.More elastic and controllable.Stable and comfortable.Strong and recyclable.All-in-one machine.Redefining next-gen manufacturing.Modular, customizable, scalable.Our platform. Your creativity.Across industries and possibilities.We co-create solutions.This moment. React.We shape change.We drive transformation.WE LEAD NEXTWE ARE KINGSTEELScript 2NARRATOR INTRODUCTION:The year is 2367, and chaos reigns. The Earth - dying from climate collapse - is lost forever. Humanity has spread to the stars. Scout ships with minimal crews are sent into the cosmos to seek out viable worlds. The rest of humankind sleeps in cryogenic stasis aboard vast colony ships that will require decades, even centuries, to reach their new homes.This is the beginning of The Scattering. The Great Human Exodus.STRICKLAND [yelling]Stick's dead, I've lost all control, we're coming in way too hot. Kordek, what have you got back there?KORDEK [yelling, clearly frustrated]I don't know, Strickland, the engine's going critical, safeties failing. It's as if the entire system just crashed.COMPUTERWARNING…WARNING…KORDEK [yelling, panic setting in]Drive failsafes collapsing, containment overrides down, we've got an intermix chamber bleed and no way to reroute.BONAR [yelling, sarcastic]ENGLISH!KORDEK [yelling]We're about three minutes from becoming a small sun!BONAR [yelling]Yeah - well, I've got some news on that three-minute deadline! We're going to crash in one!STRICKLAND [yelling]Get to the lifepods! Now. Move, move! Abandon ship. Go!COMPUTER VOICELaunching Lifepod. Launching Lifepod.STRICKLANDMy God, I didn't honestly expect that to work. I can't believe we're alive.KORDEKThose life pods are re-enforced titanium alloy, and the inertia gel is rated for hypersonic impacts…..BONARYeah. No one cares, Kordek. We're alive, that's what matters.We'd love your feedback - and if you listen on Apple Podcasts or Spotify, hit the follow button today!**Listen to all of our podcasts here - you can also watch on YouTube, or say to your smart speaker "Play How Do You Say That?!"About our guest: Toby Ricketts is a multi-award-winning voiceover artist specialising in British, Australian, New Zealand, American and Global international non-regional or mid-Atlantic voice overs. Woof! In the last 25 years of his career, Toby has managed to create a global client base of big-name brands and loyal customers - and pretty much all from his secluded hi-tech studio deep in the New Zealand jungle.Just a few of his impressive clients include Facebook, VISA, Samsung, BMW, Audi, Lexus, Airbus, Lenovo and Google. As well as lecturing on Voiceover topics at international conferences (this one included), Toby has been nominated for 5 SOVAS awards, and has won 7 One Voice Awards, including Male Voiceover of the Year twice in 2018 and 2019, and a GEMA Award in 2025.Toby's websiteToby on FacebookToby on InstaToby's YouTube channelResources: Click here for the Wildcard Generator and don't forget to think of an action your character can be doing!About your hosts:With over 40 years representing major international clients such as Google, Emirates and HSBC; Mark Ryes has been trusted to be the voice for some of the world's biggest brands. If your business needs a fresh voice to represent you, then make it Mark's British voice. As a voiceover, TV presenter, podcaster or product demonstrator - Mark makes your brand truly sparkle!Mark's demos & contact details: https://linktr.ee/britishvoiceovermarkElegantly British with an intelligent, warm and seductive voice, Samantha Boffin helps creatives and production companies create great audio that really connects with their audience. BBC-trained and with over 20 years of broadcast experience on both sides of the mic, she's created award-winning promos, narration and commercials for companies all around the globe, including the BBC, Sky, Games Workshop, John Lewis, Audible and Penguin Random House.Samantha's demos & contact details: https://linktr.ee/samanthaboffinMany thanks to our studio audience... especially Kate De Quidt, Karen Esposito and Ben Wake.

Send us Fan MailPermitting can turn “faster with modular” into “stuck in review” long before the first module leaves the plant. Sam Taylor, founder of Crosscheck Modular Consulting in Ontario, explains what actually slows modular projects down and what teams can do differently on their next build. If you've ever wondered why approvals feel unpredictable from one town to the next, this conversation puts real structure around the problem. Sam walks through the modular approvals process in Ontario, where building permits are submitted to local authorities having jurisdiction and shaped by local bylaws as much as code. She explains why early engagement with building officials matters so much, especially in smaller communities that may not see modular often, and how proactive communication can reduce redesigns, clarify inspections, and keep projects moving. Additionally, she also compares province-to-province realities, from Alberta's deeper familiarity with modular to BC's Step Code energy efficiency requirements.Support the showListen to all episodes of MBI's Inside Modular podcast at https://www.modular.org/inside-modular-the-podcast-of-commercial-modular-construction/

An airhacks.fm conversation with Ian Rogers (@Ian Rogers) about: ZX Spectrum 128K with rubber keys and a burning side grill, Basic programming competitions, REM commands as ASCII art, PC versus Amiga and Archimedes era in the UK, fractal landscape generators for Wing Commander 4 cut scenes, Ocean Software in Manchester and the Head Over Heels game, Manchester Baby and Williams tube as the first stored-program computer, Steve Furber and ARM origins at the University of Manchester, Cosworth and Pi Research Formula One telemetry, transputers and embedded PowerPC data loggers, dynamic binary translation with the Dynamite simulator, ICL 2900 emulation for the Israeli tax system, MIPS to Itanium binary translation for SGI machines, Transitive Corporation and the PowerPC to x86 product that became Apple Rosetta, the Steve Jobs era at Apple, Spark to Power binary translation and the IBM acquisition of Transitive, JDBC versus ODBC API design observations, java.util.Vector and java.util.Hashtable synchronization decisions, StringBuilder array copying overhead from removing synchronization, DARPA HPCS languages Fortress, Chapel, X10, just-in-time parallelization from Java bytecode, LCC compiler from Princeton and the iBerg backend, JikesRVM as a metacircular Java VM written in Java, GNU Classpath and Sable VM by Etienne Gagnon, Apache Harmony port of JikesRVM to Windows, Maxwell and Maxine VMS as GraalVM precursors, Bernd Mathiske and the Sun acquisition by Oracle, GNU Classpath impact of the openJDK GPL release at FOSDEM 2006, Mark Wielaard and Rémi Forax FOSDEM stories, trace compilation and de-optimization parallels with JIT, Azul Systems Vega hardware and concurrent garbage collection, C4 collector design influencing ZGC and Shenandoah, Gil Tene's telephone exchange mentality for JVM responsiveness, page unmapping and signal handler memory pressure problems in HotSpot, Cliff Click and Modular, Google Android Runtime (ART) replacing Dalvik, transactional memory for class initializers in ART, ELF files and OAT format for ahead-of-time compilation, WhatsApp bytecode obfuscation breaking the ART verifier, lock balance verification for speculative lock optimizations, D8 and R8 Android compilers, Goit internal Google bytecode optimizer, Jeremy Manson and Google's OpenJDK variant, Linux kernel performance work and perf tooling, JikesRVM stack trace format making exception-heavy DaCapo benchmarks faster than HotSpot, Energy Efficiency across Programming Languages study comparing Java and Go, Ian Rogers on twitter: @Ian Rogers

Episode 83: Thinking about a panelized kit home but not quite sure what you actually get, how it's delivered, or how it differs from modular and prefab? This episode walks through the practical basics. Steve explains typical delivery timelines (about 4–5 weeks after permits and plans are done), how Landmark can stage multiple deliveries for tight sites, rural locations, and even islands, and what's included on the truck: the complete wood structure—sill plates, floor system, sheathed wall panels with framed openings, roof trusses, roof sheathing, sub fascia, and connectors—ready for your local crew to assemble. He contrasts that with what you don't get (roofing, windows, mechanicals, finishes) and why Landmark's biggest value isn't just lumber, but the full design stack behind it: architectural plans, structural engineering, energy calcs, and site specific layouts that align with zoning, setbacks, and permit requirements. You'll also hear how “standard” floor plans are just starting points that Landmark can fully customize—even down to unusual details like floor to ceiling closet doors—and how panelized construction fundamentally differs from modular and HUD code prefab, while still giving owner builders control over their project, budget, and labor.

Yes folks, it's that time again! We have a talk back!! Also, we have a very special surprise guest that I don't think ANY of you will see coming!!!! Please be sure to listen to the whole thing as we dig in to this past season of Modular!!

My guests are two voices from the brine world. Murray Brooker and Clint Van Marrewijk. Topics:Why do brine projects take so long?WA's hard rock advantagesWill brine development be faster in this cycleThe impact of big balance sheetsWhat makes a great brine project?Brine recovery ratesThe "promise" of DLENo DLE, no Smackover"Brine without borders"Modular brine productionThe brine talent poolRapid fire

Why Your Amazon Dashboard Is Lying to You + Remotion & Voice Cloning Reality Check | Claude Sessions Amazon Dashboard Brain, Remotion Video & ElevenLabs Voice Cloning | Claude Sessions SEO Description Shubhash Sharma on building a data brain behind your Amazon dashboard. Danny McMillan on Remotion video and ElevenLabs voice cloning realities. Episode Summary Week 3 of the month means Claude Sessions, and Danny McMillan and Shubhash Sharma are back with a double feature for Amazon and TikTok Shop sellers building their own AI tooling. Shubhash picks up from last episode's SP API and Ads API walkthrough with a hard lesson learned the wrong way: a polished dashboard wired straight into Amazon is a window with no room behind it. The numbers will lie, and you will not know when a feed silently dies. He walks through the fix: a "brain" sitting between the data sources and the dashboard. Supabase as the long term store, pgvector for unstructured stuff like contracts and reviews, n8n as the orchestration layer. Six core domains every seller shares (orders, products, analytics, ads, finance, affiliates and creators) plus an optional documents layer. He closes with a dual write migration pattern so you can flip between old and new without taking the business offline. Then Danny turns to video and voice. Remotion looks like toy town out of the box, but with the right plugins (motion blur, transitions, captions, shapes, fonts, rendering) and Claude doing the orchestration, it becomes a serious production tool that can pull in your footage, branding and design system. On the voice side, he has tested VoiceBox and F5TTS and come back to ElevenLabs Multilingual v2 at £22 a month. The missing gap everywhere is cadence. He also names the deeper bet: as the market floods with AI generated content, authentic voice becomes the differentiator that cannot be cloned. Key Topics Why dashboards lie when wired straight into Amazon, TikTok and Shopify The "brain" pattern: Supabase, pgvector and n8n as a centralised data layer The six core data domains every seller needs (plus a 7th for documents) Dual write migration so the old system and brain run in parallel Remotion as a code based video tool, and what it needs to stop looking toy town The four layer creative workflow: brief, story skeleton, treatment, scene by scene ElevenLabs vs VoiceBox vs F5TTS for voice cloning your own voice Why cadence is the last hard problem in synthetic voice The authenticity premium in an AI flooded market Timestamps [00:00] Intro and welcome back to Claude Sessions [00:34] Shubhash kicks off: where to put the data you pulled last week [01:04] "Your dashboard is lying to you" and the polished dashboard pitfall [02:32] Dashboard is a window. The brain is the room behind it [04:54] Tech stack: Supabase (Postgres), pgvector, n8n [05:54] The six fundamental data domains [06:26] Orders, products, analytics, ads, finance, affiliates and creators [08:30] The optional 7th layer: unstructured documents via pgvector [09:44] Dual write pattern for safe migration [10:48] Three takeaways: audit, list domains, build one table at a time [12:28] Danny on Remotion: code based video and why it is toy town out of the box [13:51] What is missing: motion blur, transitions, captions, shapes, beat detection [14:54] The 80+ plugin packages that turn it into a real tool [16:56] Pulling in footage, logos, design systems and free music from Pixabay [18:30] The 4 layer creative workflow: brief, story skeleton, treatment, scenes [21:15] Voiceovers: ElevenLabs Pro setup and why the £22 is worth it [22:12] VoiceBox and F5TTS field test: garbage and 5 rounds of tuning later [23:22] Why cadence is the hardest thing for AI voice to fake [25:42] How much reference audio you actually need (30 min min, 2 hours ideal) [27:25] ElevenLabs UI parameters: speed, stability, similarity, exaggeration [28:52] The authenticity premium when the market floods with AI [30:30] Key takeaways, ElevenLabs API usage and locking in your voice once [34:24] Aside: "insane" and "most" as the new AI tells [36:31] SSL 2026 wrap, 18 days out, Ritu returns next week with Japan Key Takeaways Build a brain, not just a window. A dashboard wired straight to Amazon, TikTok or Shopify has no memory. When a feed silently fails, the dashboard happily lies. Sit a Supabase + pgvector + n8n layer in between, and your dashboard becomes a view on top of a real source of truth. Six domains cover almost every seller. Orders, products, analytics, ads, finance, and affiliates / creators. Map every place each one currently lives, then consolidate one domain at a time. Start with one table (orders) and let Claude do the heavy lifting. Use dual write when migrating. Write to the old store and the new brain in parallel for a week. Compare. Flip the dashboard's read side via a feature flag. If something breaks, flip back. Zero downtime, zero fear. Remotion is a system, not a tool. Out of the box it is bare. Add the plugins (motion blur, transitions, captions, fonts, rendering), bring your own footage and design system, and let Claude orchestrate the four layer workflow: brief, story skeleton, treatment, scene by scene. ElevenLabs Multilingual v2 still wins for voice cloning. VoiceBox and F5TTS were not close. Pay the £22, use Model 2, feed it 30 minutes minimum (2 hours ideal) of clean reference audio, and lock the setup in once. Cadence is the last mile. AI can match tone and timbre. It still cannot match the rises, falls and micro pauses that make a sentence sound like you. Use scripts split into short paragraphs, generate three variants, and tune the language you use to talk to Claude until the cadence lands. Authenticity becomes the moat. As written, visual and audio AI floods every channel, the brand voice that is unmistakably human becomes the differentiator. Do not give that away to save 22 dollars a month on a podcast. Notable Quotes "Dashboard is a window. We need a room behind the window. So the brain is going to be the room behind this window." Shubhash Sharma "If any of our SaaS went offline tomorrow, will our business still have its memory? The answer is no, because we haven't stored it. All we have is rented attention." Shubhash Sharma "When you migrate to your brain, don't rip out your old system. Use dual write. Run them in parallel for a week. If something breaks, flip it back. Zero downtime, zero fear." Shubhash Sharma "Remotion out of the box isn't great. It's almost like building some slides, just one step up. You have to build it as a system of what you need." Danny McMillan "The hardest part for AI to represent is cadence. It can get the tone of your voice. That's the easy bit. But the speed and the up and down of how you talk, that's where these models still fail." Danny McMillan "In our rush to use AI, you've got to remember the market floods with it. When everything sounds like AI, the only thing left is the authentic voice for your brand." Danny McMillan Resources Mentioned Supabase : Postgres backend used as the long term data store for the seller "brain" pgvector : Postgres extension for semantic search over unstructured data (contracts, reviews, supplier emails) n8n : Orchestration layer for scheduled pulls and cron jobs with a UI Amazon Selling Partner API (SP API) : Source for orders, inventory and finance data (covered in last episode) Amazon Ads API : Source for ad spend, campaign and keyword data Remotion : Code based, React powered video creation framework ElevenLabs : Voice cloning and text to speech. Model used: Multilingual v2 (Pro plan, £22 / month) F5 TTS : Open source text to speech model tested for voice cloning VoiceBox by Jamie Pine : GitHub voice cloning desktop app tested by Danny Pixabay : Free music and sound effects used inside the Remotion workflow Loom : Source of clean voice reference audio if you record team walkthroughs Seller Sessions Live 2026 : Conference 9 May 2026, 18 days out at recording Hosts Danny McMillan : Host of Seller Sessions and Claude Sessions, founder of DataBrill, building AI native tooling for Amazon sellers. Website: https://sellersessions.com LinkedIn: https://www.linkedin.com/in/dannymcmillan Shubhash Sharma : Engineer building data infrastructure for Amazon and TikTok Shop sellers. Returning Claude Sessions co host. What's Next Next week: Ritu returns from Japan with three subjects covered in this month's rotation. In 18 days: Seller Sessions Live 2026 in London on 9 May. Modular format, new venue confirmed. About Seller Sessions Seller Sessions is the leading podcast for serious Amazon sellers, hosted by Danny McMillan since 2017. Claude Sessions is the AI focused monthly strand where Danny and rotating co hosts work through the practical wins, false starts and engineering reality of building with Claude, MCPs and the wider AI stack inside real seller businesses.

This week Shawn Tierney meets up with Chuck Ridgeway of Horner Automation to learn about their new Modular PLCs in this episode of #TheAutomationPodcast. For any links related to this episode, check out the “Show Notes” located below the video. Watch The Automation Podcast from The Automation Blog: Listen to The Automation Podcast from The Automation Blog: The Automation Podcast, Episode 269 Show Notes: Special thanks to Chuck Ridgeway of Horner Automation for coming on the show, and to Horner Automation for sponsoring this episode. To learn more about these products, please see the below links: Horner Automation’s YouTube Channel Horner Automation’s LinkedIn Horner Automation’s Modular Controllers Horner Automation’s OCS360 Cloud Service Horner Automation’s Academic Program Until next time, Peace ✌️ If you enjoyed this content, please give it a Like, and consider Sharing a link to it as that is the best way for us to grow our audience, which in turn allows us to produce more content

"You don't have to start at the top—gear up with purpose, innovate, and don't let price keep you out of the game." Episode Summary: In this episode of The Gun Experiment, I sit down with Big Keith and our special guest, Rob Godek, the Director of AceTac Gear. We dive deep into the origins of AceTac, from its humble roots in a garage to becoming a respected name in modular and adaptable tactical gear. Rob opens up about the importance of balancing affordability, reliability, and innovation for everyday Americans and professionals alike. We also share stories, review some killer gear (like the low-profile plate carrier and skeleton placard), and unpack the realities of starting and growing a gear company in today's competitive landscape. Expect laughs, honest feedback, and plenty of behind-the-scenes wisdom for both new shooters and seasoned operators. Call to Action: 1. Join our mailing list: Thegunexperiment.com 2. Subscribe and leave us a comment on Apple or Spotify 3. Follow us on all of our social media: Instagram   Youtube 4. Grab some cool TGE merch 5. Ask us anything at AskMikeandKeith@gmail.com 6. Be sure to support the sponsors of the show. They're a big part of making the show possible. Show Sponsors: HSM Ammunition: Official ammo sponsor, tested and recommended by us for reliability and performance. Onsite Firearms Training (OFT): Our go-to for responsible gun ownership and hands-on, real-world defensive training. New York Tac Defense: Offering prepaid legal plans for self-defense—peace of mind when you need it most. Key Takeaways: AceTac Gear is about making purpose-driven, affordable tactical equipment without sacrificing function or quality. Rob Godek's journey illustrates the power of persistence, honest customer feedback, and staying true to the roots—especially supporting everyday Americans and first responders. Not every innovation means reinventing the wheel; often, it means listening to users and perfecting what works. The firearms and tactical gear community thrives on transparency, supporting new shooters, and embracing the “climb” rather than just chasing high-end gear. Modularity, affordability, and durability are at the heart of great EDC and tactical gear. The customer experience at AceTac goes beyond just sales—offering a genuine lifetime warranty and community engagement. Balance your gear needs with honest self-assessment; sometimes a good “middle ground” product outperforms luxury when it comes to real-world use. Guest Information: Rob Godek is the Director and CEO of AceTac Gear. With a background in law enforcement, NASCAR engine building, and a passion for hands-on innovation, Rob brings a no-nonsense, customer-focused approach to tactical gear. AceTac is dedicated to empowering users with modular, reliable kits—ensuring “Gucci” quality is accessible to all, not just the elite. Find AceTac at AceTacGear.com and on Instagram for the latest updates. SEO Keywords: AceTac Gear, Rob Godek, The Gun Experiment, tactical gear review, modular tactical gear, affordable plate carrier, law enforcement equipment, EDC gear, gear innovation, customer feedback tactical, veteran owned gear brand, lifetime warranty tactical, SHOT Show, HSM Ammunition, Onsite Firearms Training, New York Tac Defense, 2A community, plate carrier review, skeleton placard, cummerbund review, Gun Podcast, gear for everyday Americans, product development tactical gear, training for gun owners

Looking for daily inspiration?  Get a quote from the top leaders in the industry in your inbox every morning.   Mike Whincup is the Head of Design and Marketing at Galaxy Multi Rides. Growing up in a family business that pioneered mechanical bull innovation, Mike has worked across both manufacturing and operations, helping expand the company globally while also launching Do The Beach, an inflatable park franchise concept. His experience spans decades in the attractions industry, blending creativity, entrepreneurship, and operational insight. In this interview, Mike talks about modular attractions, profitability through efficiency, and trends in inflataparks. Modular attractions “If you can think it, we've probably made it, as long as we can make it safe.” Mike explains how Galaxy Multi Rides evolved from a single mechanical bull into a fully modular attraction system with interchangeable ride attachments. What began as a practical solution to improve setup efficiency turned into a versatile product line that allows operators to swap themes and experiences easily. From surfboards to sharks to branded activations, the modular concept enables venues to refresh offerings without major capital investment. This adaptability also makes the attractions appealing across multiple markets, from party rentals to permanent installations. The ability to customize and iterate has attracted major brands and entertainment venues, reinforcing the value of flexibility in attraction design. Profitability through efficiency “We're trying to create profitability through efficiency.” A central theme in Mike's philosophy is designing attractions and facilities that maximize revenue while minimizing operational strain. He highlights how inflatable parks can achieve up to 90 percent playable space compared to around 60 percent in trampoline parks, immediately increasing capacity and revenue potential within the same footprint. Efficiency also extends to staffing and layout. By designing attractions that require less supervision and optimizing facility flow, operators can reduce labor costs while maintaining safety and guest experience. This balance between design, operations, and guest flow is what drives sustainable profitability. Trends in inflataparks “It's the evolution of the concept.” Mike describes the current inflatable park movement not as a new trend, but as an evolution. Earlier versions were disconnected attractions placed side by side, while modern inflataparks are fully integrated environments where guests remain engaged continuously. This shift toward immersive, interconnected design improves safety, increases engagement, and enhances overall guest satisfaction. The model also benefits from lower build costs and greater adaptability, making it attractive for operators entering the market. As a result, inflataparks are gaining renewed momentum as a scalable and efficient alternative within the family entertainment center space.   Mike can be reached on LinkedIn. To learn more about Galaxy Multi Rides, visit www.galaxymultirides.com. To learn more about Do The Beach, visit www.dothebeach.com. This podcast wouldn't be possible without the incredible work of our faaaaaantastic team:   Scheduling and correspondence by Kristen Karaliunas   To connect with AttractionPros: AttractionPros.com AttractionPros@gmail.com AttractionPros on Facebook AttractionPros on LinkedIn AttractionPros on Instagram AttractionPros on Twitter (X)

The Government's decision to allow modular housing units in people's back gardens might seem like a good idea on the face of it, but will it lead to a bigger mess than we are already in?Joining Seán to discuss is Lorcan Sirr, Senior Lecturer in Housing at TU Dublin…

Estate Agent Johanna Murphy has been looking hard at the scheme and she points out to PJ that there's a lot of good in it as part of an overall solution to the housing crisis Hosted on Acast. See acast.com/privacy for more information.

PJ talks to JP from Big Man Tiny Homes and he says that the debate over homes in back gardens has opened peoples eyes to what a modern modular is like Hosted on Acast. See acast.com/privacy for more information.

And at Google Next, Google splits its TPUs and unleashes more powerful workplace agents. Plus, did Anthropic's Mythos escape containment?Starring Tom Merritt, Sarah Lane and Andy Beach.Links to stories discussed in this episode can be found here. Hosted on Acast. See acast.com/privacy for more information.

Anne-Marie O'Reilly, National Advocacy Manager with Threshold, on their call on Government to halt proposed planning exemptions for modular garden homes.

Speaking about the new economic forecast and the proposed exemptions for modular homes, John Cummins, Minister of State at the Department of Housing for Local Government and Planning.

Send us Fan MailFinancing can kill a great modular project long before the first module is built. That's exactly where AI is starting to change the game. Jim Park, founder of Park Place Lending, talks about how AI is impacting financing for commercial modular construction, and the real-world bottlenecks that keep good ideas from turning into funded projects.Jim digs into how AI helps with early feasibility: faster budgets, tighter schedules, cleaner pro formas, and clearer comparisons between modular vs conventional construction. Jim shares how developers can use data to identify true demand pockets, even down to ZIP codes, and why the “obvious” markets are not always the best markets. We also talk about the bigger shift most builders miss: you don't just need a better build method, you need a scalable system that connects marketing, qualification, financing, and delivery.Support the showListen to all episodes of MBI's Inside Modular podcast at https://www.modular.org/inside-modular-the-podcast-of-commercial-modular-construction/

Miniloong Pocket 1 specs: Rockchip RK3566, 1GB DDR3 RAM, 960x720 4:3 4 inch screen, Onboard 8GB storage, has LoongOS, WiFi + BT 4.2, Battery: 4000 mAh, Hall sensor sticks, Transparent buttons, Modular d-pad  

Shepard Fairey is one of the most famous artists in the world, and if you think about it, there aren't many artists who are famous in their lifetimes. In times' past, artists didn't get to live with their fame, their notoriety, the praise and scrutiny that comes with making art seen by man. We are living in a different era, art has sometimes permeated into popular culture and consciousness, and Fairey's' Obey Giant and Obama imagery are the rare instances where art becomes mega Pop Art, the kind found on tee shirts and on refrigerator magnets. Fairey is a street artist, fine artist, designer, clothing brand owner, DJ, printmaker, father, husband and revered muralist. He makes art in the moment for a number of social justice causes, and creates studio work that is meticulous and bold and innovative. As we say in the introduction to Episode 02 of Unibrow Radio, for over 35 years, Fairey has been actively pursuing a balance between image and message, creating and exploring the symbiosis of how to make works where politics, music, poster design, skate culture can all exist in a single work. What he is often asking, is how an image can, in itself, be an active work of the past, present and future.Recorded live at Fairey's gallery, Subliminal Projects, during the run of his new show, MODULAR FREQUENCY, the artist talks about how he uses his own history in his work, the constant battle between reactive work and experimentation, finding ways to rest, and the many layers of influences that he's drawn on to help develop his aesthetic. He constantly mentions he stands on the shoulders of those who came before him, and he hopes he has blazed a path for others to stand on his… 

We're proud to release this ahead of Ryan's keynote at AIE Europe. Hit the bell, get notified when it is live! Attendees: come prepped for Ryan's AMA with Vibhu after.Move over, context engineering. Now it's time for Harness engineering and the age of the token billionaires.Ryan Lopopolo of OpenAI is leading that charge, recently publishing a lengthy essay on Harness Eng that has become the talk of the town:In it, Ryan peeled back the curtains on how the recently announced OpenAI Frontier team have become OpenAI's top Codex users, running a >1m LOC codebase with 0 human written code and, crucially for the Dark Factory fans, no human REVIEWED code before merge. Ryan is admirably evangelical about this, calling it borderline “negligent” if you aren't using >1B tokens a day (roughly $2-3k/day in token spend based on market rates and caching assumptions):Over the past five months, they ran an extreme experiment: building and shipping an internal beta product with zero manually written code. Through the experiment, they adopted a different model of engineering work: when the agent failed, instead of prompting it better or to “try harder,” the team would look at “what capability, context, or structure is missing?”The result was Symphony, “a ghost library” and reference Elixir implementation (by Alex Kotliarskyi) that sets up a massive system of Codex agents all extensively prompted with the specificity of a proper PRD spec, but without full implementation:The future starts taking shape as one where coding agents stop being copilots and start becoming real teammates anyone can use and Codex is doubling down on that mission with their Superbowl messaging of “you can just build things”.Across Codex, internal observability stacks, and the multi-agent orchestration system his team calls Symphony, Ryan has been pushing what happens when you optimize an entire codebase, workflow, and organization around agent legibility instead of human habit.We sat down with Ryan to dig into how OpenAI's internal teams actually use Codex, why the real bottleneck in AI-native software development is now human attention rather than tokens, how fast build loops, observability, specs, and skills let agents operate autonomously, why software increasingly needs to be written for the model as much as for the engineer, and how Frontier points toward a future where agents can safely do economically valuable work across the enterprise.We discuss:* Ryan's background from Snowflake, Brex, Stripe, and Citadel to OpenAI Frontier Product Exploration, where he works on new product development for deploying agents safely at enterprise scale* The origin of “harness engineering” and the constraint that kicked off the whole experiment: Ryan deliberately refused to write code himself so the agent had to do the job end to end* Building an internal product over five months with zero lines of human-written code, more than a million lines in the repo, and thousands of PRs across multiple Codex model generations* Why early Codex was painfully slow at first, and how the team learned to decompose tasks, build better primitives, and gradually turn the agent into a much faster engineer than any individual human* The obsession with fast build times: why one minute became the upper bound for the inner loop, and how the team repeatedly retooled the build system to keep agents productive* Why humans became the bottleneck, and how Ryan's team shifted from reviewing code directly to building systems, observability, and context that let agents review, fix, and merge work autonomously* Skills, docs, tests, markdown trackers, and quality scores as ways of encoding engineering taste and non-functional requirements directly into context the agent can use* The shift from predefined scaffolds to reasoning-model-led workflows, where the harness becomes the box and the model chooses how to proceed* Symphony, OpenAI's internal Elixir-based orchestration layer for spinning up, supervising, reworking, and coordinating large numbers of coding agents across tickets and repos* Why code is increasingly disposable, why worktrees and merge conflicts matter less when agents can resolve them, and what it really means to fully delegate the PR lifecycle* “Ghost libraries”, spec-driven software, and the idea that a coding agent can reproduce complex systems from a high-fidelity specification rather than shared source code* The broader future of Frontier: safely deploying observable, governable agents into enterprises, and building the collaboration, security, and control layers needed for real-world agentic workRyan Lopopolo* X: https://x.com/_lopopolo* Linkedin: https://www.linkedin.com/in/ryanlopopolo/* Website: https://hyperbo.la/contact/Timestamps00:00:00 Introduction: Harness Engineering and OpenAI Frontier00:02:20 Ryan's background and the “no human-written code” experiment00:08:48 Humans as the bottleneck: systems thinking, observability, and agent workflows00:12:24 Skills, scaffolds, and encoding engineering taste into context00:17:17 What humans still do, what agents already own, and why software must be agent-legible00:24:27 Delegating the PR lifecycle: worktrees, merge conflicts, and non-functional requirements00:31:57 Spec-driven software, “ghost libraries,” and the path to Symphony00:35:20 Symphony: orchestrating large numbers of coding agents00:43:42 Skill distillation, self-improving workflows, and team-wide learning00:50:04 CLI design, policy layers, and building token-efficient tools for agents00:59:43 What current models still struggle with: zero-to-one products and gnarly refactors01:02:05 Frontier's vision for enterprise AI deployment01:08:15 Culture, humor, and teaching agents how the company works01:12:29 Harness vs. training, Codex model progress, and “you can just do things”01:15:09 Bellevue, hiring, and OpenAI's expansion beyond San FranciscoTranscriptRyan Lopopolo: I do think that there is an interesting space to explore here with Codex, the harness, as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding. We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to.Build a user journey that you're trying to solve into code. It's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate in prompts. To let the model cook, you have to step back, right? Like you need to take a systems thinking mindset to things and constantly be asking, where is the Asian making mistakes?Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC.swyx: [00:01:00] All right.[00:01:03] Meet Ryan swyx: We're in the studio with Ryan from OpenAI. Welcome.Ryan Lopopolo: Hi,swyx: Thanks for visiting San Francisco and thanks for spending some time with us.Ryan Lopopolo: Yeah, thank you. I'm super excited to be here.swyx: You wrote a blockbuster article on harness engineering. It's probably going to be the defining piece of this emerging discipline, huh?Ryan Lopopolo: Thank you. It is it's been fun to feel like we've defined the discourse in some sense.swyx: Let's contextualize a little bit, this first podcast you've ever done. Yes. And thank you for spending with us. What is, where is this coming from? What team are you in all that jazz?Ryan Lopopolo: Sure, sure.Ryan Lopopolo: I work on Frontier Product Exploration, new product development in the space of OpenAI Frontier, which is our enterprise platform for deploying agents safely at scale, with good governance in any business. And. The role of VMI team has been to figure out novel ways to deploy our models into package and products that we can sell as solutions to enterprises.swyx: And you have a background, I'll just squeeze it in there. Snowflake, brick, [00:02:00] stripe, citadel.Ryan Lopopolo: Yes. Yes. Same. Any kind of customerswyx: entire life. Yes. The exact kind of customer that you want to,Vibhu: so I'll say, I was actually, I didn't expect the background when I looked at your Twitter, I'm seeing the opposite.Stuff like this. So you've got the mindset of like full send AI, coding stuff about slop, like buckling in your laptop on your Waymo's. Yes. And then I look at your profile, I'm like, oh, you're just like, you're in the other end too. Oh, perfect. Makes perfect.Ryan Lopopolo: I it's quite fun to be AI maximalist if you're gonna live that persona.Open eye is the place to do it. And it'sswyx: token is what you say.Ryan Lopopolo: Yeah. Certainly helps that we have no rate limits internally. And I can go, like you said, full send at this stay.swyx: Yeah. Yeah. So the Frontier, and you're a special team within O Frontier.Ryan Lopopolo: We had been given some space to cook, which has been super, super exciting.[00:02:47] Zero Code ExperimentRyan Lopopolo: And this is why I started with kind of a out there constraint to not write any of the code myself. I was figuring if we're trying to make agents that can be deployed into end to enterprises, they should be [00:03:00] able to do all the things that I do. And having worked with these coding models, these coding harnesses over 6, 7, 8 months, I do feel like the models are there enough, the harnesses are there enough where they're isomorphic to me in capability and the ability to do the job.So starting with this constraint of I can't write the code meant that the only way I could do my job was to get the agent to do my job.Vibhu: And like a, just a bit of background before that. This is basically the article. So what you guys did is five months of working on an internal tool, zero lines of code over a mi, a million lines of code in the total code base.You say it was cenex, more like it was cenex faster than you would've. If you had done it by end. SoRyan Lopopolo: yeah, thatVibhu: was the mindset going into this, right?Ryan Lopopolo: That's right.[00:03:46] Model Upgrades LessonsRyan Lopopolo: Started with some of the very first versions of Codex CLI, with the Codex Mini model, which was obviously much less capable than the ones we have today.Which was also a very good constraint, right? Quite a visceral feeling to ask the [00:04:00] model to build you a product feature. And it just not being able to assemble the pieces together.Which kind of defined one of the mindsets we had for going into this, which is whenever the model just cannot, you always pop open at the task, double click into it, and build smaller building blocks that then you can reassemble into the broader objective.And it was quite painful to do this. Honestly, the first month and a half was. 10 times slower than I would be. But because we paid that cost, we ended up getting to something much more productive than any one engineer could be because we built the tools, the assembly station for the agent to do the whole thing.[00:04:43] Model Generations, Build Systems & Background ShellsRyan Lopopolo: But yeah, so onward to G BT 5, 5, 1, 5, 2, 5, 3, 5 4. To go through all these model generations and see their kind of corks and different working styles also meant we had to adapt the code base to change things up when the model was revved. [00:05:00] One interesting thing here is five two, the Codex harness at the time did not have background shells in it, which means we were able to rely on blocking scripts to perform long horizon work.But with five, three and background shells, it became less patient, less willing to block. So we had to retool the entire build system to complete in under a minute and. This is not a thing I would expect to be able to do in a code base where people have opinions. But because the only goal was to make the Asian productive over the course of a week, we went from a bespoke make file build to Basil, to turbo to nx and just left it there because builds were fast at that point.swyx: Interesting. Talk more about Turbo TenX. That's interesting ‘cause that's the other direction that other people have been doing.Ryan Lopopolo: Ultimately I have. Not a lot of experience with actual frontend repo architecture.swyx: You're talking that Jessica built the sky. So I'm like, I know the NX team. I know Turbo from Jared [00:06:00] Palmer.And I'm like, yeah, that's an interesting comparison.[00:06:02] One Minute Build LoopRyan Lopopolo: The hill we were climbing right, was make it fast.swyx: Is there a micro front end involved? Is it how how complex reactRyan Lopopolo: electron base single app sort of thingswyx: And must be under a minute. That's an interesting limitation. I'm actually not super familiar with the background shelf stuff.Probably was talked about in the fight three release.Ryan Lopopolo: BA basically means that codex is able to spawn commands in the background and then go continue to work while it waits for them to finish. So it can spawn an expensive build and then continue reviewing the code, for example.swyx: Yeah.Ryan Lopopolo: And this helps it be more time efficient for the user invoking the harness.swyx: And I guess and just to really nail this, like what does one minute matter? Like why not five, okay, good. We want no. WeRyan Lopopolo: want the inner loop to be as fast as possible. Okay. One minute was just a nice round number and we were able to hit it.swyx: And if it doesn't complete, it kills it or some something,Ryan Lopopolo: No.We just take that as a signal that we need to stop what we're doing, double click, decompose a build graph a bit to get us to high back under so that we [00:07:00] can able the agent continue to operate.swyx: It's almost like you're, it's like a ratchet. It's like you're forcing build time discipline, because if you don't, it'll just grow and grow.That's right. And you mentioned that my current, like the software I work on currently is at 12 minutes. It sucks.Ryan Lopopolo: This has been my experience with platform teams in the past, where you have an envelope of acceptable build times and you let it go up to breach and then you spend two, three weeks to bring it back down to the lower end of the average low bed stop.But because tokens are so cheap Yeah. And we're so insanely parallel with the model, we can just constantly be gardening this thing to make sure that we maintain these in variants, which means. There's way less dispersion in the code and the SDLC, which means we can simplify in a way and rely on a lot more in variance as we write the software.[00:07:45] Observability, Traces & Local Dev StackVibhu: Lovely.[00:07:46] Humans Are BottleneckVibhu: You mentioned in your article, like humans became the bottleneck, right? You kicked off as a team of three people. You're putting out a million line of code, like 1500 prs, basically. What's the mindset there? So as much as code is disposable, you're doing a lot of review. A lot [00:08:00] of the article talks about how you wanna rephrase everything is prompting everything, is what the agent can't see.It's kind of garbage, right? You shouldn't have it in there. So what's like the high level of how you went about building it, and then how you address okay, humans are just PR review. Like how is human in the loop for this?Ryan Lopopolo: We've moved beyond even the humans reviewing the code as well.[00:08:19] Human Review, PR Automation & Agent Code ReviewRyan Lopopolo: Most of the human review is post merge at this point.But post, post merge, that's not even reviewed. That's justswyx: Oh, let's just make ourselves happy by YouRyan Lopopolo: haven't used fundamentally. The model is trivially paralyzable, right? As many GPUs and tokens as I am willing to spend, I can have capacity to work with my hood base.The only fundamentally scarce thing is the synchronous human attention of my team. There's only so many hours in the day we have to eat lunch. I would like to sleep, although it's quite difficult to, stop poking the machine because it makes me want to feed it. You have to step back, right?Like you need to take a systems thinking mindset to things and [00:09:00] constantly be asking where is the agent making mistakes? Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC, and usually what that has looked like is like we started needing to pay very close attention to the code because the agent did not have the right building blocks to produce.Modular software that decomposed appropriately that was reliable and observable and actually accrued a working front end in these things, right?[00:09:35] Observability First SetupRyan Lopopolo: So in order to not spend all of our time sitting in front of a terminal at most, doing one or two things at a time, invested in giving the model that observability, which is that that graph in the post here.swyx: Yeah. Let's walk through this traces and which existed firstRyan Lopopolo: we started with just the app and the whole rest of it. From vector through to all these login metrics, APIs was, I dunno, half an [00:10:00] afternoon of my time. We have intentionally chosen very high level fast developer tools. There's a ton of great stuff out there now.We use me a bunch, which makes it trivial to pull down all these go written Victoria Stack binaries in our local development. Tiny little bit of python glue to spin all these up. And off you go. One neat thing here is we have tried to invert things as much as possible, which is instead of setting up an environment to spawn the coding agent into, instead we spawn the coding agent, like that's the entry point.It's just Codex. And then we give Codex via skills and scripts the ability to boot the stack if it chooses to, and then tell it how to set some end variables. So the app and local Devrel points at this stack that it has chosen to spin up. And this I think is like the fundamental difference between reasoning models and the four ones and four ohs of the past, where these models could not think so you had to put them in [00:11:00] boxes with a predefined set of state transitions.Whereas here we have the model, the harness be the whole box. And give it a bunch of options for how to proceed with enough context for it to make intelligent choices. SoVibhu: sales, so like a lot of that is around scaffolding, right? Yes. Previous agents, you would define a scaffold. It would operate in that.Lube, try again. That's pivoted off from when we've had reasoning models. They're seeming to perform better when you don't have a scaffold, right? That's right.[00:11:28] Docs Skills GuardrailsVibhu: And you go into like niches here too, like your SPEC MD and like having a very short agent MG Agent md.swyx: Yes. Yes.Vibhu: Yeah. So you even lay out what it is here, but I likeswyx: the table contents.Vibhu: Yeah.swyx: Like stuff like this, it really helps guide people because everyone's trying to do this.Ryan Lopopolo: This structure also makes it super cheap to put new content into the repository to steer both the humans and the agents.swyx: You, you reinvented skills, right?Vibhu: One big agents andswyx: skills from first princip holdsRyan Lopopolo: all skills did not exist when we started doing this.Vibhu: You have a short [00:12:00] one 100 line overall table of contents and then you have little skills, right? Core beliefs, MD tech tracker. Yeah. Yeah. The scale is overRyan Lopopolo: The tech jet tracker and the quality score are pretty interesting because this is basically a tiny little scaffold, like a markdown table, which is a hook for Codex to review all the business logic that we have defined in the app, assess how it matches all these documented guardrails and propose follow up work for itself.Before beads and all these ticketing systems, we were just tracking follow up work as notes in a markdown file, which, we could spa an agent on Aron to burn down. There's this really neat thing that like the models fundamentally crave text. So a lot of what we have done here is figure out ways to inject textswyx: intoRyan Lopopolo: the system right when we get a page, because we're missing a timeout, for example.I can just add Codex in Slack on that page and say, I'm gonna fix this by adding a timeout. Please update our reliability documentation. To require that all network calls have [00:13:00] timeouts. So I have not only made a point in time fix, but also like durably encoded this process knowledge around what good looks like.swyx: Yeah.Ryan Lopopolo: And we give that to the root coding agent as it goes and does the thing. But you can also use that to distill tests out of, or a code review agent, which is pointed at the same things to narrow the acceptable universe of the code that's produced.swyx: I think one of the concerns I have with that kind of stuff is you think you're making the right call by making, it's persisted for all time across everything.Yes. But then you didn't think about the exceptions that you need to make, right? And that you have to roll it back.Vibhu: Part of it isswyx: also sometimes it can follow your s instructions too.Vibhu: It's somewhat a skill, right? So it determines when it uses the tools, right? Like it's not like it'll run outta every call.It'll determine when it wants to check quality score, right?Ryan Lopopolo: Yeah. And we do in the prompts we give these agents, allow them to push back,[00:13:51] Agent Code Review RulesRyan Lopopolo: When we first started adding code review agents to the pr, it would be Codex, CLI. Locally writes the change, pushes up a PR on [00:14:00] those PR synchronizations of review agent fires.It posts a comment. We instruct Codex that it has to at least acknowledge and respond to that feedback. And initially the Codex driving the code author was willing to be bullied by the PR reviewer, which meant you could end up in a situation where things were not converging. So yeah, we had to,swyx: he's just a thrash.Ryan Lopopolo: We had to add more optionality to the prompts on both of these things, right? The reviewer agents were instructed to bias toward merging the thing to not surface anything greater than a P two in priority. We didn't really define P two, but we gave it, youswyx: did define P two.Ryan Lopopolo: We gave it a framework within which to score its outputswyx: and then greater than P zero is worse, right?Yes. P two is very good.Ryan Lopopolo: P zero is you will mute the code place ifswyx: you merch thisRyan Lopopolo: thing, right?swyx: Yeah.Ryan Lopopolo: But also on the code authoring agent side, we also gave it the flexibility to either defer or push back against review feedback, right? This happens all the time, right? Like I happen to notice something and leave a code review, [00:15:00] which.Could blow up the scope by a factor of two. I usually don't mean for that to be addressed Exactly. In the moment. It's more of an FYI file it to the backlog, pick it up in the next fix it week sort of thing. And without the context that this is permissible, the coding agents are gonna bias toward what they do, which is following instructions.swyx: Yeah.[00:15:19] Autonomous Merging Flowswyx: I do wanted to check in on a couple things, right? Sure. All the coding review agent, it can merge autonomously. I think that's something that a lot of people aren't comfortable with. And you have a list here of how much agents do they do Product code and tests, CI configuration and release tooling, internal Devrel tools, documentation eval, harness review, comments, scripts that manage the repository itself, production dashboard definition files, like everything.Yes. And so they're just all churning at the same time, is there like a record that, that any human on the team pulls to stop everythingRyan Lopopolo: Because we are building a native application here. We're not doing continuous deploy. So there's still a human in the loop for cutting the release branch.I see. We require a blessed [00:16:00] human approved smoke test of the app before we promote it to distribution, these sort of things.swyx: So you're working on the app, you're not building like infrastructure where you have like nines of reliability, that kinda stuff?Ryan Lopopolo: That's correct. That's correct. Okay. And also like full recognition here that all of this activity took in a completely greenfield repository.There's. Should be no script that this applies generally toswyx: this is a production thing, you're gonna shipRyan Lopopolo: toswyx: customers. Of course. Yeah, of course. So this is realVibhu: And like one of the things there is, you mentioned you started this as a repo from scratch. The onboarding first month or so was pretty, it was like working backwards, right?Yeah. And then you had to work with the system and now you're at that point where you know, you're very autonomous. I'm curious like, okay, so what, how human in the loop is it? So what are the bottlenecks that you wish you could still automate? And part of that is also like, where do you see the model trajectory improving and offloading more human in the loop?We just got 5.4. It's a really good,Ryan Lopopolo: fantastic model, by the way.Vibhu: Yeah. Yeah. It's the first one that's merged. Top tier coding. So it's codex level coding and reasoning. So general reasoning both in one model. SoRyan Lopopolo: andVibhu: computer [00:17:00] use vision.Ryan Lopopolo: Now we now with five four, I can just have Codex write the blog post, whereas for this one I had to balance between chat.swyx: Oh, I need to, I might be out of a job. Oh my God.Ryan Lopopolo: Oh,swyx: I know. You just gave me an idea for a completely AI newsletter that five four could do. Yeah, I get it Now.Ryan Lopopolo: This sort of thing is just one example of closing the loop, right? Like the dashboard thing you mentioned. We have Codex authoring the Js ON, for the Grafana dashboards and publishing them and also responding to the pages, which means when it gets the page, it knows exactly which dashboards are defined and what alerts.What alert was triggered by which exact log in the code base. ‘cause all of this stuff is collated together.swyx: It has to own everything.Yes. Yeah. Yeah.Ryan Lopopolo: And it means that if we have an outage that did not result in a page. It has the existing set of dashboards available to it. It has the existing set of metrics and logs and can figure out where the gaps in the dashboard are or [00:18:00] in the underlying metrics and fix them in one go.In the same way, you would have a full stack engineer be able to drive a feature from the backend all the way to the front end.Vibhu: So it, it seems like a lot of the work you guys had to do was you as a small team are fully working for a way that the model wants the software to be written. It's like less human legible for better. Code legibility, agent legibility. How do you think that affects broader teams? So one at OpenAI, do liaison, like this is how software should be written. Like I can imagine, say you join a new team with this methodology, this mindset there's ways that, teams do code review, teams write code, like teams are structured and a lot of it is for human legibility.So should we all swap? Like how does this play back one broader into OpenAI and then like broader into the software engineering, right? Is it like teams that pick this up will it's pretty drastic, right? You have to make a pretty big switch. Should they just full send Yeah.Ryan Lopopolo: The mindset is very much that I'm removed from the process, right? I can't really have deep code level opinions about [00:19:00] things. It's as if I'm. Group tech leading a 500 person organization.Vibhu: Yeah.Ryan Lopopolo: Like it's not appropriate for me to be in the weeds on every pr. This is why that post merge code review thing is like a good analog here, right?Like I have some representative sample of the code as it is written, and I have to use that to infer what the teams are struggling with, where they could use help, where they're already moving quickly and I can pivot my focus elsewhere.Vibhu: Yeah.Ryan Lopopolo: So I don't really have too many opinions around the code as it is written.I do, however, have a command based class, which is used to have repeatable chunks of business logic that comes with tracing and metrics and observability for free. And the thing to focus on is not how that business logic is structured, but that it uses this primitive ‘cause I know that's gonna give leverage by default.Vibhu: Yeah.Ryan Lopopolo: Yeah, back to that sort of systems stinking,Vibhu: and you have part of that in your blog post, enforcing architecture and ta taste how you set boundaries for what's used. There's also a section on redefining [00:20:00] engineering and stuff, but yeah, it's just, it's interesting to hear,Ryan Lopopolo: and as the models have gotten better, they have gotten better at proposing these abstractions to unblock themselves, which again, lets me move higher and higher up the stack to look deeper into the future on what ultimately blocked the team from shipping.swyx: Yeah. You mentioned so you, this is primarily a, it is like a 1 million line of code base electron app. But it manages its own services as well, so it's like a backend for front end type thing.Ryan Lopopolo: We do have a backend in there, but that's hosted in the cloud.Yeah. This sort of structure is actually within the separate main and render processesWithin theswyx: electric.That's just how electronic works.Ryan Lopopolo: Yeah, of course. So have also treated like. MVC style decomposition with the same level of rigor, which has been very fun.swyx: I have a fun pun. This is a tangent, NVC is model view controller. Any sort of full stack web Devrel knows that.But my AI native version of this is Model view Claw, the clause the harness.Ryan Lopopolo: That's right. That's right. I do think that there is an interesting space to [00:21:00] explore here with Codex, the harness as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding.We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to build, a user journey that you're trying to solve into code, it's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate and prompts to let the model cook.Yeah. It's been very fun. And there's also a very engineering legible way of increasing capabil. It's fantastic, right? Yeah. Just give you, just give the model scripts, the same scripts you would already build for yourself.swyx: Yeah.Yeah. So for listeners, this is Ryan saying that software engineering or coding against will eat knowledge work like the non-coding parts that you would normally think.Oh, you have to build a separate agent for it. No, start a coding agent and go out from there. Which open Claw has like it's pie Underhood.Ryan Lopopolo: [00:22:00] Yes.Vibhu: Basically define your task in code. Everything is a codingswyx: agent by the way. Since I brought it up, it's probably the only place we bring it up. Is any open claw usage from you?Any?Ryan Lopopolo: No. No. Not for me. I don't have any spare Mac Minis rattling around my house.swyx: You can afford it? No. I just, I'm curious if it's changed anything in opening eye yet, but it's probably early days. And then the other, the other thing I, I wanna pull on here is like you mentioned ticketing systems and you mentioned prs and I'm wondering if both those things have to go away or be reinvented for this kind of coding.So the git itself and is like very hostile to multi-agent.Ryan Lopopolo: Yeah. We make very heavy use of work trees.swyx: But like even then, like I just did a, dropped a podcast yesterday with Cursors saying, and they said they're getting rid of work trees ‘cause it still has too many merge conflicts.It's still un too un unintuitive. But go ahead.Ryan Lopopolo: The models are really great at resolving merge conflicts. Yeah. And to get to a state where I'm not synchronously in the loop in my terminal, I almost don't care that there are mergeswyx: with disposable.[00:23:00] Yeah.Ryan Lopopolo: We invoke a dollar land skill and that coaches codex to push the PR Wait for human and agent reviewers Wait for CI to be green.Fix the flakes if there are any merged upstream. If the PR comes into conflict, wait for everything to pass. Put it in the merge queue. Deal with flakes until it's in Maine. End. This is what it means to delegate fully, right? This is in a, very large model re probably a significant tax on humans to get PRS merged, but the agent is more than capable of doing this and I really don't have to think about it other than keep my laptop open.swyx: Yeah. I used to be much more of a control freak, but now I'm like, yeah, actually you could do a better job of this than me. Yeah. With the right context. Yes.[00:23:47] Encoding Requirementsswyx: Anything else in harness in general? Just this piece, I just wanna make sure we,Ryan Lopopolo: I think one thing that I maybe didn't make super clear in the article that I heard on Twitter as an interesting, that's respond [00:24:00]swyx: to them.What's the chatter and then what's your response?Ryan Lopopolo: Ultimately, all the things that we have encoded in docs and tests and review agents and all these things are ways to put all the non-functional requirements of building high scale, high quality, reliable software into a space that prompt injects the agent.We either write it down as docs, we add links where the error messages tell how to do the right thing. So the whole meta of the thing is to basically tease out of the heads of all the engineers on my team, what they think good looks like, what they would do by default, or what they would coach a new hire on the team to do to get things to merch.And that's why we pay attention to all the mistakes, mistakes that the agent makes, right? This is code being written that is misaligned with some as yet not written down, non-functional requirement.swyx: Sorry, what? Did the online people misunderstand orRyan Lopopolo: No,swyx: whatyouRyan Lopopolo: responded to? Somebody just literally said that.I was like, oh yeah,swyx: okay,Ryan Lopopolo: This is the [00:25:00] thing. This is what I've been doing. Oh, youswyx: agree? Yeah. I see. Interesting.Ryan Lopopolo: One other neat thing, which I did totally did not expect is folks were just. Taking the link to the article and giving it to pi or Codex and say, make my repo this,Vibhu: you achi a whole recursion.Ryan Lopopolo: And it was wildly effective. Really? It was wildly effective. NoVibhu: way. It just actually is something I tried with five, four yesterday. I didn't have time. Last time I was like out speaking of something, and this is one of my things, I was like, okay, I have this article. Can we just scaffold out what it would be like to run this?And I, I did it first as that and then I was like, okay, let me take another little side repo and say okay, if I was to fully automate this like this because I haven't written a line of code, it'sRyan Lopopolo: like over full, setVibhu: it right. The side thing I'm doing of voice. TTS I'm just like, slobbing out, whatever.It's nothing production. I'm like, how would I make this like this? And it's actually like a really good way. It's like a good way to learn what could be changed, what could be like, it's just a good analyzing, right? You give it all the codes, you give it all the context, you give it the article and it walks you through it very well.That's right. That's right.[00:25:57] Inlining Dependencies[00:25:57] Dependencies Going Away & Brett Taylor's Responseswyx: I guess one more thing before we go to Symphony is I wanted to cover [00:26:00] Brett Taylor's response. We had him on the show. He is your chairman, which is wild. Yeah. That he's reading your articles as well and like getting engaged in it. He says software dependencies are going away.Basically they can just be like vendored. Yes. Response.Ryan Lopopolo: Aswyx: hundred percent. A hundred percent agree. You still pro qr, you still pay Datadog. You still pay Temporal. Thank you.Ryan Lopopolo: Yep. The level of complexity of the dependencies that we can internalize is, I would say low, medium right now. Just based on model capability.What does the,swyx: what is medium?Ryan Lopopolo: I would say like a. A couple thousand line dependency is a thing that we could in-house No problem. Call in an afternoon of time. One neat thing about it is like probably most of that code you don't even need. Like by in-house and abstraction, you can strip away all the generic parts of it and only focus on what you need to enable the specific thing.Yes. You're building,swyx: I've been calling this the end of b******t plugins.Ryan Lopopolo: Yeah.swyx: Because there's so much when I published an open source thing, I want to accept everything, be liberal. I want to accept, this is post's law, but that means there's so much bloat. Yes. There's so much overhead.Ryan Lopopolo: One other neat thing about [00:27:00] this too is when we deploy Codex Security on the repo, it is able to deeply review and change. The internalized dependencies in a much lower friction way than it would be to like, push patches upstream, wait for them to be released, pull them down, make sure that's compatible with all the transitive I have in my repo and things like that.So it's also much lower friction to internalize some of these things if code is free. ‘cause the tokens are cheap sort of thing.swyx: Yeah. Yeah. I think like the only argument I have against this is basically scale testing, which obviously the larger pieces of software like Linux, MySQL, he calls up even the Datadog and Temporals and then maybe security testing where Yes.Classically, I think, is it linis tos, it said security open source is the best disinfectant.Ryan Lopopolo: Many eyes.swyx: Many eyes. And if inline your dependencies and code them up, you're gonna have to relearn mistakes from other people that Yep.Ryan Lopopolo: Yep. And to internalize that dependency, you're back to zero and you have to start.Reassembling all those bits and pieces to Yeah. Have [00:28:00] high confidence in the code as it is written. Yeah.Vibhu: Even part of the first intro of this, you basically mentioned like everything was written by codex, including internal tooling, right? So internal tooling, like when you're visualizing what's going on it's writing it for itself.swyx: Yeah. I'm built internal tools way I now, and like I just show them off and they're like, how long did you spend? And I didn't spend any time. I just prompted it,Ryan Lopopolo: very funny story here.swyx: Yeah, go ahead.Ryan Lopopolo: We had deployed our app to the first dozen users internally had some performance issues, so we asked them to export a trace for us get a tar ball, gave it to our on-call engineer, and he did a fantastic job of working with Codex to build this beautiful local Devrel tool, next JS app, the drag and drop the tar ball in, and it visualizes the entire trace.It's fantastic. Took an afternoon, but none of this was necessary. Because you could just spin up codex and give it the tar ball and ask the same thing and get the response immediately. So in a way, optimizing for human [00:29:00] legibility of that debugging process was wrong. It kept him in the loop unnecessarily when instead he could have just like Codex cooked for five minutes and gotten this same.swyx: Yeah, you verify your instincts here of this is how we used to do it. Or this is how I would have used to solve it.Ryan Lopopolo: Yeah. In this local observability stack. Like sure, you can de deploy Yeager to visualize the traces, but I wouldn't expect to be looking at the traces in the first place because I'm not gonna write the code to fix them.swyx: Yeah. So basically there needs to be like this kind of house stack and owning the whole loop. I think that is very well established. And it sounds like you might be like sharing more about that in the future, right?Ryan Lopopolo: Yeah. I think we're excited to do[00:29:36] Ghost Libraries Specs[00:29:36] Ghost Libraries & Distributing Software as SpecsRyan Lopopolo: We're gonna talk about Symphony in a little bit, but like the way we distribute it as a spec, which I think folks are calling Ghost Libraries on Twitter.This is like a such a cool name. It does mean it becomes much cheaper to share software with the world, right? You define a spec, how you could build your own specifying as much as is required for a coding agent to reassemble it [00:30:00] locally. The flow here is very cool. Like we have taken. All the scaffolding that has existed in our proprietary repo spun up a new one.Ask Codex with our repo as a reference. Write the spec. We tell it. Spin up a team ox spawn a disconnected codex to implement the spec. Wait for it to be done. Spawn another codex and another team ox to review the spec com or review the implementation compared to upstream and update the spec so it diverges less.And then you just loop over and over Ralph style until you get a spec that is with high fidelity able to reproduce the system as it is. It's fantastic.Vibhu: And you're basically, you're not really adding any of your human bias in there, right? That's correct. A lot of times people write a spec and be like, okay, I think it should be done this way, and you'll riff on something.And it's no, the agent could have just handled it like you're still scaffolding in a sense, right? I want it done this way. It can determine its spec better.swyx: That's right. That's right. Part of me it, I'm, I've been working a lot on evals recently, and part of me is wondering if [00:31:00] an agent can produce a spec that it cannot solve.Is it always capable of things that he can imagine or can you imagine things that it is impossible to do?Ryan Lopopolo: I think with Symphony, we, there's like this there's this axis where you have things that are easier, hard, or established or new, right? And I think things that are hard and new is still something that the models need humans.Yeah. Drive.swyx: Yeah. Yeah.Ryan Lopopolo: But I think those other quadrants are largely salt. Given the right scaffold and the right thing that's gonna drive the agent to completion,swyx: it's crazy that it solved,Ryan Lopopolo: but it means that the humans, the ones with limited time and attention get to work on the hardest stuff, like the problems where it's pure white space out in front. Or like the deepest refactorings where you don't know what the proper shape of the interfaces are. And this is where I wanna spend my time. ‘cause it lets me set up for the next level of scale.swyx: Yeah. Yeah. Amazing. Let's introduce Symphony.I think we've been mentioning it every now and then. Elixir. Interesting option.Ryan Lopopolo: Yeah.swyx: Yeah. I'm not,Ryan Lopopolo: again, like the [00:32:00] elixir manifestation here is just a derivative. Is it a modelswyx: chosen? Yeah.Ryan Lopopolo: Yeah. Yeah. And it chose that because the process supervision and the gen servers are super amenable to the type of process orchestration that we're doing here.You are essentially spinning up little Damons for every task that is in execution and driving it to completion, which. Means the mall gets a ton of stuff for free by using Elixir and the Beam.swyx: I had to go do a crash course in Beam and Elixir, and I think most people are not operating at that scale of concurrency where you need that.But it is a good mental model for Resum ability and all those things. And these are things I care about. But tell me the story, the origin story of Symphony. What do you use it for? Is this, how did it form maybe any abandoned paths that you didn't take?[00:32:46] Terminal Free Orchestration[00:32:46] Symphony: Removing Humans from the LoopRyan Lopopolo: At the end of December we were at about three and a half PRS per engineer per day.This was before five two came out in the beginning of January. Everyone gets back from holiday with five two and no other work [00:33:00] on the repository. We were up in the five to 10 PRS per day per engineer. And I don't know about y'all, but like it's very taxing to constantly be switching like that. Like I was pretty tapped out at the end of the day, again, where are the humans spending their time? They're spending their time context switching between all these active tmox pains to drive the agent forward.swyx: Yeah. No way. Yeah.Ryan Lopopolo: So let's again, build something to remove ourselves from the loop. And this is what frantic sprinted adapt here to find a way to remove the need for the human to sit in front of their terminal.So a lot of experimentation with Devrel boxes and, automatically spinning up agents, like it seems like a fantastic end state here, where my life is beach. I open live twice a day and say yes no to these things. Yeah. And this is again, a super, super interesting framing for how the work is done.Because I become more latency and sensitive. I have [00:34:00] way less attachment to the code as it is written. Like I've had close to zero investment in the actual authorship experience. So if it's garbage. I can just throw it away and not care too much about it. In Symphony, there's this like rework state where once the PR is proposed and it's escalated to the human for review, it should be a cheap review.It is either mergeable or it is not. And if it's not, you move it to rework. The elixir service will completely trash the entire work tree NPR and start it again from scratch. Okay. And this is that opportunity again to say, why was it trash right? What did the agent do that wasswyx: bad. Yeah.Ryan Lopopolo: Fix that before moving the ticket toswyx: endRyan Lopopolo: of progress again.swyx: Yeah. Why is this not in codex app? I guess this, you guys are ahead of Codex app,Ryan Lopopolo: yeah, so the way the team has been working is basically to be as AI pilled as possible and spread ahead. And a lot of the things we have worked on have fallen out [00:35:00] into a lot of the products that we have.Like we were in deep consultation with the Codex team to. Have the Codex app be a thing that exists, right? To have skills be a thing that Codex is able to use. So we didn't have to roll our own to put automations into the product. So all of our automatic refactoring agents didn't have to be these hand rolled control loops.It has been really fantastic to be, in a way, un anchored to the product development of Frontier and Codex and just very quickly try to figure out what works and then later find the scalable thing that can be deployed widely. It's been a very fun way to operate. It's certainly chaotic. I have lost track very often of what the actual state of the code looks like.‘cause I'm not in the loop. There was. One point where we had wired playwright directly up to the Electron app. With MCPM CCPs, I'm pretty bearish on because the harness forcibly injects all those tokens in the [00:36:00] context, and I don't really get a say over it. They mess with auto compaction. The agent can forget how to use the tool.There's probably only what three calls in playwright that I actually ever want to use. So I pay the cost for a ton of things. Somebody vibed a local Damon that boots playwright and exposes a tiny little shim CLI to drive it. And I had zero idea that this had occurred because to me, I run Codex and it's able to, it's oh, it's better.Yeah. Like no knowledge of this at all. Uhhuh.[00:36:30] Multi Human ChaosRyan Lopopolo: So we have had like in human space to spend a lot of time doing synchronous knowledge sharing. We have a daily standup that's 45 minutes long because we almost have to. Fan out the understanding of the current state.swyx: Yeah, I was gonna say this is good for a single human multi-agent, but multi human, multi-agent is a whole like po like explosion of stuff.Ryan Lopopolo: Yeah. And that this is fundamentally why we have such a rigid, like 10,000 [00:37:00] engineer level architecture in the app because we have to find ways to carve up the space so people are not trampling on each other.swyx: Sorry, I don't get the 10,000 thing. Did I miss that?Ryan Lopopolo: The structure of the repository is like 500 NPM packages.It's like architecture to the excess for what you would consider, I think normal for a seven person team. But if every person is actually like 10 to 50. Then the like numbers on being super, super deep into decomposition and sharding and like proper interface boundaries make a lot more sense.swyx: Yeah. To me, that's why I talked about Microfund ends and I, an anex is from that world, but Cool. It is just coming back to, to, to this I dunno if you have other, thoughts on. Orchestrating so much work coin going through this. Is this enough? Is this like any aha moments?Vibhu: It'll be interesting to see like where, okay, so right now you pick linear as your issue tracker, right?swyx: Or it's like a is it actually linear? This is actually linear.[00:37:55] Linear vs Slack WorkflowVibhu: Oh, that's linear. It's linear.swyx: Oh I never looked atVibhu: video. The demo video I had to download to [00:38:00] run.swyx: So I, because I'm a Slack maxie, but Yeah, linear. Linear is also really good. Yes,Ryan Lopopolo: we do make a good use of Slack. We we fire off codex to do all these lotion, elasticity, fix ups, the things that like sync that knowledge into the repository.It's super cheap. Yeah.swyx: Yeah.Ryan Lopopolo: Just do it in Codex.swyx: My biggest plug is OpenAI needs to build Slack. You need to own Slack. Build yours. Turn this into Slack.Ryan Lopopolo: I did read about it. Youswyx: did?Ryan Lopopolo: Yeah.[00:38:25] Collaboration Tools for AgentsRyan Lopopolo: I would say that if we think that we want these agents to do economically valuable work, which is like this is the mission, right?We want AI to be deployed widely, to do economically valuable work, then we need to find ways for them to naturally collaborate with humans, which means collaboration tooling, I think, is an interesting space to explore.swyx: Yeah, totally. Yeah. GitHub, slack, linear.Vibhu: Yeah, that was my thing. Okay, where do we see right now Codex has started Codex Model, then CLI, now there's an app, app can let me shoot off multiple Codex is in parallel, but there's no great team collaboration for Codex.And it [00:39:00] seems like your team had some say into what comes out, right? So you talked to ‘em, codex kind of was a thing. From there, if you guys are on the bound, what stuff that like, you might not focus on, but what do you expect other people to be building, right? So people that are like five x 50 Xing.Should you build stuff that's like very niche for your workflow, for your team? Should it be more general so other people can adopt? Is there a niche there? ‘Cause part of it is just okay, is everything just internal tooling? Do we have everything our own way? Like the way our team operates has our own ways that we like to communicate or is there a broader way to do it?Is it something like a issue tracker? Just thoughts if you wanna riff on that.[00:39:35] Standardizing Skills and CodeRyan Lopopolo: I think TBD we have not figured this out in a general way. I do think that there is leverage to be had in making the code and the processes as much the same as possible. If you think that code is context, code is prompts, it's better from the agent behavior perspective to be able to look in a package in directory X, Y, Z, and it not to have to page so [00:40:00] deeply into directory if you C, because they have the same structure, use the same language, they have the same patterns internally.And that same like leverage comes from aligning on a single set of skills that you're pouring every engineer's taste into to make sure that the agent is effective. So like in our code base, we have, I think, six skills. That's it. And if some part of the software development loop is not being covered, our first attempt is to encode it in one of the existing setup skills, which means that we can change the agent behavior.Yeah. More cheaply than changing the human driver behavior.swyx: Yeah.[00:40:39] Self Improvement via Logsswyx: Have you ever, have you experimented with agents changing their own behavior?Ryan Lopopolo: We do.swyx: Yeah. Or parent agent changing a subagents, behavior or something like that.Ryan Lopopolo: We have some bits for skill distillation. So for example, there's one neat thing you can do with Codex, which is just point it at its own session logs to ask it to tell you how you can use [00:41:00] the tool pedal better.swyx: It's like introspectionRyan Lopopolo: or ask it to do things. I useVibhu: this session better. What skills should Iswyx: high? I like the modification of, you can do, just do things to you can just ask agent to do things.Ryan Lopopolo: Yeah. You can just codex things. This is like a, this is like a silly emoji that we have, right? You can just codex things, you can just prompt things.It's really glorious future we live in, but okay, you can do that one-on-one. But we're actually slurping these up for the entire team into blob storage and. Running agent loops over them every day to figure out where as a team can we do better and how do we reflect that back into the repositories?Yes, though everybody benefits from everybody else's behavior for free. Same for like PR comments, right? These are all feedback. That means the code as written, deviated from what was good, a PR comment, a failed build. These are all signals that mean at some point the agent was missing context. We gotta figure out how toswyx: Yeah.Ryan Lopopolo: Slurp it up and put it back in the reboot.swyx: By the way, I do this exactly right. I used to, when I use cloud code for [00:42:00] knowledge work, cloud cowork is like a nice product, right? Yes. In I think you would agree. I always have it tell me what do I do better next time? And that's the meta programming reflection thing.So I almost think like you have six reflection extraction levels in symphony and almost like the zero of layer. So the six levels are PO policy, configuration, coordination, execution, integration, observability. We've talked about a couple of these, but the zero layer is like the, okay, are we working well?Can we improve how we work? Yes. Can I modify my own workflow without MD or something? I don't know.Ryan Lopopolo: Yeah, of course. Yeah, of course you can. Like this thing is also able to cut its own tickets ‘cause we give it full access.Yeah. Make it a ticket to have it cut. Tickets you can.Put in the ticket that you expect it to file as on follow up work,swyx: like Yeah. Self-modifying. Yeah.Ryan Lopopolo: Yeah.[00:42:44] Tool Access and CLI FirstRyan Lopopolo: Put, don't put the agent in a box. Give the agent full accessibility over it. Domain.swyx: I had a mental reaction when you said don't put the agent in a box. So I think you should put it in a box. Like it's just that you're giving the box everything it needs.Ryan Lopopolo: Yeah. Context and tools.swyx: But we're like, as developers, we're used to calling [00:43:00] out to different systems, but here you use the open source things like the Prometheus, whatever, and you run it locally so that you can have the full loop. I assume.Ryan Lopopolo: Yep.Vibhu: I think likeRyan Lopopolo: another, you wanna minimize cloud, cloud dependencies.Vibhu: You also want to make sure that you think about what the agent has access to. What does it see? Does it go back into the loop, like from the most basic sense of you let it see its own like calls, traces it can determine where it went wrong. But are you feeding that back in? So you know, just the most basic level of you wanna see exactly what's input output, like does the agent have access to.What is being outputted, right? It can self-improve a lot of these things. It's allRyan Lopopolo: text, right? My job is to figure out ways to funnel text from one agent to the other.swyx: It's so strange like way back at the start of this whole AI wave Andre was like, English is the hottest day programming language.It's here, it's just Yeah. The feature as well.Vibhu: A lot of, okay. Like a lot of software, a lot of stuff. There's a gui, it's made for the human. We're seeing the evolution of CLI for everything, right? All tools have CLIs. Your agents can use [00:44:00] them well, do we get good vision? Do we get good little sandboxes?Like right now? It's a really effective way, right? Models love to use tools. They love the best. They love to read through text. So slap a CLI let it go loose. That works for everything.Ryan Lopopolo: It does. Yeah. Yeah.[00:44:14] UI Perception and RasterizingRyan Lopopolo: We've also been adapting nont, textual things to that shape in order to improve model behavior in some ways, right?We want the agent to be able to see the UI agents do not perceive visually in the same way that we do. They don't see a red box, they see red box button, right? They see these things in latent space. So if we want, Hey, yeah, I do. We haveswyx: a ding if that goes off every time. Alien spaceRyan Lopopolo: ding.Anyway if we wanna actually make it see the layout, it's almost easier to rasterize that image to ask EOR and feed it in to the agent. Ha. And there's no reason you can't do both, right? To like further refine how the model perceives the object it's [00:45:00] manipulating.swyx: Cool. Could we, you wanna talk about a couple more of these layers that might bear more introspection or that you have personal passion for?[00:45:07] Coordination Layer with ElixirRyan Lopopolo: I will say that the coordination layer here was a really tricky piece to get right.swyx: Let's do it. Yep. I'm all about that. And this is Temporal core.Ryan Lopopolo: This is where when we turn the spec into Elixir, where like the model takes a shortcut, right? Like it's oh, I have all these primitives that I can make use of in this lovely runtime that has native process supervision.Which is I think, a neat way to have taken the spec and made it more choices achievable by making choices that naturally mapswyx: Yeah.Ryan Lopopolo: To the domain, right? In the same way that like you would prefer to have a TypeScript model repo if you are doing full stack web development, right? Because the ability to share types across the front end and backend reduces a lot of complexity.And becauseswyx: that's what graph kill used to be.Ryan Lopopolo: That's right. Andswyx: I don't know if it's still alive, butRyan Lopopolo: [00:46:00] no humans in the loop here. So like my own personal ability to write or not write elixir. Doesn't really have to bias us away from using the right tool for the job. It is just wild.swyx: Love it. I love it.Yeah. I wonder if any languages struggle more than others because of this? I feel like everyone has their own abstractions. That would make sense. But maybe it might be slower, it might be more faulty where like you'd have to just kick the server every now and then. I, I don't know. I think observability layer is really well understood.Integration layer, CP is dead. I think all these just like a really interesting hierarchy to travel up and down. It's common language for people working on the system to understandRyan Lopopolo: The policy stuff is really cool, right? Yeah. You don't really have to build a bunch of code to make sure the system wait for the, to passswyx: it's institutional knowledge.Ryan Lopopolo: Yeah. You just give it the G-H-C-L-I with some text that say CI has to pass. It makes the maintenance of these systems a lot easier.[00:46:57] Agent Friendly CLI Outputswyx: Do you think that CLI maintainers need to be [00:47:00] do anything special for agents or just as is? It's good because like I don't think when people made the G GitHub, CLI, they anticipated this happening.Ryan Lopopolo: That's correct. The GH CLI is fantastic. It's great super industry.swyx: Everyone go try GH repo create GH pull and then pull request number, right? GH HPR, like 1 53, whatever. And then it like pullsRyan Lopopolo: basically my only interaction with the GitHub web UI at this point is GH PR view dash web.Exactly. Glanceswyx: at the diffRyan Lopopolo: and be like Sure thing. Send it. Yeah. But the CLI are nice ‘cause they're super token efficient and they can be made more token efficient really easily. Like I'm sure you all have seen like I go to build Kite or Jenkins and I could just get this massive wall of build output.And in order to unblock the humans, your developer productivity team is almost certainly gonna write some code that parses the actual exception out of the build logs and sticks it in a sticky note at the top of the page. And you basically [00:48:00] want CLI to be structured in a similar way, right? You're gonna want to patch dash silent to prettier because the agent doesn't care that every file was already formatted.Just wants to know it's either formatted or not. So it can then go run a right command. Similarly, like in our PNPM distributed script runner, when we had one, when you do dash recursive, like it produces a absolute mountain of text. But all of that is for passing. Test suites. So we ended up wrapping all of this in another scriptswyx: to suppress the,Ryan Lopopolo: which you can vibe the channel only output the failing parts of the tests.swyx: You make a pipe errors versus the standard, standard out. I don't know. Okay. Whatever. Too much thinking have to do that. The CII used to maintain SCLI for my company and yeah, this is like core, very core to my heart. But you're vibing my job.Ryan Lopopolo: That's right.swyx: Cool. Any other things?This is a long spec. [00:49:00] I appreciate that. It's got a lot of strong opinions in here. Any other things that we should highlight? I think obviously you can spend the whole day going through some of these, but I do think that some of these have a lot of care or some of this you might wanna tell people, Hey, take this, but, make it your own.[00:49:15] Blueprint Spec and GuardrailsRyan Lopopolo: Fundamentally, software is made more flexible when it's able to adapt to the environment in which it is deployed, which means that things like linear or GitHub even are specified within the spec, but not required pieces of it. There's like a more platonic ideal of the thing that you could swap in like Jira or Bitbucket, for example.But being able to tightly specify things like the ID formats or how the Ralph Loop works for the individual agents. Basically means you can get up and running with a fully specified system quickly that you then evolve later on. I think we never intended for this to be a static spec that you can [00:50:00] never change.It's more like a blueprint to get something worth a starting point up and running.swyx: Yeah.Ryan Lopopolo: For you then to vibe later to your heart's content,swyx: you have like code and scripts in here where it's oh, I think this is a really good prompt. It's just a very long prompt.Ryan Lopopolo: Fundamentally, the agents are good at following instructions, so give them instructions.And it will, improve the reliability of the result. We, much like the way we use Symphony, we don't want folks to have to monitor the agent as it is vibing the system into existence. So being very opinionatedVery strict around what these success criteria are means that our deployment success rate goes up. Yeah. It means we don't have to get tickets on this thing.Vibhu: Think it all goes back to that like code to disposable, right? Like early on when you had CLI or you'd kick off a Codex run, it would take two hours. You would wanna monitor okay, I'm in the workflow of just using one.I don't want it to go down the wrong path. I'll cut it off and, just shoot off four, like that was my favorite thing of the Codex app, right? Yeah. Just Forex it like, [00:51:00] it's okay. One of them will probably be right, one of them might be better. Stop overthinking it. Like my first example was probably like deep research.When you put out deep research and I'd ask it something like, I asked it something about LLM, it thought it was legal something and spent an hour, came back with a report completely off the rails. And I was like, okay, I gotta monitor this thing a bit. No don't monitor it. Just you want to build it so it's that it, it goes the right way.And you don't wanna, you don't wanna sit there and babysit, right? You don't want to babysit your agentsRyan Lopopolo: with that deep research query that you made. Looking at the bad result, you probably figured out you needed to tweak your prompt Yeah. A bit, right? That's that guardrail that you fed back into the code base for the task, your prompt to further align the agent's execution.Same sort of concept supply there too.swyx: When you talk, how are the customers feelingRyan Lopopolo: for Symphony? I think we have none, right? This is a thing we have put out into theswyx: world. Symphony's internal, right? As long as you are happy, you are the customer. That'

This year's GDC Special is a big one. So big that this episode is over 2 hours long... and it's only part 1 (but your nice hosts don't know that yet)!0:15:49GDC 2026 - Monday GDC Encounters: Speed Networking Day 1Game Developer ConferenceThe Tension: Designing for Discomfort in 'Wanderstop'Steven MargolinGame Developer ConferenceThe Black Designers' Dilemma"Carl Varnado, Jabari Ali, Jarory DeJesus, Evan Narcisse"Game Developer ConferenceThe Games Industry Social (aka: GIG IRL)Media Indie Exchange (aka: The MIX)DogpileToot GamesGame Funding: Lessons from Outersloth"Victoria Tran, Forest Willard"Game Developer ConferenceOutersloth reveals its game funding agreement with developersAlex Forbes-CalvinGamesIndustry.bizFrom Beautiful to Playable: Texture Compression Secrets Every Game Artist Shoul…Jad DeebGame Developer ConferenceFour Artists Use Substance 3D to Texture 'Clair Obscur: Expedition 33'"Alan Reynaud, Mathieu Costat"Game Developer ConferenceGDC 101"Sam Warnke, Natalie Sam"Game Developer ConferenceFrom Reliable to Respected: Breaking Free of the Good Job TrapCecile HemeryGame Developer ConferenceEstablishing the Standards and Practices of Game Preservation"Garrett Fredley, Andrew Borman"Game Developer ConferenceFresh Grad to Art Director: My Journey at 'Love and Deepspace'Xianzi FengGame Developer ConferenceCutscene Pipeline in 'Love and Deepspace'"Xianyu Wang, Ji Zhang"Game Developer Conference1:06:09GDC 2026 - TuesdayGame Education Roundtable Day 1Game Developer ConferencePraise the Architect and Pass the Ammunition: Health & Damage in 'The Outer Wor…Game Developer Conference'Civilization VII': Impactful UI Sound Design at ScaleKadet KuhneGame Developer ConferenceWhy We Still Believe: A Conversation with Amir SatvatAmir SatvatGame Developer ConferenceAlways Supporting (the) Games CommunityAmir Satvat3rd Annual Game Developer's ConcertAustin WintoryGame Developer ConferenceTechnical Artists Roundtable (20th Year)!!! Day 1Jeff HannaGame Developer ConferenceThe Modular and Expressive World Art of 'Keeper'Nick MaksimGame Developer ConferenceLocal Game Community Organizers ForumMarlena Abraham, Michael Lee, Daniel Lin, Laia BeeGame Developer ConferenceTiny ConSociety of PlayBlack in GamingSo Your Game Got Cancelled: Navigating Personal Development and Career OutcomesMark LaCroixGame Developer ConferenceSince we recorded this episode, a major South Korean gaming website wrote up a very detailed recap of Mark's roundtable. [English Machine Translation]MAR10 Day returns with festivities for fans of all ages in honor of the Super M…NintendoWhy Good Games Fail: The Startup Audit Every Studio NeedsLucien ParsonsGame Developer Conference'despelote': Capturing the Feeling of 2001 Quito, EcuadorJulian CorderoGame Developer Conference

John Flake, Professor of chemical engineering and Associate Vice Chancellor of Research at LSU, joins Dave Cohen to discuss the benefits and risks of nuclear power in Louisiana.

In this episode of The New Warehouse Podcast, Kevin chats with Ben Hull, Director of Sales at Item America, about how modular warehouse solutions are reshaping operations. Item America, a German-based company with a growing U.S. presence, specializes in aluminum extrusion systems that allow teams to design and build custom solutions on the shop floor. From ergonomic workstations to AMR-compatible carts, the conversation explores how flexibility, customization, and continuous improvement are driving smarter warehouse design. Hull shares how modular thinking helps operations reduce waste, adapt faster, and create solutions that truly fit their needs.Learn more about sponsors here: EPG, iAutomate, Big Joe Forklifts, Surgere, Ocado Intelligent Automation Follow us on LinkedIn and YouTube.Support the show

This Week in AI sneak peak! If you enjoy the episode find us on Spotify, Apple podcasts and YouTube by looking up "This Week in AI" or by going to thisweekinai.aiThis week Jason sat down with Jake Loosararian and Chris Lattner on Episode 6 of This Week in AI. Jake is the CEO and co-founder of Gecko Robotics, a company deploying purpose-built robots and AI for mission-critical infrastructure inspection across energy, defense, and manufacturing. Chris is the CEO and co-founder of Modular, building a universal software layer that lets developers run AI models across Nvidia, AMD, and Apple silicon without being locked into any single hardware vendor.We explore the GPU shortage, why China's chip smuggling reveals the stakes of the AI cold war, how purpose-built robotics are beating humanoids on ROI, the case for American reindustrialization, and why the next decade could be the best ever for private equity in capital-intensive industries.Purpose-Built Robots vs. Humanoids: Jake has been building mission-critical robots for 13 years. He explains why general-purpose humanoids still have too little ROI for industrial use, and why specialized robots that find and fix problems are winning in the field.The GPU Shortage Is Real: Chris breaks down why you can't just go buy 100 Blackwell chips today, why Nvidia's Cuda creates massive lock-in, and how Modular is building a unified software layer across all major chip architectures.Google TPUs Are the Sleeper: Chris ranks Google as the number one threat to Nvidia's dominance, ahead of Amazon's Trainium and AMD.China's Chip Smuggling & the AI Cold War: A Supermicro co-founder allegedly smuggled $2.5B in Nvidia chips to China using fake serial numbers and a hairdryer. The Best Decade for Private Equity: Jake makes the case that capital-intensive, commoditized infrastructure assets: waste-to-energy, water treatment, old power plants will all generate incredible returns.Self-Driving State of Play: Chris, a former Tesla Autopilot lead, gives his read on Waymo's lead, Tesla's small Austin pilot, and why the real signal is when Tesla starts filing for fully autonomous permits in California.Learn more about Gecko Robotics: https://www.geckorobotics.comLearn more about Modular: https://www.modular.com/This Week In AI is made possible by:*PayPalOpen* - One Platform for all Business: paypalopen.com*Timestamps:*00:00 Welcome & intro to Jake Lu (Gecko Robotics) and Chris Lattner (Modular)01:34 Gecko's 13-year journey & the Cantilever platform05:15 Chris Lattner on Modular: replacing Cuda & unifying AI hardware11:10 Nvidia lock-in, AMD's Rock & why the software stack is broken19:49 The GPU shortage: how real is it?22:13 Who challenges Nvidia? Google TPUs, Amazon Trainium & AMD ranked28:17 China chip smuggling: $2.5B in Nvidia GPUs & the AI cold war37:43 Self-driving update: Waymo, Tesla's Austin pilot & Chris's Tesla history42:20 Figure's humanoid package sorting — real or demo magic?43:47 The best decade for private equity in capital-intensive assets51:04 Reindustrialization, the trades boom & making manufacturing cool58:39 Building tech companies outside Silicon Valley1:06:46 Breaking news: Brett Adcock launches Hark from Figure1:10:15 Closing thoughts: grit over hype, customers over valuationsSubscribe to This Week in AI on Apple: https://thisweekinai.ai/spotifySubscribe to This Week in AI on Spotify: https://thisweekinai.ai/appleThanks for watching!

Timestamps: 0:00 come on, doctor's orders 0:13 Intel Core Ultra 270K Plus, 250K Plus 1:31 Win11 glitches but it'll get better 3:00 National AI Legislative Framework 5:17 QUICK BITS INTRO 5:27 Galaxy S26 series AirDrop support 5:56 GrapheneOS no personal information 6:27 Crunchroll hack 7:02 Modular, indestructible robot NEWS SOURCES: https://lmg.gg/v9Lr2 Learn more about your ad choices. Visit megaphone.fm/adchoices

Building components in a warehouse does not automatically make you a manufacturer. In this episode of Prefab, Unfiltered, recorded live at Advancing Prefabrication, Todd Weyandt sits down with Jon Benson to explore what it truly means to transition from traditional construction to productized manufacturing in modular construction and prefabrication. As industrialized construction matures, the conversation is shifting from “offsite construction” to serialization, guardrails, and repeatable systems. Scaling prefab requires more than space and labor. It requires product discipline, standardized workflows, and the willingness to protect the system. This conversation dives into how modular construction companies can move beyond project-by-project customization and into scalable manufacturing models that protect margin, schedule, and quality. If you are involved in prefabrication, modular construction, industrialized construction, or productized building systems, this episode offers a strategic look at what real manufacturing maturity requires.   You'll Learn The difference between construction in a warehouse and true manufacturing Why serialization and productization are critical to scaling prefab How guardrails protect repeatability and profitability When to say no in order to protect standardization Why buyer maturity influences prefab adoption How product thinking reshapes modular construction strategy   Meet Our Guest Jon Benson brings more than two decades of experience in modular construction and industrialized manufacturing. With a background rooted in OEM and manufacturing environments, he has helped guide the evolution from offsite construction toward serialized, product-based building systems. His perspective centers on discipline, repeatability, and aligning operational capability with market demand to create scalable prefab strategies.   Todd Takes Prefabrication Is Not Manufacturing Until It Is Serialized. True manufacturing requires repeatability, standardization, and product discipline. Without serialization and guardrails, prefabrication remains project-based and difficult to scale. Productization Requires Saying No. Mature prefab operations protect their systems. Not every customization should be accepted. Guardrails preserve margin, schedule, and quality across projects. Buyers Matter as Much as Builders. Scaling modular construction depends on procurement alignment. When owners and contractors understand and commit to standardized systems, prefab can move from one-off solutions to scalable programs.   More Resources  Thanks for listening! Please be sure to leave a rating and/or review and follow up our social accounts. Bridging the Gap Website Bridging the Gap LinkedIn Bridging the Gap Instagram Bridging the Gap YouTube Todd's LinkedIn Jon's LinkedIn TAS Energy's Website   Thank you to our sponsors! Graitec North America Graitec North America LinkedIn Autodesk's Website  

Most mainstream phone options are kind of the same, year in and year out — but that doesn't mean there's no innovation to be found. The Verge's Allison Johnson is at Mobile World Congress, and joins the show to report on all the modular phones, robot phones, small phones, big phones, and (alas) 6G phones set to hit the market this year. After that, The Verge's Jess Weatherbed explains the phenomenon of the gadget strap, and makes the case that they're an increasingly useful accessory as our phones become even more important to our daily lives. (Yes, even if you have pockets.) Finally, The Verge's Jay Peters helps David answer a question from the Vergecast Hotline (call 866-VERGE11 or email vergecast@theverge.com!) about whether the metaverse, however you want to define it, is ever going to be realized. Further reading: Oh great, here comes 6G  Honor claims its Robot Phone will launch later this year  Lenovo made a Franken-laptop with modular ports and a second screen  Vivo's next phone will launch with a professional camera rig  Tecno's latest concept phone is lit by neon  Honor's Magic V6 is the first foldable with an IP69 rating  The Motorola Razr Fold is shaping up to be pure flagship Xiaomi's super-slim power bank costs extra in orange.  Honor's thinnest tablet doesn't come cheap.  Peak Design has wearable gadget straps for people who hate bags  Apple's misunderstood crossbody iPhone strap might be the best I've seen  Meta confirms Reality Labs layoffs and shifts to invest more in wearables Meta's VR metaverse is ditching VR Subscribe to The Verge for unlimited access to theverge.com, subscriber-exclusive newsletters, and our ad-free podcast feed.We love hearing from you! Email your questions and thoughts to vergecast@theverge.com or call us at 866-VERGE11. Learn more about your ad choices. Visit podcastchoices.com/adchoices