POPULARITY
Categories
319 episodes with brief history
406 episodes with brief history
384 episodes with brief history
46 episodes with brief history
158 episodes with brief history
27 episodes with brief history
32 episodes with brief history
35 episodes with brief history
85 episodes with brief history
39 episodes with brief history
49 episodes with brief history
32 episodes with brief history
31 episodes with brief history
18 episodes with brief history
25 episodes with brief history
13 episodes with brief history
12 episodes with brief history
25 episodes with brief history
13 episodes with brief history
49 episodes with brief history
60 episodes with brief history
15 episodes with brief history
41 episodes with brief history
12 episodes with brief history
10 episodes with brief history
14 episodes with brief history
13 episodes with brief history
6 episodes with brief history
8 episodes with brief history
7 episodes with brief history
8 episodes with brief history
29 episodes with brief history
7 episodes with brief history
6 episodes with brief history
7 episodes with brief history
9 episodes with brief history
8 episodes with brief history
6 episodes with brief history
8 episodes with brief history
10 episodes with brief history
29 episodes with brief history
29 episodes with brief history
8 episodes with brief history
8 episodes with brief history
5 episodes with brief history
14 episodes with brief history
4 episodes with brief history
9 episodes with brief history
27 episodes with brief history
7 episodes with brief history
6 episodes with brief history
9 episodes with brief history
10 episodes with brief history
25 episodes with brief history
10 episodes with brief history
7 episodes with brief history
24 episodes with brief history
11 episodes with brief history
8 episodes with brief history
23 episodes with brief history
30 episodes with brief history
9 episodes with brief history
7 episodes with brief history
10 episodes with brief history
8 episodes with brief history
7 episodes with brief history
4 episodes with brief history
5 episodes with brief history
8 episodes with brief history
4 episodes with brief history
7 episodes with brief history
14 episodes with brief history
5 episodes with brief history
8 episodes with brief history
3 episodes with brief history
5 episodes with brief history
9 episodes with brief history
5 episodes with brief history
4 episodes with brief history
4 episodes with brief history
4 episodes with brief history
3 episodes with brief history
6 episodes with brief history
6 episodes with brief history
7 episodes with brief history
4 episodes with brief history
4 episodes with brief history
3 episodes with brief history
4 episodes with brief history
12 episodes with brief history
3 episodes with brief history
7 episodes with brief history
21 episodes with brief history
3 episodes with brief history
3 episodes with brief history
5 episodes with brief history
3 episodes with brief history
4 episodes with brief history
5 episodes with brief history
6 episodes with brief history
5 episodes with brief history
8 episodes with brief history
4 episodes with brief history
4 episodes with brief history
2 episodes with brief history
3 episodes with brief history
3 episodes with brief history
5 episodes with brief history
2 episodes with brief history
7 episodes with brief history
4 episodes with brief history
5 episodes with brief history
5 episodes with brief history
5 episodes with brief history
3 episodes with brief history
3 episodes with brief history
3 episodes with brief history
5 episodes with brief history
4 episodes with brief history
4 episodes with brief history
2 episodes with brief history
3 episodes with brief history
6 episodes with brief history
2 episodes with brief history
3 episodes with brief history
2 episodes with brief history
2 episodes with brief history
3 episodes with brief history
3 episodes with brief history
5 episodes with brief history
4 episodes with brief history
3 episodes with brief history
4 episodes with brief history
4 episodes with brief history
4 episodes with brief history
4 episodes with brief history
2 episodes with brief history
3 episodes with brief history
2 episodes with brief history
5 episodes with brief history
3 episodes with brief history
4 episodes with brief history
3 episodes with brief history
4 episodes with brief history
7 episodes with brief history
4 episodes with brief history
4 episodes with brief history
4 episodes with brief history
2 episodes with brief history
3 episodes with brief history
2 episodes with brief history
2 episodes with brief history
4 episodes with brief history
4 episodes with brief history
2 episodes with brief history
4 episodes with brief history
2 episodes with brief history
4 episodes with brief history
4 episodes with brief history
4 episodes with brief history
2 episodes with brief history
5 episodes with brief history
Dr Adam Koontz and Col Willie Grills talk about Hardboiled Fiction and it's adaption into Noir Film, and its reflection of the culture and the human heart. Visit our website - A Brief History of Power Thanks to our sponsors, Ad Crucem, Memento, and Gnesio Health Dr Adam Koontz - Redeemer Lutheran Church Pr. Willie Grills - Zion Lutheran Church Music thanks to Verny
What did the ancient world discover about the cosmos? What were the contributions of Copernicus, Kepler, and Galileo? How did the science of astronomy advance under Newton? And how did everything change again with the discoveries of special relativity, general relativity, and quantum mechanics? With us to answer these questions is Sarah Alam Malik. SarahĀ is an expert on dark matter, and her work on large-scale experiments such as the Large Hadron Collider has placed her at the cutting edge of exploring the universe's mysteries and its fundamental laws. Today we discuss her new book entitled, A Brief History of the Universe (and our place in it).
Tell me your favorite episode for the 6th anniversary show! For thousands of years, Korea has stood at the crossroads of East Asia, shaped by powerful neighbors but never defined by them.Ā It has been home to ancient kingdoms, Buddhist temples, Confucian scholars, devastating invasions, colonial rule, war, division, and one of the most remarkable economic and cultural transformations in modern history.Ā Despite everything, they find themselves in the 21st century, independent but divided.Ā Learn more about the history of Korea on this episode of Everything Everywhere Daily. Sponsors Saily Get an exclusive 15% discount on Saily data plans! Use code everythingeverywhere at checkout. Download Saily app or go to https://saily.com/everythingeverywhere ButcherBox Get your choice between chicken breast or top sirloin for a year OR ground beef for life, PLUS $20 off when you go toĀ ButcherBox.com/everything Quince Go toĀ quince.com/dailyĀ for 365-day returns, plus free shipping on your order! Mint Mobile Save 50% on Unlimited premium wireless plans starting at $15/month atĀ MintMobile.com/EED TrueWerk Get 15% off your first order at truewerk.com with code everything DripDrop Go to dripdrop.com and use promo code everything for 20% off your first order! Subscribe to the podcast!Ā https://everything-everywhere.com/everything-everywhere-daily-podcast/ -------------------------------- Executive Producer: Charles Daniel Associate Producers: Austin Oetken & Cameron Kieffer Ā Become a supporter on Patreon: https://www.patreon.com/everythingeverywhere Discord Server: https://discord.gg/Ds7Rx7jvPJ Instagram: https://www.instagram.com/everythingeverywhere/ Facebook Group: https://www.facebook.com/groups/everythingeverywheredaily Twitter: https://twitter.com/everywheretrip Website: https://everything-everywhere.com/Ā Disce aliquid novi cotidie Learn more about your ad choices. Visit megaphone.fm/adchoices
Historiansplaining: A historian tells you why everything you know is wrong
No other American colony projected such extensive power with so few people. We recount how the French explored the vast northern region they called āCanadaā for decades in pursuit of furs and the Northwest Passage, but repeatedly failed to plant a lasting colony in the harsh and forbidding landāuntil they found in Samuel de Champlain a leader with the shrewdness and grit to overcome the severe cold, the vast distances, and the treacherous politics of the Saint Lawrence basin. We trace the growth of Quebec from little more than a warehouse in the frozen wildnerness to a thriving town, controlling the most critical gateway into the continent and serving as the hub of a lucrative trading network, a vast constellation of mission towns and outposts (including the Christianizing experiment known as Montreal), and most importantly, a formidable indigenous alliance system that dominated the continenet from the Atlantic to Lake Superior. Finally, we consider the disasters of the mid-1600s, including deadly epidemics and warfare with the Five Nations, that brought Canada's most important allies to their knees and threatened to wipe the colony off the map. Please sign up as a patron to support the podcast! -- https://www.patreon.com/c/u5530632 Previous lecture discussing the history of the Haudenosaunee Confederacy (aka the Iroquois Confederacy or Five Nations): https://historiansplaining.com/individual-episodes/the-hiawatha-belt/ Previous lecture, discussing the dynamics and importance of the fur trade: āHistory of the United States in 100 Objects, no. 24 ā Beaver-Fur Stovepipe Hatā -- https://historiansplaining.com/individual-episodes/beaver-fur-stovepipe-hat/ Previous lecture on the first French colony on the North American mainland, Acadia: https://historiansplaining.com/individual-episodes/acadia-first-foothold-in-the-north/ Image: Engraving depicting the battle of Lake Champlain, July, 1609, published in Samuel de Champlain's āLes Voyages du Sieur de Champlain,ā 1613, based on a drawing by Champlain himself Suggested Further Reading: Riendeau, āA Brief History of Canadaā; David Hackett Fischer, āChamplain's Dream: The European Founding of North Americaā; Moogk, āLa Nouvelle France: The Making of French Canadaā; Linteau, āThe History of Montrealā; Greg Koabel, āThe Nations of Canadaā podcast,
The Year of the Werewolf resumes with a new mini series. Researcher and investigator RyanĀ joins us once again to discuss Otto Skorzeny and the Spider Network in the Emerald Isle. In textbook Ghost Stories style, though, we're taking this first episode to do a little scene setting with a crash course in the history of Ireland: colonial occupation, Irish resistance, the machinations of the British deep state, and the IRA's vexed and uneasy relationship with Germany and, later, NAZIS.Ā Ā SUPPORT THE SHOW HERE: https://www.patreon.com/c/GhostStoriesForTheEnd
A history of Glen Helen in Yellow Springs and also a fabulous art collection.
Dr Adam Koontz talks about how we preach about the law and the errors of legalism and antinomianism. Visit our website - A Brief History of Power Sign up for Memento, a Lutheran devotional for men. Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
In 1964, Israel completed its National Water Carrier, leading the Arab states to worry about the economic growth this would mean for Israel. They understood that water meant agriculture, agriculture meant food security, food security meant Israel could absorb more immigrants, more immigrants meant a larger population, and a larger population meant a stronger army and a state that would be more difficult to dislodge. Syria tried to divert the waters of the Chazbani and Banias rivers away from Israel, but in successive skirmishes Israeli tank crews wreaked havoc on Syrian bulldozers earthmoving equipment and tanks. Eventually, Syria and the other Arab states abandoned the diversion effort. On January 1, 1965 was the first terrorist incursion of a new organization called the PLO. This marked the emergence of a new model of Palestinian nationalismāone that would place armed struggle at its core and would, over time, come to dominate the Palestinian national movement. Credits The War over Water (Survival of a Nation) Jewish Learning Institute 1959-1988 | Who Are The PLO And Fatach? Brief History of the Israeli-Palestinian Conflict āØWho Was Yasser Arafat? The Jewish Nation Who Invented Palestinian Nationalism and Why? | Explained unpkd Learn more at TellerFromJerusalem.com Don't forget to subscribe, like and share! Let all your friends know that that they too can have a new favorite podcast. Ā© 2026 Media Education Trust llc Ā
Marlin Flory and Gerry Rominger join the Journey on its 100 podcast episode to reflect on how far the almond industry has come. About 100 years ago, the California almond industry was just starting to grow with applied irrigation. Flory and Rominger, multi-generational California almond industry members take listeners through a few major advancements in the industry over that time and detail how the industry supports its growth.āIt's fascinating the evolution of the industry, both with machinery and technology. The science has just really changed everything and let it become what it is today.ā - Gerry RomingerIn Today's episode: Hear from almond producer and industry leaders Gerry Rominger and Marlin Flory, respectivelyExplore the evolution of the almond industry in CaliforniaDiscover how these prominent industry members weather the twists and turns and the optimism they maintain through it allThe Almond Journey Podcast is brought to you by the Almond Board of California. This show explores how growers, handlers, and other stakeholders are making things work in their operations to drive the almond industry forward. Host Tim Hammerich visits with leaders throughout the Central Valley of California and beyond who are finding innovative ways to improve their operations, connect with their communities, and advance the almond industry.ABC recognizes the diverse makeup of the California almond industry and values contributions offered by its growers, handlers, and allied industry members. However, the opinions, services and products discussed in existing and future podcast episodes are by no means an endorsement or recommendation from ABC. The Almond Journey podcast is not an appropriate venue to express opinions on national, state, local or industry politics. As a Federal Marketing Order, the Almond Board of California is prohibited from lobbying or advocating on legislative issues, as well as setting field and market prices.
Jeremy dips his toe into the dangerous waters of opinion. And he asserts his own! While keeping doctrine in its place, Jeremy argues that Christians should pursue burial instead of cremation. Ā Do Theology is part of Foundations Media. Learn more at https://foundationsmedia.org Ā https://dotheology.com https://store.dotheology.com https://www.buymeacoffee.com/DoTheology Ā Contact Us: show@dotheology.com https://twitter.com/dotheology https://facebook.com/dotheology Ā Subscribe to the podcast: https://linktr.ee/DoTheology Ā 0:00 Introduction 2:19 Opinions Shared on X 7:04 Jeremy's Opinion 7:57 The Doctrine Chart 10:56 "Fitting" vs. "Sinful" 19:17 A Brief History of Cremation 23:18 Burial Better Reflects Biblical Teaching 31:31 Burial Is Better Stewardship 38:40 Burial Is A Better Witness 47:05 What About Money? 53:30 Conscience Chatter
A whirlwind tour of columns at their most iconic: capital moments, loadābearing drama, and centuries of standing their ground. Rae and Andi lean into Greek bulges, Roman ruleābreaking, and postmodern inside jokes. Hosted on Acast. See acast.com/privacy for more information.
Dr Adam Koontz talks about the predicted trend of increased bi-vocational ministry and what Paul wrote about pastors making their living. Visit our website - A Brief History of Power Thanks to our sponsors, Ad Crucem, Memento, and Gnesio Health Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
Trust in institutions is at a historic low. Turns out there are about sixty years of very good reasons for that.From Watergate and Thatcher decimating mining communities, through the cash for questions scandals of the 1990s, Iran-Contra, the fabricated case for the Iraq War, and a British Post Office scandal that ruined the lives of hundreds of people, this is a brief history of how governments, politicians, businesses, and institutions systematically destroyed the trust of the people they were supposed to serve.We also look at why not all distrust is the same, what manufactured distrust is, and give you examples of people and places that have worked to earn your trust.ā ā ā ā ā ā ā ā ā ā https://www.patreon.com/HistorysGreatestIdiotsā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā https://www.instagram.com/historysgreatestidiotsā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā https://buymeacoffee.com/historysgreatestidiotsā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā Artist: Sarah Cheyā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā https://www.fiverr.com/sarahcheyā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā
Trust in institutions is at a historic low. Turns out there are about sixty years of very good reasons for that.From Watergate and Thatcher decimating mining communities, through the cash for questions scandals of the 1990s, Iran-Contra, the fabricated case for the Iraq War, and a British Post Office scandal that ruined the lives of hundreds of people, this is a brief history of how governments, politicians, businesses, and institutions systematically destroyed the trust of the people they were supposed to serve.We also look at why not all distrust is the same, what manufactured distrust is, and give you examples of people and places that have worked to earn your trust.ā ā ā ā ā ā ā ā ā ā https://www.patreon.com/HistorysGreatestIdiotsā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā https://www.instagram.com/historysgreatestidiotsā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā https://buymeacoffee.com/historysgreatestidiotsā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā Artist: Sarah Cheyā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā https://www.fiverr.com/sarahcheyā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā
Dr Adam Koontz talks about Christian Nationalism and how the debates around it in the church relate to the proclamation of the gospel. Visit our website - A Brief History of Power Sign up for Memento, a Lutheran devotional for men. Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
Boyle is frequently described at the first modern chemist, but his work encompassed much more than that. Among other things, he was a founding member of the Royal Society. Research: Boyle, Robert. āAn account of Philaretus during his Minority.ā Accessed online: https://celt.ucc.ie/published/E650001-100.html Boyle, Robert. āNew experiments physico-mechanicall.ā Oxford. 1660. https://archive.org/details/chepfl-lipr-AXA74/mode/1up?q=proportional Boyle, Robert. āNew experiments physico-mechanical, touching the air.ā London. Richard Davis. 1682. https://quod.lib.umich.edu/e/eebo/A29007.0001.001?rgn=main;view=fulltext Boyle, Robert. āThe Sceptical Chymist.ā London. J. Crooke. 1661. Accessed online: https://www.gutenberg.org/cache/epub/22914/pg22914.txt āCopy of Sir Robert Boyle's Will.ā Brief History of Blue. https://omekas.prattsi.org/s/HistoryofBlue/item/109 āDecember 31, 1691: Death of Robert Boyle.ā This Month in Physics History. APS News. Dec. 1, 2016. https://www.aps.org/apsnews/2016/12/this-month-in-physics-history Henderson, Felicity. āWhat Scientists Want: Robert Boyleās To-do List.ā The Royal Society. August 26, 2010. https://royalsociety.org/blog/2010/08/what-scientists-want-boyle-list/ Highmore, Nathaniel. āThe history of generation. Examining the several opinions of divers authors, especially that of Sir Kenelm Digby, in his Discourse of bodies ...ā 1651. Accessed online: https://wellcomecollection.org/works/kv5tr2uz/items Martin, Christy. āFull Boyle.ā Distillations Magazine. Science History Institute Museum and Library. May 13, 2012. https://www.sciencehistory.org/stories/magazine/full-boyle/ Masson, Flora. āRobert Boyle: A Biography.ā London: Constable & Company Ltd. 1914. Accessed online: https://www.gutenberg.org/cache/epub/73234/pg73234.txt Principe, Lawrence M.. "Robert Boyle". Encyclopedia Britannica, 24 Apr. 2026, https://www.britannica.com/biography/Robert-Boyle āRobert Boyle (1627-1691): Sherborne School library benefactor.ā The Old Shirburnian Society. https://oldshirburnian.org.uk/robert-boyle-1627-1691/ āRobert Boyle: wishlist of a Restoration visionary.ā The Guardian. June 3, 2010. https://www.theguardian.com/science/2010/jun/03/robert-boyle-royal-society-wishlist āThe Royal Society of London.ā National Museum Australia. https://www.nma.gov.au/exhibitions/exploration-and-endeavour/royal-society-london Sweeney, Patricia E. āRobert Boyle.ā Ebsco. 2022. https://www.ebsco.com/research-starters/history/robert-boyle West, John B. āThe Original Presentation of Boyleās Law.ā Journal of Applied Physiology 1999 87:4, 1543-1545. https://journals.physiology.org/doi/full/10.1152/jappl.1999.87.4.1543 See omnystudio.com/listener for privacy information.
I'm excited to work with Microsoft once again as the presenting sponsors of the AI Engineer World's Fair! We'll streaming live from MS Build today for a special crossover pod with our friends at No Priors and the one and only Satya Nadella. However we did not hold back with this interview - we asked all the burning questions about uptime and Copilot that we know you have in your minds. Lets go!For almost two decades, GitHub has been the home of software, where both open source and closed flow, through commits, pull requests, reviews, actions, etc.This ecosystem flourished as open-source maintainers and contributors would continue shipping code for the benefit of the community. However as coding agents began to ship mass quantities of code - growing 1400% in 2026, it marked a new era that was both extremely exciting and challenging for GitHub.While these agents help more people ship more projects, they also significantly increase the floor of how much code is shipped, how often it is shipped, how many people commit code, and basically orders of magnitude multiples in every dimension of GitHub infrastructure:Now GitHub inevitably experiences more pressure on their infrastructure which was originally designed around human developers moving at human speed. This has resulted in a very publicly notable uptime story:So it begs the question of whether current systems around code can absorb what AI produces. Can CI/CD keep up when every idea becomes a build? Can open source maintainers survive floods of AI-generated slop contributions? Can GitHub preserve the human social contract of software while becoming the operating layer for agents?Which brings us to the perfect person to answer these questions: GitHub COO Kyle Daigle. In this episode, he joins swyx to unpack what happens when AI doesn't just autocomplete code, but starts changing how companies operate, how open source works, how pull requests get reviewed, and how GitHub itself has to scale. We go deep on GitHub's internal AI workflows: micro-skills, WorkIQ, MCP, Slack, Teams, email, Copilot workflows, the new Copilot desktop app, CLI, cloud agents, and how Kyle uses agents to look backwards across company context before deciding what to do next. Kyle also reflects on GitHub's history building webhooks, APIs, Actions, npm, Dependabot, and Semmle, why the AI era is breaking GitHub in new ways, how Actions became a general-purpose compute layer, and what Copilot becomes after code completion.Full Video PodWe discuss:* Kyle's expanded role across GitHub* How AI got Kyle coding again after years in leadership* Why GitHub rolls out AI through existing workflows instead of forcing new tools* WorkIQ, MCP, Slack, Teams, email, and GitHub as company context* Why massive āmega-skillsā are giving way to small, atomic micro-skills* How AI changes summarization, communications, marketing, and analyst work* Why former developers in leadership may have a unique advantage in the AI era* Kyle's ā15 agents on Saturdayā workflow* How Kyle built an AI-generated executive presentation for CRO/CFO teams* Why AI changes the chief of staff role without removing the human work* GitHub Actions, webhooks, arbitrary code execution, and secure agent compute* The npm acquisition, supply-chain security, 2FA, and token invalidation* Slop forks, vendoring, and whether AI agents change dependency management* What pull requests become when most PRs come from agents* Prompt requests, vouching, AI review, and trust in open source* What counts as a ādeveloperā when AI lowers the barrier to building* GitHub Spark, low-code, and why GitHub refuses to hide the code* 14x commit growth, Actions load, databases, monorepos, and availability* Copilot's evolution from completion to CLI, desktop app, cloud agents, and SDK* Context, memory, rules, and making GitHub āact like Kyle wants it to actā* Ambient AI, OpenClaw, enterprise security, and the new operating system for agents* What swyx should ask Satya Nadella about Microsoft's AI futureKyle Daigle* LinkedIn: https://www.linkedin.com/in/kyledaigle* X: https://x.com/kdaigleTimestamps00:00:00 Introduction00:03:36 Why AI Got Kyle Coding Again00:07:04 Running GitHub with AI: WorkIQ, MCP, Slack, Teams, and Skills00:15:39 The Golden Age for Former Developers in Leadership00:17:31 15 Agents on Saturday and AI-Generated Executive Work00:20:20 How AI Changes the Chief of Staff Role00:21:45 GitHub's History: Actions, npm, Webhooks, and Open Source00:28:45 Slop Forks, Vendoring, and AI Dependency Management00:33:57 Pull Requests, Prompt Requests, and Trust in Agent-Generated Code00:41:21 GitHub Stars, 200M+ Developers, and the New AI Builder Wave00:45:15 GitHub Spark, Low-Code, and Why GitHub Still Shows the Code00:47:38 GitHub's Hardest Era: 14x Growth, Reliability, and Scale00:59:21 Actions as the Compute Layer for CI/CD and Automation01:02:04 The State and Future of GitHub Copilot01:08:24 Ambient AI, Background Agents, and the Future of the SDLC01:13:09 OpenClaw, Enterprise Security, and the New OS for Agents01:18:03 Build Announcements, WorkIQ, FoundryIQ, and Microsoft Context01:21:41 What Should swyx Ask Satya?TranscriptIntroduction: Kyle Daigle's Expanded Role at GitHub and MicrosoftSwyx [00:00:00]: We're here with Kyle Daigle, COO of GitHub. Welcome.Kyle [00:00:07]: Hey, thanks for having me.Swyx [00:00:08]: You're not just CEO of GitHub. People know you as that. You have a new role.Kyle [00:00:11]: So I have an expanded role now. I've been working at GitHub for thirteen years and doing all things developer. Joined as a developer myself. And now, I'm also responsible as the CMO of Developer for Microsoft. And so all the kind of learnings and passion for developers and how we work with them and how we communicate and how we bring our products to market, we're also bringing that expertise to the broader Microsoft ecosystem and helping every developer that uses a Microsoft product or would like to have a sort of similar experience that they've had with GitHub over the years. So it's a different role in some ways, but it's also just building on the experience that I've had at GitHub of just sort of tell the truth, be authentic, show people how to use it and then let the products speak for themselves. Now just doing that with, all of Microsoft.Swyx [00:01:09]: We'll be releasing this in conjunction with Build. You got lots of stuff planned, and we can sort of touch on that whenever it's appropriate. I think one of the interesting things is I rarely meet a COO who's also a CMO. I think you're a very outward facing and you're very confident publicly. That's rare. Do you actually view yourself as COO? What's What is your thing?From GitHub Developer to COO/CMO: Building the Platform and Operating GitHubKyle [00:01:33]: I think for me, it's been funny. The titles have always been, aā have always felt a little strange to me. I joined GitHub as a developer? I wrote so much of theSwyx [00:01:46]: Let's bring that up. You wrote the back ends?Kyle [00:01:48]: I was going through, I was going through, some old photos, when folks were talking about how things were being built or how there was a build GitHub. I built, webhooks and worked with teams building the API, built the platform layer. Anything that integrated with GitHub, up until really twenty eighteen, I built or ran the engineering teams. And that's kind of where my the beginning of my passion always was helping people build things, deliver them to, their customers. And so being a developer, building for developers was always super unique. In aā I think as my role expanded, it became my ability to talk to not just developers, but also enterprise customers or business leaders and have this translation layer. And then through all those years, GitHub has always operated pretty uniquely. Post-pandemic, working remotely was not as novel as it was when GitHub started in two thousand and eight. But all that expertise of running remote teams, doing it well, became this sort of bigger role, ultimately turning into the COO role of how do we operate GitHub in the way that GitHub's always operated after the Microsoft acquisition. And kind of so on from there. So like for me, I think theā I've, I still code. I love coding but the problem has always been, people. It's a much harder problem to both support our own employees, a harder problem to communicate to developers and enterprise buyers what we're building why it matters, ācause those are two very different messages. And so getting to work in the mix of COO, CMO, also just being a dev, I think is what's kept me at GitHub for so long.AI Workflows for Leadership: Commits, Retrospectives, and ContextSwyx [00:03:40]: Apparently, you haveā your commits have gone up. What's this? What's going on?Kyle [00:03:45]: Rui's called me out pretty aggressively. So I thinkā as you can imagine, right, you can see my normal era of being a dev In the twenty thirteen, twenty fourteen era, and then moving into management, and then ultimately the COO role. I think what you see there is me, really getting back to coding thanks to AI. Iā similar to, attaching problems between how to market and how to operate a business and how to code, I find, building agents and workflows that are connecting very disparate problems to be what's driving this. So that's, some of it's writing software. A lot of it is, connecting a ton of a different data sources to, help me out. But that is completely me really diving in on the AI side in trying out our tools, trying out everyone's tools, But building for me, building for the non-technical leader, though I'm technical and how we're, able to use these tools more than just the simple, call and response that I think a lot of the non-technical, your employers, you have to getā you have to use AI, and so everyone uses, ChatGPT or Copilot or Claude or whatever. To really get into, how is this going to help me out, itā I find that it's not the I need to write a blog post, I need to those simple examples. Helping people find the workflows of, āOkay, I need you to go through all the PRs today. I need you to go through everything that we've posted online. I need you to go through what we did the last three months. Go through all of my Obsidian notes for any mentions of this then go through my transcripts at work.ā We use, Teams, so, using WorkIQ, go call that MCP server, grab all the transcripts, go through all the Slack, and then build me out the plan of, what this week's messaging actually was. That's something that was, impossible because for me, I find AI in a what most of this launch here is actually, less building forward. It's actually, a recursive loop backwards. I'm always looking at what had happened first. Go back through the week and tell me what we did, what worked, what didn't work? And then tell me in the next three or four days-What would you tweak based on this sort of like looking backwards and then looking ahead a little bit? I find that to be so much more valuable, especially for like non-technical, because that retrospection is actually LLMs are very good at that. Like finding all the patterns, pulling them out, and then applying that retrospection to just a couple of days or just like a short period of time. Is all a bunch of apps that I've built and launched a bunch of, internal tools. I use the new, GitHub Copilot app, the desktop app with workflows. Every time I crack open my laptop, it's running workflows for me. It's just a ton of different stuff and of course, it all ends up on, it all ends up on GitHub.Swyx [00:06:47]: Of course. That's where, that's where, stuff is hosted. Man, there's so much to ask you. I was going to leave the how do you run a company with AI thing at the end. I have to ask oneā double click one thing. You said, you are looking back at the week. You're, you're understanding what happens. When you say we That's three thousand people. How?Rolling Out AI Internally: Skills, CLIs, and Company ContextKyle [00:07:09]: I think when we started rolling out AI internally beyond engineering, right? One of the things that I was really, passionate about is like we have to do this in a way where no one has to change how they work. I don't want to have to teach you a tool. I don't want to have to teach you something new. And so for us, we tried out a few tools. Most of them don't work because I got to get you on board? I got to teach you how to use it. What we've actually ended up doing is we've built like a set of skills internally. We have we each have our set of skills, and we've just been distributing even to the non-technical folks, the CLI. And then effectively, we're just giving it access to like read about everything that we're writing. So that's for us, that's usually GitHub, Teams, Email, and Slack. So Teams for, video chat, generally speaking.Swyx [00:08:03]: Teams and Slack?Kyle [00:08:04]: so we use Teams for video communication, but we don't use it for chat. W-weā GitHub for a long history, right? We're alwaysSwyx [00:08:13]: Also SlackKyle [00:08:14]: Talking about ChatOps and like everything is built into Slack. Like every command, every flow.Swyx [00:08:18]: So even though you have been acquired for I don't know, eight years nowKyle [00:08:22]: we stillSwyx [00:08:23]: You still use Slack?Kyle [00:08:23]: it's a purpose-built tool for us, and I think the reality is that moving off of it would be so bluntly expensive? Simply because all the tooling is, baked in with that paradigm. And they both have their pros and cons but they don't work the same way at all. We still use a bunch of different tools Because it's the purpose-built tools that We need. And thenSwyx [00:08:47]: Well, the same doesn't go for the rest of Microsoft, presumably.Kyle [00:08:50]: like the like various teams like operateSwyx [00:08:53]: They make their own decisionsKyle [00:08:54]: Various ways. I think it just matters what you're trying to what you're trying to do. But we do we do work across kind of every tool that we use, and then by giving everyone access to all of that context and the new WorkIQ MCP server, which is quite cool if you do live in the M365 like world. I can ask it all these backwards-facing questions, and it's incredibly important for our teams that are working remotely. There's a lot of stuff you miss when you're not in an office, and we are spread out all over the world. So most of that is looking back. And then we post, we post either auto-automatically into GitHub issues or discussions, these sorts of like findings or like our industry reports. Like what's happening this morning, today, yesterday. A little automation gets run. We'll use the app. We might use GitHub Actions like with, our agentic workflows just to go do that run, and then we push it into GitHub, and w-we keep having a conversation. So usually for us, it's about that sort of like looking back, looking forward on the non-technical side. And then of course for a lot of those folks, it's also building an app, pushing it to GitHub pages or pushing it somewhere to host it et cetera. But it's just like enabling everyone with that power of it's going to take me a week to figure this out. Instead, we're going āOkay I built a skill. Let's put it into a repo. We'll all share that skill together, and then we'll use the CLI or now the app-ā ājust to run it.āMicro Skills vs. Mega Skills: How GitHub Uses AI at WorkSwyx [00:10:26]: All right. I think, I think we're going straight into like the team management and productivity thing. I think a lot of people are getting various levels of LLM psychosis. How do you manage the bloat of skills? Like everyone Has their thing, and they're Like trying to promote it to the rest of their peers in their org, right? And obviously, whoever becomes a skill influencer internally becomes like an AI leader, right? Of sorts. I assume you have those.Kyle [00:10:50]: like I think we haveSwyx [00:10:52]: And I assume it's a mess a Yeah.Kyle [00:10:54]: there's like Iā like I think the reality is there's two pieces. Like first is I think that we're ending the era of these like massive, beautiful, perfect skills that are just like not any of those things. ācause for a while, right every tweet every day is like go download the skills, the perfectly managed thing to do this entire workflow. And I think that like what we've found and whatā I was just with my team, this week, and we were talking about the skill side, and we're really talking about these like incredibly micro skills that are just doing one thing for us very well Versus a skill that's going to do I said, that full report. That doesn't really exist on our side anymore. It's usually how doā like a single skill that's going to identify the most important marketing information given any MCP server. Like this is the most important thing. Less about stitch a bunch of tools together and have it produce this mega output because then weeks go by, months go by, things change, and you want to tweakSwyx [00:11:58]: It's brittleKyle [00:11:58]: Your mega skill and you're screwed? You can't do that. And so now we're really just talking about the Legos we're using and just letting the instruction book be something we're all putting together. Whereas I think a lot of AI skills for a while have been that mega instruction book style.Swyx [00:12:15]: I've, thought a lot about Postel's law. I don't know if that's a term that is, means things to folks. It's the idea that you should be liberal in what you accept and strict in what you output, right? And I think that's like a good framing principle for skills. This is my skills, obviously on GitHub. I feel like everyone should have like how like some repos In GitHub are special repos? I feel like we should sort of reify the slash skills and everyone like give it some kind of special presentation. Anyway, so, yeah, this is one of those like download Download anything, transcribe anything, and then you can string together the atomic skills that do one thing well Into like some kind of orchestration skill that calls other skills. I assume, does that match?Kyle [00:12:56]: I like I think so. I think that theSwyx [00:13:00]: Summarize anything.Kyle [00:13:01]: Like I think the- For me, summarizing something for I do communications and PR and analyst relations and marketing and customer activities, and so my summarize everything is very different for each one of those like Contexts. What āCause if I'm summarizing something for an analyst, that's a very different thing than, probably how I'm going to summarize something for like a customer meeting or an engagement. So that's I think like the difference when we're talking about the like the tools I might use on Saturday or the skills I might use on a Saturday when it's just for Kyle. Yeah, those are kind of like they have an atomic actual tool underneath or maybe skill, and then Kyle cares about X. But I think when we're talking about work and enabling the the marketers, communicators there, it's the atomic, this is what good summarization is, and then this is what I care about as for marketing for communications For whatever. And that I think is like the interesting matrix problem when we go from like a developer set of concerns to all kinds of different professions, is that what that word means to me is different than it means to you is different than it means to the analyst or the salesperson, and that's where I think the matrix mess is that we're starting to like still starting to find. It's about these mega skills but they're all just slight permutations, but those permutations are really important. It's the difference between someone reading this and going āDid AI make this?ā what Or āThis makes total sense, and I would expect this when I'm giving a briefing to Gartner,ā or like whatever else.Swyx [00:14:37]: I think the beauty of it maybe is that you don't have to be that careful about what goes in there. It doesn't have to exactly fit as long as it like roughly is contained in there. I used to complain about plugin hell, basically. Like when you have a framework and then you have a hundred things that you need to integrate, everyone does like the GitHub used to be bloated full of these things. And now we don't need them anymore ācause now you just use skills.Former Developers in Leadership: AI as a Creation MultiplierKyle [00:15:00]: And like I think the most magical thing is the just that like I can just also crack it open. Like Like yes, I could go like change the how the plugin is coded, or like I could go do that now with AI, but I think there's just something more magical about getting a response back and being āThat's not right,ā and then you just crack the skill open, you just type English words and it's different. That building block is just, I think very unique. Once I get everyone to kind of understand how to best how to best make those changes to get the most power out of them.Swyx [00:15:36]: Is there aā you have a your peer group that Of people like you. Is there a common framing for Something I'm feeling is, which is true, is that is this a golden age for former developers who are now in leadership? Because you can wield the tools, you would know the right words, you're maybe not too close to the details. Doesn't matter. But like you're more effective than someone who doesn't come from that background.Kyle [00:15:59]: I think that like the secret has always been your ability to identify patterns and solve problems, and I think that for folks that like myself that don't code day to day anymore, that has made me successful as a developer, made me successful as a COO and now CMO. And so now that I have access to get and write code, I'm now applying that sort of like pattern finding and problem solving, and I know enough still about how to then go and say, āOh, I want to make an app, but I don't want to break into jail or create something that's not going to be able to work or to be deployed scale or whatever.ā that ability to apply all that additional business knowledge and still code I think is what makes that so interesting to me. Slightly different than I think some of the other like technical leaders that became business leaders and now are going back to their apps and updating them. Good for them? But I think the more, much more interesting thing is, well, now I have this whole new set of expertise over ten plus years. Why not take that and use that as a developer with these AI tools? So I definitely think that makes me more powerful, but I think that's true for like every dev as well. Most of the dev friends I still have also have some other underlying skill and passion. There's really talented, very kind of linear computer science software devs, absolutely. I just find that the folks that came from a different career, went to school for something else, went off and did this random thing, and then became a software dev, or were a dev, did a random thing, came back. Learning that extra set of information, learning those extra skills, and now having the power of an AI where I can crank up fifteen agents on Saturday while my kids are doing lacrosse, That's like really powerful. And I think it gets me back to that feeling of like creation, and it's very hard to replicate that in most other senses? That first time you build an app and you click it and you show someone that's magical. And so being able to do that not just in code, but across all kinds of different assets that's, that's huge. We were doing we're doing our every year we do our revenue planning. We talk about okay, what is it going to look like for next year? And of course as you imagine, there's, slideshows everywhere talking about what are we going to talk about, what's the narrative, et cetera. And so as you said I'm āOkay, well, I could probably just like build something to build this and then that way I don't have to go build the whole spreadsheet or I have to pass it to my team.ā So we went through this process, and I got all the information and used the skills I mentioned. I built like a little app just to make it so I could look at some of the information in a SQLite database, more easily. And I ultimately built this entire presentation without touching any of it and I was āOkay, I'm just going to present this to our CRO, the CFO, their teams,ā without mentioning I'd built it with AI. I like built a skill to make it look very much not AI driven. Just not pretty.AI-Generated Presentations, Human Taste, and the Changing Chief of Staff RoleSwyx [00:19:03]: Like a design. Yeah.Kyle [00:19:03]: Not pretty. But just like very clearly not AI. Kind of like don't do anything interesting.Swyx [00:19:08]: That's, yeah, that is valuable.Kyle [00:19:08]: Just go Exactly. We did the whole thing through. It used my notes from Obsidian, it used all the context I mentioned before, the plans, and Never came up once that it was AI generated.Swyx [00:19:20]: It didn't matter.Kyle [00:19:20]: Never once. D It didn't matter. And so now I takeSwyx [00:19:23]: This is a toolKyle [00:19:23]: I can take that tool and go, āLook, I don't want you to go build slideshows.ā They're just helping us share information with each other. If this thing can do it With a little bit of crafting from you and then we can look at it together, awesome. There's no value in all that extra work. I think that the ability to, make it look humanly bad and and build a little app to, manipulate the data I think is part of, that upside for devs that are now in leadership roles. Because, the thing that I feel like I said before, this that's all a people, that's all a people problem. I know if you've used a coworker or not to build a slide deck, unless you spent a bunch of time to not do it.Swyx [00:20:07]: I know, but like it was so, I think there's a certain charm to just being blatantly AI. āCause I think that you're well, you're just honest about There may be mistakes here that I cannot vouch for. So how much value is there? But anyway I think, actually the real question I want to ask is, there's aā You were a chief of staff To Thomas. And in the pre-AI world, the that job would've been a chief of staff job of like Can you prep me these slides and all that? And now you do it yourself.Kyle [00:20:35]: I still, I still have a chief of staff. Because, the difference is it's sort of the discussion every time we have some sort of technology evolution is it's not that the jobs the roles don't all go away, they just change? And so yeah, I don't have someone spending all their time building out slides for me and presentations ācause I don't need that anymore. But now I need that person that is able to go and find all the different connections between humans in those discussions to help me find out, okay, I should be meeting with this group and this team, and they have an opportunity, and I'm going to be in San Francisco today, I'm going to be in Seattle tomorrow. Those sorts of human connection aspects are still incredibly valuable and has always been a big part of that chief of staff role. But now just like chiefs of staff are not opening up, letters to process, they're doing emails. What It's the same thing. And now they're, they're not building out as many of these presentations because they have the the ability to have a AI take it on for, and share that with me and great. Let's keep moving ācause it's allowing us to go faster and make better decisions more quickly.Swyx [00:21:45]: Awesome. Well, so we can dive into more sort of, Productivity insights as you go. I did want to do a little bit of a brief history of colleague and hub. Because, we started here. And then you also involved the NPM acquisition. I did, I do want to touch upon that. And then more recently, I just want to bring up to present day where we're having uptime issues Which transparently we've already Addressed publicly, but we'll, we'll discuss in the pod. Did I miss anything? Like what, any other major highlights? Obviously, it's, it's a lot of years to cover.A Brief History of GitHub: Webhooks, Actions, Acquisitions, and Platform EvolutionKyle [00:22:15]: No the I think one of one highlight was right before the acquisition closed in twenty eighteen, I got to launch the first version of ActionsSwyx [00:22:27]: OhKyle [00:22:27]: At GitHub Universe. So it was OSwyx [00:22:29]: They're that young?Kyle [00:22:30]: It was October of twenty eighteen, I think. Yeah. Yeah.Swyx [00:22:33]: Gee, Jesus.Kyle [00:22:34]: I got to I was the engineering leader on that project and got to launch that. And then, yeah, we did acquisitions of NPM you said, Semmle, Dependabot Pul Panda a whole bunch of things. That was a bigSwyx [00:22:47]: Pul Panda.Kyle [00:22:48]: Abi is doing well.Swyx [00:22:51]: DX. Holy crap.Kyle [00:22:52]: Did well on DX. I and like that was a that was the big shift, after the acquisition. I had to join the sort of business side.Swyx [00:23:00]: So I need to hit you on some of these things ācause you were there. Right? And how often do I get to talk to someone who was there? But yeah, Actions. Is that the number one source of security issues on GitHub?Kyle [00:23:11]: Oh, sh I think that the number one source of, security issues is probably like all, the literal code in everyone's like underlying repositories. I would say back further than that is, if you remember I had to show in this graph was this is, I'm, didn't say this before, this is ultimately webhooks.Swyx [00:23:30]: You yeah.Kyle [00:23:31]: Like circa whatever it was.Swyx [00:23:32]: It says Hookshot in there.Kyle [00:23:32]: I forget. Yeah. Yeah, Hookshot's in there. And so like back then, it says GitHub Services. Do you see, it says Hookshot FE for front end, and then it says GitHub Services. GitHub Services back in the old days, right? You we had a repository that was Ruby code, and you could write any Ruby code in there, and then we would execute that On your behalf As a service, and then that way if an if you were trying to integrate with something, it didn't we would run it for you.Swyx [00:23:57]: And of course no containers ācauseKyle [00:23:58]: No, ācause it wasSwyx [00:23:59]: Well, no containersKyle [00:24:00]: Twenty fourteen. And so there was some isolation obviously, but it was mostly the separations on the server level. That's like an example as long as the very old version of Pages, which ran on its own containerization infrastructure, not on Actions.Swyx [00:24:15]: Which like all-time great product.Kyle [00:24:16]: Pages powers the internet at this point to some degree. Those were places where like clearly there were no like issues like to my knowledge. But it was those things where I'm looking at and going āOkay, well we can't be running arbitrary Ruby code,ā like on everyone's behalf. Then containerizing all of that up intoUh into actions now where yeah the containerization, is r-really good. The pinning most folks aren't pinning it the like to a particularSwyx [00:24:48]: ImagesKyle [00:24:48]: Sha, et cetera like their workflows, and so that's a big that's a big place Of pain for folks if they're just doing similar to any dependency management, just V1 or newest or latest, I think. But, that journey from that day to āOkay, we're just going to run all this arbitrary code, and, it'll basically be okay,ā to now, no, we have, really good containerization. We have a new, underlying, ag-agent, containerization, service. It's like we're using it under the hood. It's through Azure. They recently announced it. The Azure, Dev Compute, but it's, very fast, very fast compute to be able to, spin up your own cloud agents, or whatnot. We're using it under the hood for some parts of the new,Swyx [00:25:36]: Microsoft Dev Box?Kyle [00:25:37]: No. Dev Compute, yeah.Swyx [00:25:41]: Hmm. Not finding it just yet.Kyle [00:25:44]: Oh, it's, it's in there somewhere.Swyx [00:25:46]: All right. Well, we'll cut that out.Kyle [00:25:47]: Sorry. But with, Dev Compute, you can, run, really fast, spin up really, small VMs really quickly, so you're doing a tool callSwyx [00:25:58]: Same conceptKyle [00:25:58]: Just do it containerize exact-exactly. So we're using that so definitely moving that direction to protect us from every every piece of code that we're ultimately running.Swyx [00:26:07]: look, that grows into the full SDLC? Code hosting was just the start and and then it's grown beyond that. Let's talk about NPM may-maybe ācause I think that's also, a very major point in the industry. I do think, it was looking for a home. It was, kind of struggling as a business, right? I don't know, I don't know how you would characterize that whole acquisition and how itNPM, Package Security, and Keeping the Internet RunningKyle [00:26:33]: like when we were talking to the team, I think the big thing for the both of us was to find a way to keep NPM, which was basically powering the internet then and way more so now to some degree running. Keep it going keep continuing to scale. It was having scaling problems, if I recall, back at that time. They were doing some rewrites. ItSwyx [00:27:00]: that's cute compared to now.Kyle [00:27:01]: Well, that's the thing is like when I'm talking to folks now, there's there's so many more underlying uses of NPM than there were back when we had them join in with GitHub. But that was ultimately the goal. It was really okay, we used to have pages. We have, the world's code. Let's make sure that we can keep NPM running well for the world. And we put a bunch of time and investment into fixing some of the underlying backend, changes, some of which we talked about some of the manifest work, et cetera. And then now, really trying to bring the the security posture of NPM up to speed. But, it is a unique challenge in that every move that we make to make it more secure will break a lot of people. And security is paramount. And also, we take it very seriously. We're, the any time that we have a problem with GitHub or we make a change that makes us more secure but hurts, there's, a snow day for developers or a really bad fire that they have to go put out. And so we've, have changed the 2FA policies. We've changed the way the tokens work. When we find tokens that have been exposed or potentially, exposed, we invalidate them, andSwyx [00:28:22]: I love that feature in GitHub. Yeah, it's greatKyle [00:28:23]: That creates issues, but, the but that's the thing is we're trying to push the community, forward without necessarily, doing something that is going to break the contract that's been for 15 years or close to it or some amount of years on NPM.Slop Forks, Vendoring, and the Future of Open Source Supply ChainsSwyx [00:28:43]: I think theā So now we're talking about, open source and publishing. And I think there's something here with what people are calling slop forks, which, I think Malta from Vercel is doing. And, part of me thinks, well, the way to get past any vulnerabilities, we just, let's just get rid of the concept of NPM. And we only publish source code. And anytime you want to import it you have your coding agent look at it and then adapt whatever subset you're going to use into your vendor it. But, the AI vendor it. Is that realistic? I don't know. Is itā Will that solve all our security issues? I don't know.Kyle [00:29:24]: I don't think it'll solve I so Mitchell was just talking Mitchell Hashimoto Was just talking about this today, and I think that I-in some ways, it's all all things, old or new again? Yeah, absolutely vendoring everything. Like I do I do remember twenty thirteen, twenty fourteen.Swyx [00:29:42]: This is Yeah. Let's, we must return toKyle [00:29:43]: That's what is We were vendoring everything. We were having actual discussions around, or at least I remember we were āShould we take this full thing?ā āWhy is this so big? We only need this one file.ā And so I do think there's something true there where having either taking only what you need or the dependencies just getting incredibly small over time, I think will help to some degree, but it's not going to solve the fundamental problem, I don't think, because the vulnerabilities in an agent looking at them, there's time and time again, there's a million different ways in which we can convince an agent that this thing is, secure or not and pull it in. Or we can do static code analysis or runtime testing to say whether the code works or not. That is, I think, the step that needs to continue to be, invested in. The question is just on, how much scope. Should it be this enormous project that I'm pulling down, or should it be this piece? Either most companies are running some amount of security checking on the on the packages that they're bringing in or vendoring. That I think won't change. That's like what advanced security does to some degree, Socket does some degree. Like everyone is doing a piece of that. How we each do that like especially when we're talking to enterprise customers, is just like very different. No there's no one wants one single way to do it. And I think that's always been GitHub's, unique position in the world. I talk a lot to maintainers, I talk a lot to folks about this. It's we'reā we rarely start like a process and a practice and like push it onto the community. We usually wait for the sort of like RFC process socially or literally, everyone agreeing, and then we'll cement something in. Because otherwise we'reMaintainers, RFCs, Vouching, and the Social Layer of TrustSwyx [00:31:35]: That fits your role in the ecosystem, yeahKyle [00:31:36]: We're GitHub. Yeah, we don't want to shape the whole thing. We want it to be figured out. But like how do you balance that like sort of Role in the industry to keep everything as secure as is possible and make sure that you're you're not going to be compromised as a human, ācause that's usually how it all happens. And Not not create a process or lock us into a flow that you're not going to or like Mitchell's not going to or other open source projects aren't going to like. That's always been a tricky balance for us, and I think that's something that we haven't talked about enough is we're not going to be able to fix everything for everyone in a way that everyone is going to like. So tell, help us, tell us what is working. When Mitchell was talking about, the Upvote, the upSwyx [00:32:22]: I was going to bring up his thing. Yeah.Kyle [00:32:23]: I forget what it Yeah. When he's talking to us, I was chatting with him and talking to him about this and I put it on Twitter and we talked to, also over DM, was āWe're going to keep working.ā but I think the important thing is I do actually want to hear what isn't working for you. And as, be as specific and clear for your project as is possible. And to every piece of credit over the many years that we've known each other through the industry, he's always done that and I appreciate that ācause there are places that we need to fix up, and we hear from him, and we'll fix up just like we do all other kinds of maintainers. But that that process between making those types of improvements and being more secure and like creating, I forget what he calls it's not the proof process, not the claims process. Do what I'm talking about? He has that he his projects have a way for you to kind of like,Swyx [00:33:13]: VouchKyle [00:33:13]: Vouch. Thank you. Yeah. He has like the vouch system for saying, āHey, you should accept my PRs.ā That's beenSwyx [00:33:20]: I just built this into GitHub. I don't know.Kyle [00:33:22]: Well, see, but that's the thing is that you say that and like he and his community really likes this and then I'll go talk to other maintainers and other maintainers, globally, and they're āNo, this doesn't work for me.ā And that is the tension, but also the kind of beauty of GitHub, depending on which way you look at it is we want to help maintainers, so we create all these tools to let you have more control over how much you take in from AI and PRs. But you can also use this. What You can go use this project, and if it takes off and becomes the kind of mostly standard, then yeah, we probably wouldn't enforce it but we would add it in because that's the flow that we tend to do?Swyx [00:34:02]: I hear a lot of people don't know the history of the pull request. And like like that's how, that's something that GitHub standardized basically.Kyle [00:34:08]: Yeah. It was a very messy process Like beforehand, and now the we have the benefit of it being the process? And now we have to go and Figure out the next best process or what adaptations change, or what does a pull request look like when eighty percent of your PRs are just coming from your agents and not From other devs?Swyx [00:34:31]: Do you like the prompt request idea from Peter?Kyle [00:34:34]: like I think that for each like each idea I think has its merits. I'm not, I'm not avoiding saying anything good or bad, but I feel like I've seen a version of we have that we have entire Thomas' store. Take all the assets of what you've built and put that in. I think that's got great ideas. There's all these various permutations of the PR flow, but I think the reason why there's not a single answer is ultimately we're trying to codify trust. We're trying to say āOkay, if Sean reviews this I'm going to trust it because you're Sean or you're the senior dev or you're the whatever.ā And right now, when we are working in a flow where an agent writes code and another agent reviews code and then Kyle goes and looks at it the trust is kind of diffuse. And most of the tools that we're talking about are talking more about verification flows. We have more assets to look at, so I can probably say whether this is a good PR or not. But that still doesn't solve, I think, the human problem of I'm looking at a PR and I want to know if I can trust it. And we're still, we still tend to use human signals for that? Mitchell approving it or Kyle approving it or whatever. And so I think that's, I think that's why most of these options haven't really solved it is because, it's a social problem ultimately. It's a it's a human problem to review it and agree. Or you fully trust the tool and you're imbuing that tool with full trust Which I think in some cases that absolutely exists.AI-Generated PRs, Trust, and the Waymo AnalogySwyx [00:36:08]: And so like in the same way that there will be a tipping point in society when we don't allow humans to drive anymore Because machines are measurably better than Than humans. I'm looking for that tipping point, right? Like Mythos is ridiculously expensive. Someday we'll have Mythos on a desktop. I don't know. Will, does that change the equation?Kyle [00:36:30]: I think it's more I took a Waymo here, and I was on my phone and not looking around at all. There are other, self-driving, vehicles that I would not trust while, staring at the road. And I think that trust is something that isSwyx [00:36:48]: Is this a Zoox thing? What is itKyle [00:36:50]: I think that is both. I think that is both. LikeSwyx [00:36:53]: There's Zoox in this robo taxi. That's it. It'sKyle [00:36:56]: Well, depending on what level Of self-driving. But, my point is sort of that I think part of that is I strongly believe that's, a mixture of verifiable proof. Like how many accidents, how much data, and so on, and the human aspect of how I feel when I'm in this car, what it tells me, et cetera. And so that's why I think some of the like Some of these some of our AI tools tend to, imbue me with more of that feeling of trust, even if the data says this is 100% accurate. I feel like it takes more time for us to go, āShould I trust this or not?ā And that's in the soft sense of, startups with high agency, weekend projects, and open source. And then there's enterprises and regulated industries and everything else, and that is an even harder problem to go solve because even when it is fully verified, not only do you have to have trust from the humans on the team, you probably have to have trust from multinational,Swyx [00:37:55]: Oh my GodKyle [00:37:55]: Multi governments around the world and regulating agencies. And so that's where I feel like until we tip over to your point on the sort of like human EQ side of it. I feel okay this feels okay I've been proven enough. Then the ball will start to roll a lot faster, where we'll end up getting to the āOkay, we can trust this,ā and feel good about it in the Most difficult of cases.Reputation, Sponsors, Stars, and Bot Activity on GitHubSwyx [00:38:18]: If human trust is the thing that matters, I feel like GitHub as the developer social network could maybe do more there. Like vouchers are one system But, we have star counts, and then we have Contributor rights, and that's it. And I feel like there should be more in that space. I don't know if there's any other design decisions there.Kyle [00:38:37]: I think that one of the places that we don't really expose right now in this sort of way is, some degree of like hard trust and support, which would like for me is like sponsors is a good example of that.Swyx [00:38:49]: Ah.Kyle [00:38:49]: It like costs you something. To prove that I believe in your project and I trust you To some degree or I want to support you at the very least.Swyx [00:38:56]: Solve payments for open source. Why not?Kyle [00:38:58]: I think that I think that like as we keep moving forward, right, there's more and more projects where I'm, adding more and more dollars into sponsors personally because I want to like support them, but I also like know of I've probably never met them in person, but, I know of enough of their work that I want to support them. I think the thing that I don't love about stars or commit counts or anything else is ultimately, even with all of the various, abuse and de-spamming and deduplication work that we do or anti-abuse work that we do, these are all, not active social signals. They're passive ones that are ultimately gamifiable. And you may trust me, but another open source maintainer may not. And on what heuristic should you be, trusting me? That I think, is kind of where some of our thinking is right now. What signal from me is most important to you? Youā If you can define that potentially, honestly in an agentic workflow that's what we see some of these open source projects do, where you have GitHub actions, and then you have like an agentic workflow that's calling AI, and you're setting these rules. Like if Kyle has submitted and gotten accepted PRs across any given project and has a social handle tied to his account in GitHub, and that social account's older than a certain amount. Really complex measures that matter to you ācause most open source projects have that heuristic built into their heads, if not written down in the contributing guidelines. You could take that and then go apply that and then just say, āOh, we're not going to accept this PR.ā Building something that is, I think, malleable to everyone's needs, is a little bit better, rather than going āHmm, this account's too young.ā Because what happens? The attackers just go and go and create a multitude of accounts, and they wait Until it ages up. Needs to have a certain amount of stars. That's how star inflation happens. Need to have a certain amount of reposSwyx [00:40:46]: Oh my God. YeahKyle [00:40:47]: With PRs. They all just create repos and submit PRs to each other, and then they come in and do something nefarious. And so, it's hard. It's hard to find the measure. So I think we're, we're looking more at how can we provide you tools so you can kind of choose what's best for you. And of course, we'll give you some standards. But the trust vector, gets down to I don't know, some version of like human digital ID like everyone's been talking about. Like how do I prove that it's meSwyx [00:41:13]: Give me your eyeballsKyle [00:41:14]: On the internet. Give me your eyeballs. Exactly.Swyx [00:41:18]: The I got to keep moving on Topics, but obviously I can go all day on this stuff because, I've been involved in GitHub and open source My entire professional career. Stars. Very superficial. Everyone knows it. But I think time to one hundred thousand stars is the fastest I've ever seen. Like people just reached that in I don't know, months. And then like at the same time I don't trust it right? Like how many of these are real or bot or like whatever. I don't know how to ask this but like what can we do about it? LikeKyle [00:41:49]: JustSwyx [00:41:49]: Is stars broken? Is stars fine?Kyle [00:41:51]: I think that there's kind of two, there's like two pieces. Obviously we're constantly like trying to find ways in which like your users are producing spam, which would, I would include like be like only doing star gamification. When we find them, we pluck āem out and we,Swyx [00:42:08]: But it's like a Whac-A-MoleKyle [00:42:10]: It's a hundred percent like a Whac-A-MoleSwyx [00:42:11]: There's no wayKyle [00:42:11]: Now, powered by AI to be helpful. But I think more so what I'm seeing is, a lot of the like fastest time to X tends to be because we're now inviting so many more people into like software development on GitHub That like the zeitgeist is just swarming? And it'sSwyx [00:42:32]: It's not just developers anymoreKyle [00:42:33]: And it's not you and I. Like like however you want to say like what a developer is it's not just folks who have been coding for a very long time. It's folks that have maybe started coding or only joined in since the AI era. And nowSwyx [00:42:44]: what's the latest Octoverse number? I know eighty million was my lastRem- member that a number of developers on GitHubKyle [00:42:50]: Oh, we're over 200 million now.Swyx [00:42:53]: Okay. Well, so you see?Kyle [00:42:55]: Like over 200 million developers now.Swyx [00:42:56]: But it's not developers, right? It's, it's people with a GitHub account.What Counts as a Developer in the AI Era?Kyle [00:43:00]: So, so this is, this is the biggest debate that I would say, everyone loves to have at GitHub at this point. From my perspective, right, I think that there's, there's clearly a difference between, professional enterprise developer and then developers. But I think that I think that the idea that we should be I don't know, splitting hairs or segmenting developers in the early era of software development is, not worth our not worth the time. SoSwyx [00:43:29]: When you get into gatekeepingKyle [00:43:31]: 100%Swyx [00:43:31]: What is a developer?Kyle [00:43:31]: 100%. āCause I wasn't a developer when I started writing code? I was going toSwyx [00:43:36]: Oh, no. I madeā I cloned a thing, seven years before I learned to code. And then I and then I wrote about my learning to code journey, and people Just called me a fraud ācause I had a GitHub account. And I'm āWell, no, I just use GitHub, but I don't know-ā āI didn't know what I was doing.āKyle [00:43:49]: I I remember that. I remember those sets of posts, and like that's, that's b******t. So I fight very clearly on the line of, if you create code, if you have an idea and you create it into some way of, I'm, I'm going to run it and use the app right now, you may still use AI in that moment, but that's okay. At some point you're going to do the next thing. You're going to create a bigā You're going to have to learn about this database. You're going to fix a bug, whatever. We're all on some same journey, and those people are also hearing about the great new agent skill package or a new CLI tool or a new whatever. And those projects are going up because you want to be a part of this moment, just like I wanted to be a part of the Ruby community when Ruby was popping off when I started becoming a developer, and now I can just click the star button. And so I think that yes, there's clearly some amount of like spamming and game gamification that we're working against, but I really think we're just seeing this whole new cohort of folks that are moving from technology to technology because they're not working on a 20-year-old software application. They're working on a side app that they built on the weekend for their friends or for their new idea or whatever. And that's how you see these enormous charts going up and to the right with With stars.Swyx [00:44:59]: I think something that's remarkable is the persistence or, that GitHub extends to those folks. Usually when I see platforms go into a new audience, they usually have to, have like a second platform with a different name that wraps the main platform. But somehow GitHub has been able to sort of persist and extend, and it's friendly and whatever? So it's, it's nice.Spark, Low-Code, and Always Showing the CodeKyle [00:45:19]: I that's partially why I think as we've tried to move into I don't know, more like low-code-y things. We so we started working on Spark as like a way to, build an app and run it. I think that the reality is that we anytime we try to, kind of put even a veneer on top of it without when we put a veneer on top of something, we still always show you the code. That's kind of like a tenant. We're never going to, hide the code from you ever, because whatSwyx [00:45:52]: Why would you?Kyle [00:45:52]: That's, yeah, that's the whole point? However, I think that what we learned with things like Spark is that really the value of Spark for most devs is, easy runtime. And you may have a runtime or a host that you're going to use for that or you just build something and run it but, the package of making that even more simple isn't really needed for folks that are trying to build software and not just trying to build, an app, which is, slightly different, a slightly different goal. So I want to get you in, I want to get you comfortable. I think the best thing for me as, someone that did not traditionally come into software dev way back, I want anyone to be able to breach that chasm and not be in the I don't know, I feel like we're, we're still in an era of, STEM. I've got a 12-year-old and an eight-year-old, and it's āWe got to get āem into STEM,ā? Over and over. And I like I do, I do the things that good parents do. I was āOh, you want to do coding?ā āYes, I want to do coding.ā Do coding classes. But now they're just not afraid of doing software. And that's, I think, the thing that's honestly kept me at GitHub for so long. Anyone should be able to go and build a thing, just like I can go change a light switch in my house. I'm not going to go into the breaker box ācause I'll probably kill myself? But, I can go change that light switch. Everyone should be able to go and say, āThis fricking app doesn't do what I want. I want it to work like this.ā And that I think, is what's kind of kept us all connected with GitHub through the years and some and during the easiest of times or in the hard times because of that opportunity of, we're the home for all developers, and we want everyone to be able to have that feeling that we've had of, had an idea, I created it and holy s**t here it is.Swyx [00:47:37]: Here it is. All right, I'm going to try to do more spicy questions.GitHub's Hardest Scaling Moment: Growth, Agents, and UptimeKyle [00:47:42]: Great.Swyx [00:47:42]: Is it an easy time now or a hard time?Kyle [00:47:45]: Oh at GitHub? It's a hard time. Like, it's a hard time and also, I was just with my team and I said, āThis is also, the best and most exciting time that I think I can remember at GitHub.ā BecauseSwyx [00:47:57]: Best of times, worst of times. It's never oneKyle [00:47:59]: ācause we've we were talking about Octoverse reports and, usually we do an Octoverse report once a year, and we look at the numbers, and we say, āOh my goodness.ā I was at Universe in October saying, āThis was the fastest year of growth that we've ever had,ā right? And now we're doing more in a month than we did in a year last year.Swyx [00:48:20]: You're talking about PRs.Kyle [00:48:21]: Commits.Swyx [00:48:21]: Commits, yeah.Kyle [00:48:22]: PRs. Kind of like you name it by roughly every measure that we're looking at, there's some amount of sort of growth that is much bigger, and that is breaking our system in new ways, not old ways. Like webhooks were always notoriously, unreliable over the years?Swyx [00:48:38]: Whose fault is that?Kyle [00:48:39]: not anymore mine, but for a period of time, I'm sure you could pull up a tweet that was āIt was me. I'm sorry.ā but, now, that got rewritten at a scale level that is still working and is not having problems today. Now what we're finding isn't just the isn't the-The simple stuff that folks are on the sometimes on Twitter or on the internet are āHey, why is this like this?ā Sure. There's absolutely silly problems that we shouldn't exist. But now we're talking about, unique, novel permission problems that happen only at a scale across all different objects or whatever, that now we have to go rewrite this underlying system. And so it's, there are problems that yeah, caught us off guard, which I think I said. Like the growth is astronomical, but also we're making such material progress in that I'm excited once we're once we've kind of like reimagined the underlying foundation layer, or pieces of it at least, what's going to be possible when it's not just all of us and all the new people that are being developers and all of their agents and all the tools like working together. Because that'll still happen in that in that GitHub tool, that GitHub community. But it's a it's a hard day anytime we can't give you what you're looking for. We have the same problem internally. We operate through github. Com. Of course, we have backups when things go down and whatnot for our own operations but we feel it too. If it's not working it's not working for us, and that's kind of like the promise of dogfooding for GitHub. It's always been true. We're using the same tool you're using. We're not using a super secret version. We and so we also need it to be great for us for our customers of course for open source. And now an exponential growth of agents, Doing it too.Swyx [00:50:32]: I wanted to load for audio listeners who maybe haven't seen your tweets, whatever. So one billion commits in twenty-five. Now it's two hundred and seventy-five million per week on pace for fourteen billion this year, if growth remains linear. Is that still the pace? I don't know. It's been aKyle [00:50:48]: it's, it's speedingSwyx [00:50:50]: Roughly.Kyle [00:50:50]: It's still speeding up.Swyx [00:50:51]: It's, it's April, so yeah.Kyle [00:50:51]: Exactly. This was in April.Swyx [00:50:53]: All right. So basically you have fourteen x growth, right? Year on year on year. And I think that's a scaling issue. I think, I'm going to like try to really steel man this thing. People have experienced fourteen x growth. They haven't had your downtime. And that's likeā C-can we go dig into that? Why? Like what's theā what broke? What are we doing to fix it? Like just anything for the community to reassure them.Why GitHub Reliability Is Breaking in New WaysKyle [00:51:18]: so there's a Like I was saying, there's a couple different places that we've seen the growth issues. Some of the growth issues, which is why we're tā I was talking about pushing hard on more CPUs is in actions in particular. More tools, more agents, more PRs mean more builds, more builds mean more CPUs. And so we are expanding through not just our data center, but obviously we were talking about moving to Azure and moving to, adding an additional cloud compute because we simply need more CPUs. Not as much GPUs. We definitely need GPUs too, but now CPUs are becoming a factor.Swyx [00:51:53]: It's very CPU heavy.Kyle [00:51:54]: Underneath the hood when it comes to some of the underlying services, we've been breaking up over the years our database infrastructure, so that way we have, more cognitive separation between our the various services. The place that we continue to have pain is in, permissioning. And so right now m-many of our permissioning layers sit into a database that we like internally call MySQL One, and old Hubbers will know what I'm talking about. And so we've been pulling things out of MySQL One for many years, because like and we use we use Vitess and we use other technologies to shard and we do it as one bigSwyx [00:52:31]: Famous thing, PlanetScale was born from this andKyle [00:52:32]: A hundred percent. Sam Old Hubber and friend. And so finding these opportunities to like break this out and then do that globally. The other thing that I think is interesting and both a unique opportunity and tricky is we also run everything I just talked about in a black box container with GitHub Enterprise Server for people that work on-prem. So we take everything I just said, and we also do it on-prem, and we also do all of that and we do it in a data residence setup for customers that need to have their data in a single location. Each of these has the unique characteristic around how we're sort of storing that data in MySQL or in a permissioning setup. That's where some of these outages have oc-occurred, where you're seeing it more like across the board rather than just like the one pieceSwyx [00:53:17]: Filling the databaseKyle [00:53:17]: Isn't quite working. Exactly. And so part of it is that. I think there's been some other places where agents are much more or more projects appear to be moving towards monorepo versus we were going the other direction for many years in the industry. Repos were smaller, but there were more of them, and now we're seeing the opposite. Repos are bigger, and there's, not fewer of them per se ācause there's new growth, but, we're just seeing many more big repos. Big repos, big monorepos have always had, a unique performance problem. Because each one, is slightly different if, particularly if the underlying blobs are incredibly big Inside the repos. And so we've done a ton of work that you proā like most people haven't probably experienced, unless you're in this case of the monorepo. But that Git, infrastructure layer improvement does help the overall, system because, many of the improvements that make monorepos work better make all repo infrastructure work better. And so, I could kind of keep going down the line where it's another thing where we're moving out of, We're changing how we do j I'll just say job queuing for lack of a better, explanation changing the underlying technologies there.Swyx [00:54:32]: I spent two years being a job queuing guy, so.Kyle [00:54:34]: And so it's kind of a little bit of a little bit of piece by piece, and it's mostly because as we wereā as it was built, we built everything in a way that assumed, I guess in some ways that the size of the pipe of work was going to remain the same. There's just going to be more people coming through each of those pipes. But instead now in places whereA git push was, generally a certain size for example, is now, no longer true.Swyx [00:55:03]: Oh, yeah.Kyle [00:55:03]: OrSwyx [00:55:05]: I push a thousandKyle [00:55:06]: On the average. 100%Swyx [00:55:06]: A thousand line commits like dailyKyle [00:55:07]: Same thing with PRs. Like PRs same thing. And like we've talked about optimizing that and making changes where, and there were technology choices that did not work there? And it got slow, and it didn't It was not fast. It did not do what the users wanted. And so we've been reeling that all out and going āOkay, that's just not right. Let's stop putting good money after bad and do it the do it the right way or the right way now.ā So there's It's a it's a lot of things, not quite when I've experienced scale at GitHub historically, it's almost always two options that we've used. We go vertical scaling, particularly with databases, right? And we go horizontal scaling. Oh, we just have more people using this service. Great. We're going to add more servers, and we rack them in our data center, or we use it in a cloud. And now we're sort of in a like diagonal, where like vertical doesn't really work anymore. Horizontal isn't work either because we're all We all have some CPU or GPU constraints in the world now, and now we have to go in and like crack open services that have been running for 10 or 15 years and go, āOkay, the rules of this service have legitimately changed, and now we have to rewrite them.ā None of this is an excuse. This is like we're We have to do the work. We have to make it better.Swyx [00:56:22]: actually as an infra guy, I'm āThis is like one of the most fascinating scaling challenges I've ever seen.āKyle [00:56:26]: That's that's, that's the thing that's the thing that it's hard for Like when we weren't talking about it publicly, and I was like I came out, and I was āHey, I just want to explain what's going on.ā Part of it comes from a very old GitHub ethos, which is it's our it's our uptime. It's down. W What I know you're a developer, so you're, you're inclined to want to understand more what's going on. But at the same time us going āHey, this service didn't, perform the way we expected, and now we have to go change it,ā we weren't We're not trying to hide anything from you i
Rhythm takes the spot light. James Brown HITS the ONE and music history is altered. The butterfly effect in full swing, birthing hip-hop decades later.In this pod and this Wednesday's companion Substack post, we trace funk's lineage through the drum breaks that built breakdance, to the samples that got paid once and borrowed forever, and the artists still keeping it funky!For 30% off your first year with DistroKid to share your music with the world click ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā DistroKid.com/vip/lovemusicmoreā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā
Aman Verjee has had one of the more unusual careers in finance. He started on Wall Street at Lehman Brothers, joined PayPal in its earliest days and worked alongside Peter Thiel and Elon Musk, and eventually became a venture capitalist in Silicon Valley. Along the way he developed an obsession with the history of finance, which led to his upcoming book, A Brief History of Financial Bubbles. He joined Coleman to talk about what the biggest bubbles of the last 500 years have in common, what they reveal about the societies that produced them, and what actually caused the 2008 crisis. Then they look at the questions that everyone is asking: Is AI a bubble, and how will it end? Learn more about your ad choices. Visit megaphone.fm/adchoices
Dr Adam Koontz and Col Willie Grills answer listener questions about the translation of the Bible into Japanese, linguistic idiosyncrasies, and doctrine and practice. Visit our website - A Brief History of Power Thanks to our sponsors, Ad Crucem, Memento, and Gnesio Health Dr Adam Koontz - Redeemer Lutheran Church Pr. Willie Grills - Zion Lutheran Church Music thanks to Verny
Going Back to Smallville returns with our Smallville season 8 rewatch of āInjustice,ā an episode that pushes the show into some surprisingly dark territory while introducing Tess Mercer's version of the Injustice League with Plastique, Parasite, Livewire, and Neutron. We talk about Clark struggling with what to do about Davis/Doomsday, Oliver becoming more ruthless, and Chloe getting pulled deeper into the chaos as the season races toward the finale. More than anything, this episode feels like a major turning point for Tess, because by the end of it, it really seems like she officially knows Clark's secret and believes she's helping him fulfill his destiny. Between the DC references, the growing tension between Clark and Oliver, and the Kandor tease at the end, āInjusticeā gave us a lot to unpack.Support the show: https://patreon.com/hopefullyawesomeBecome a Member on Youtube: https://www.youtube.com/channel/UCHRvjz_pKP1Th5Y8ZIwFMtQ/joinCheck out our Merch! - https://hopefullyawesome.creator-spring.com/This video is NOT sponsored. Some product links are affiliate links which means if you buy something we'll receive a small commission.Mail to:Matt & Maggie - PO Box 3924, Kingsport TN, 37664, United StatesMatt & Maggie - 1001 N Eastman Road # 3924, Kingsport TN, 37664, United States
In this solo episode of the Anglotopia Podcast, Jonathan Thomas delivers his definitive guide to Oxford ā his favorite city in England outside of London and the subject of his guidebook 101 Oxford Travel Tips and Tricks. From the bleary-eyed chaos of his first visit in 2012 with an angry 16-month-old and the Mini Cooper factory ring road at midnight, to two stays as a student on the Oxford Experience program, Jonathan brings nearly 15 years of personal history with the city to bear on a comprehensive, enthusiastic, and practically useful travel guide. The episode covers how to get there, how long to stay, the Oxford Experience immersive student program, the colleges you must see, the Bodleian Library's remarkable layers, the essential museums, the unrivaled bookstore scene led by Blackwell's and its famous five-mile Norrington Room, Oxford's extraordinary literary connections from Lewis Carroll to Tolkien to Philip Pullman, the day trips that demand your time ā including Blenheim Palace and the Cotswolds ā and the practical tips that will make your visit infinitely more enjoyable. Links 101 Oxford Travel Tips and Tricks by Jonathan Thomas ā [Anglotopia Store link] Oxford Experience at Christchurch English-Speaking Union Oxford Course Bodleian Library Tours ā bodleian.ox.ac.uk Blackwell's Bookshop Oxford ā blackwells.co.uk Oxford University Press Bookshop Scriptum, Turl Street Ashmolean Museum ā ashmolean.org Pitt Rivers Museum ā prm.ox.ac.uk Blenheim Palace ā blenheimpalace.com Rousham House & Garden ā rousham.org Didcot Railway Centre ā didcotrailwaycentre.org.uk Oxford Walking Tours Morse Walking Tour Oxford The Randolph Hotel (now Graduate Oxford) Friends of Anglotopia ā Takeaways Oxford is Jonathan's favourite city in England outside London ā and most Americans either skip it or see it in a rushed half-day bus tour that barely scratches the surface. Two days minimum is the right call; three is better. Oxford is just 60 miles and 40-45 minutes by direct train from London Paddington, making it one of the easiest day trips or overnights in Britain ā and you can also get there direct by bus from Heathrow without going into London at all. The Oxford Experience ā a residential immersive programme at Christchurch offering one-week courses for adults in July and August ā is Jonathan's single highest recommendation for anyone who wants to truly inhabit the city. Courses cost Ā£1,500āĀ£2,000 all-in and include room, board, lectures, and excursions; book in November when the schedule is released as popular courses fill within hours. The Bodleian Library is not one library but several ā the Divinity School, Duke Humphrey's Library, the Radcliffe Camera, and the Weston Library ā and the best way to see them properly is to book a guided tour well in advance, as they sell out. Blackwell's bookshop on Broad Street is arguably the greatest bookshop in the world ā the underground Norrington Room alone has five miles of shelving beneath Trinity College ā and Jonathan has never left without spending several hundred pounds. Staff will package books in brown paper and ship them back to the US at reasonable rates. Oxford's literary connections are extraordinary: Lewis Carroll wrote Alice in Wonderland at Christchurch (Alice was the Dean's daughter); Tolkien and C.S. Lewis met with the Inklings at the Eagle and Child every Tuesday through the 1930s and 40s; Philip Pullman set His Dark Materials here; Oscar Wilde studied at Magdalen; and Inspector Morse has made every corner of the city feel like a crime scene. The Eagle and Child ā the Inklings' famous pub on St. Giles' Street ā has been closed since COVID and is currently being refurbished by new owners. It must reopen as a pub by heritage law, and is expected to reopen either in 2026 or 2027; keep an eye on the show notes link for updates. If you're in Oxford for even one day, you must go to Blenheim Palace ā just eight miles away by bus, the only non-royal non-episcopal palace in England, birthplace of Winston Churchill, UNESCO World Heritage Site, and arguably the greatest country house in Britain. A bus from Oxford drops you at the gates. Jonathan's top Oxford hack: stay for at least one night. By 4-5pm the tour buses are gone, Oxford becomes a completely different city, and the cultural life ā theatre, bookshop talks, music ā begins. Arrive early to beat crowds at the sights, then save the evenings for culture and quieter exploration. Avoid mid-April to mid-June (exam season, colleges restrict access), avoid July if you run hot (medieval stone buildings have no air conditioning and bake in the heat), and buy a fan the moment you arrive if visiting in summer. September and October are ideal months to visit. ā Soundbites "Most of my early memories of Oxford were driving the ring road at midnight with a toddler who would not go to sleep and who would only stop crying if he was in the car. We drove round and around, seeing nothing other than the Mini Cooper plant every time we went past." ā Jonathan on his first trip to Oxford in 2012. "Oxford has this warmth to it ā that yellow beige Cotswold stone, weathered and warm. And there's this scholarly, bookish vibe from the place that you don't really get anywhere else. It's not just a campus. Oxford University is the town of Oxford." ā Jonathan on why Oxford grabs you. "I was immediately spellbound. I loved it immediately. And that's the thing about Oxford ā it grabs you once you visit, and you're walking around this beautiful architecture surrounded by deep, deep history. They don't even know exactly how old the university is. It's over 800 years old. When Oxford was founded, the Aztec Empire hadn't even reached its peak." ā Jonathan on falling in love with Oxford in 2016. "There were riots. There was full scale urban warfare in Oxford in 1355 ā the St. Scholastica's Day riot. 63 scholars and 30 townspeople were killed. As a result, the town was forced to pay annual reparations to the university in a formal ceremony that continued into the Victorian era." ā Jonathan on Oxford's violent town vs. gown history. "You basically get to live as an Oxford student for a week. Morning is lectures, afternoon is tours and excursions, evening is formal dinner in the Great Hall. And one night you're invited to high table ā suit and tie, port, mingling with the professors. It's a very quintessentially British experience." ā Jonathan on the Oxford Experience programme. "I've never gotten out of the Norrington Room without spending several hundred pounds. Let me just say that. Five miles of shelving underground beneath Trinity College. So many books." ā Jonathan on Blackwell's legendary underground bookshop. "The Pitt Rivers Museum is like the Victorian cabinet of curiosities. Dimly lit, quiet ā maybe people don't even know it's there. Polynesian canoes, samurai outfits, weapons, armour. A strange and wonderful melange of human culture from all over the world." ā Jonathan on one of Oxford's most atmospheric museums. "If you're in Oxford and you don't go to Blenheim Palace, you've wasted a trip to Oxford. It's the only non-royal, non-episcopal palace in England. I would argue it's probably the greatest house in Britain. And a bus from Oxford drops you right at the gates." ā Jonathan on Blenheim Palace. "By four or five o'clock in the afternoon, the tour buses are gone. And it's just you and the people who live and work and study in Oxford. Oxford becomes a completely different place. That's when the cultural life wakes up." ā Jonathan's key Oxford overnight hack. "Scriptum on Turl Street ā if you're a bookish type, you will love this place. Beautiful blank books, journals, diaries, fancy pens. I have a beautiful leather book from there with gorgeous cream pages that I cherish so much I haven't written anything in it. I'm afraid to ruin it." ā Jonathan on his favourite hidden gem shop in Oxford. ā Chapters 00:00 Introduction ā Jonathan sets up the Oxford guide episode and plugs his Oxford guidebook 01:48 Jonathan's Relationship with Oxford ā Brideshead Revisited, American universities, and the Oxford DNA in US campus culture 03:30 First Visit: Oxford 2012 ā Diamond Jubilee trip, an angry toddler, and the ring road at midnight 06:20 Second Visit: Oxford 2016 ā The train from Paddington, the proper day, and falling in love properly 08:42 A Brief History of Oxford ā Ford of the Oxen, Alfred the Great, Henry II, 800 years, and the St. Scholastica's Day riot 13:30 The University Explained ā 44 colleges, town vs. gown, the founding of Cambridge by Oxford exiles, and Oxford today 16:10 How to Get There ā Train from Paddington, Oxford Tube bus, direct from Heathrow, and why not to drive 19:30 Getting Around Oxford ā Walking, taxis, park-and-ride pitfalls, and Tolkien's grave 21:10 Day Trip vs. Overnight ā Why staying beats leaving, and how Oxford transforms after 4pm 23:40 The Oxford Experience Programme ā Christchurch, Worcester College, the Nelson course, high table, and the Enigma course Jonathan wants to do next 33:15 Accommodation Options ā Hotels, staying in colleges out of term time, and the Randolph (Inspector Morse's pub) 35:20 The College System Explained ā 44 semi-independent colleges, how to apply, porters, scouts, and visiting hours 38:00 Must-See Colleges ā Christchurch, Magdalen, Worcester, Merton, Wadham (Brideshead), and the peculiar All Souls 43:00 The Bodleian Library ā Five buildings, Duke Humphrey's Library, the Radcliffe Camera, the Divinity School, and why you must book a tour 47:00 Radcliffe Square & St. Mary's Church Tower ā The most beautiful urban space in Britain and the best views in Oxford 48:40 The Ashmolean Museum ā Britain's first public museum, the Alfred Jewel, Guy Fawkes's lantern, Turner paintings, and it's free 51:00 The Pitt Rivers Museum ā Through the Natural History Museum, the shrunken heads, Polynesian canoes, and the Victorian cabinet of curiosities 53:00 Carfax Tower, Oxford Castle & Prison, and the Covered Market ā Views, ruins, Brown's CafĆ©, and Ben's Cookies 55:30 The Botanic Garden & Broad Street ā Riverside walks, the Martyrs' Cross, and the Reformation in Oxford 56:30 Shopping in Oxford ā The High Street, Blackwell's, the Norrington Room, OUP Bookshop, Scriptum, The Last Bookshop, and why to skip the Harry Potter tat 01:03:00 Literary Oxford ā Lewis Carroll, Tolkien, C.S. Lewis, Oscar Wilde, Philip Pullman, Inspector Morse, and the Eagle and Child update 01:09:00 Harry Potter Oxford ā Divinity School, Duke Humphrey's Library, Bodleian courtyard, Christchurch Great Hall, and the new TV series 01:12:00 Day Trips from Oxford ā Blenheim Palace, the Cotswolds, Stratford-upon-Avon, Rousham House, Didcot Railway Centre, and Bicester Village 01:18:00 Practical Tips ā Book ahead, avoid exam season, avoid July heat, arrive early, save museums for the afternoon, walk everywhere, punt the river, visit Scriptum 01:24:00 Wrap-Up ā Oxford rewards time and attention; two days minimum, the Oxford Experience if you can, and a call for listeners to share what they love about Oxford Video Version
Dr Adam Koontz talks about the two primary ways of bringing people into the church and the supposed conflict between them. Visit our website - A Brief History of Power Sign up for Memento, a Lutheran devotional for men. Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
Col Willie Grills shares stories of the circuit riders of yesteryear and talks about bringing the word of God even where it is difficult. Visit our website - A Brief History of Power Thanks to our sponsors, Ad Crucem, Memento, and Gnesio Health Pr. Willie Grills - Zion Lutheran Church Music thanks to Verny
Ryan and Lola give you a brief and terribly biased USA and UK perspective of the recent history of body piercing aftercare products. We'll start with medicine cabinet antiseptics and the ways they can irritate a healing piercing, then move on to the 90's which introduced us to a new generation of irritating chemicals. We'll eventually get to sea salt solutions and then sterile saline spray, which is where I think many of us are today. If you're interested in learning more about chamfer needles and how they can be used to pierce cartilage Ryan has a new video on that very subject at www.patreon.com/ryanpba. Find out more at https://piercing-wizard-podcast.pinecast.co
Your outrage is worth a fortune. Just not to you.From a 3,800-year-old complaint tablet in ancient Mesopotamia to cancel culture, Tommy Robinson and Donald Trump, this is the full history of outrage: who manufactures it, who profits from it, and who is laughing all the way to the bank.We cover Roman emperors, the medieval pillory, the tabloid press, Jon Ronson's "So You've Been Publicly Shamed," the small boats panic (with the actual statistics), and why the richest 1% own more wealth than the bottom 95% of humanity, partly because they're very good at keeping you looking the other way.ā ā ā ā ā ā ā ā https://www.patreon.com/HistorysGreatestIdiotsā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā https://www.instagram.com/historysgreatestidiotsā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā https://buymeacoffee.com/historysgreatestidiotsā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā Artist: Sarah Cheyā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā https://www.fiverr.com/sarahcheyā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā ā
Weekend Edition for May 23-24, 2026 Show Notes: Germany / Switzerland - Study TourĀ Support 1517 Podcast Network 1517 Podcasts 1517 on YouTube 1517 Podcast Network on Apple Podcasts 1517 Events Schedule 1517 Academy - Free Theological Education What's New from 1517: By Water and the Word by Brian Thomas: https://shop.1517.org/products/9781967920013-by-water-and-the-word?srsltid=AfmBOopBUXbtbkYK0o6UHbWQm8_6UA7hG6B4RXYSeMxos6wbtbxX3Hnk Being Family by Dr. Scott Keith https://shop.1517.org/products/9781964419961-being-family?srsltid=AfmBOooZqqK-X8KqD64jZn1qUUrqiRwO-l3S4Z_WtIcfayMLAlTyHgoN A Reasoned Defense of the Faith by Adam Francisco https://shop.1517.org/collections/coming-soon/products/9781964419879-a-reasoned-defense-of-the-faith Stretched: A Study for Lent and the Entire Christian Life by Dr. Christopher Richmann https://shop.1517.org/products/9781964419381-stretched The Essential Nestingen: Essays on Preaching, Catechism, and the Reformation https://shop.1517.org/products/9781964419121-the-essential-nestingen More from the hosts: Dan van Voorhis SHOW TRANSCRIPTS are available: https://www.1517.org/podcasts/the-christian-history-almanac CONTACT: CHA@1517.org SUBSCRIBE: Apple Podcasts Spotify Stitcher Overcast Google Play FOLLOW US: Facebook Twitter Audio production by Christopher Gillespie (outerrimterritories.com).
Jon Buck's Sermon on 1 Corinthians 15:23-26, from May 10, 2026.
Jon Buck's Sermon on 1 Corinthians 15:23-26, from May 10, 2026.
Dr Adam Koontz answers a listener question about LCMS internal conflicts and why the structure of synodical polity isn't designed for the people who now comprise it. Visit our website - A Brief History of Power Sign up for Memento, a Lutheran devotional for men. Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
Dr Adam Koontz talks with Dr Dylan Thompson about the beauty and complexity of creation, how modern medicine thinks it can control nature, and modern science parallels alchemy. Check out Dr Thompson's book from Ad Crucem Visit our website - A Brief History of Power Thanks to our sponsors, Ad Crucem, Memento, and Gnesio Health Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
Shamelessly promoting our new paid sister channel, Professor Kozlowski Lecture Notes, where you can find our discussions of V for Vendetta, Watchmen, Sandman, and all the rest of our forthcoming research into "A Brief History of British Magick" and beyond.You can also listen along by joining the Patreon - paid patrons get access to all Notes recordings without paying for each lecture individually. It's a BARGAIN!
Henry Augustin Beers, native of Buffalo, NY and professor of English at Yale, with the help of John Fletcher Hurst (1834-1903), Methodist bishop and first Chancellor of American University, has written a sweeping thousand 900 year history of English literature, up to the end of the 19th century. Although at times biased and sometimes misguided (as when he dismisses Mark Twain as a humorist noteworthy in his time but not for the ages), his research is sound and his criticism is interesting and quite often very balanced. In addition, the last chapter of each part is Hurst's synopsis of religious and theological literature in the language. This book is interesting for its point of view, but also useful as a jumping-off point for those interested in reading the classics. (Summary by Kalynda)Genre(s):Ā History, Literary CriticismLanguage:Ā EnglishKeyword(s):Ā American LiteratureĀ (38),Ā English literatureĀ (36), history of literature (1), Beers: English literature (1), beers (1)
A Brief History of English and American Literature (Pt.1)Henry Augustin Beers, native of Buffalo, NY and professor of English at Yale, with the help of John Fletcher Hurst (1834-1903), Methodist bishop and first Chancellor of American University, has written a sweeping thousand 900 year history of English literature, up to the end of the 19th century. Although at times biased and sometimes misguided (as when he dismisses Mark Twain as a humorist noteworthy in his time but not for the ages), his research is sound and his criticism is interesting and quite often very balanced. In addition, the last chapter of each part is Hurst's synopsis of religious and theological literature in the language. This book is interesting for its point of view, but also useful as a jumping-off point for those interested in reading the classics. (Summary by Kalynda)Genre(s):Ā History, Literary CriticismLanguage:Ā EnglishKeyword(s):Ā American LiteratureĀ (38),Ā English literatureĀ (36), history of literature (1), Beers: English literature (1), beers (1)
Charlie Ungemach of Gird Up Ministries continues talking with Dr Adam Koontz about the polarization of politics, the need to proclaim the whole word of God, and how to talk to people who have no reference for Christianity. Watch the full episode Visit our website - A Brief History of Power Sign up for Memento, a Lutheran devotional for men. Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
Dr Adam Koontz and Col Willie Grills talk about why depression is such a common problem among pastors, why modern medical practice struggles to cure it, and the application of the Gospel to depression. Visit our website - A Brief History of Power Thanks to our sponsors, Ad Crucem, Memento, and Gnesio Health Dr Adam Koontz - Redeemer Lutheran Church Pr. Willie Grills - Zion Lutheran Church Music thanks to Verny
Key Topics Covered Finding and holding onto your core "Why" in the nursing profession. The unique challenges and immense emotional rewards of pediatric emergency nursing. A brief look back at the history and evolution of Nurses Month and Nurses Week. Hilarious and heartwarming memories of hospital appreciation efforts, from expired skincare baskets to unit spirit weeks. The profound importance of mental health breaks, massage chairs, and unit camaraderie to keep our cups full. Chapters [00:00] Welcome to Episode 110 & Happy Nurses Month! [01:06] Meet Jess and Sam: Pediatric ER Travel Nurses [03:57] Jess's Why: Being a Glimpse of Light on the Worst Days [07:27] Sam's Why: Nurturing Spirits and Healing with Little Things [11:19] A Brief History of Nurses Week and Nurses Month [12:42] The Good, the Bad, and the Expired: Nurses Week Memories [16:05] Fostering Joy: Spirit Weeks, Costumes, and Camaraderie [20:07] Focusing on Mental Health and Relaxation at Work [24:44] AMN Healthcare Month Giveaways and Wrap-up Resources Mentioned Learn more about AMN Healthcare and find your next travel assignment: AMN Healthcare Follow along for giveaways, prizes, and community updates on Instagram: @amnnurse (DM the code "AMN Cares" for special prizes!) Join the Nursing Uncharted Community! We want you to feel empowered and optimistic in your travel nursing journey! If you loved this episode, please share it with a fellow nurse who could use a smile and a warm reminder of their "why." Subscribe to Nursing Uncharted on your favorite podcast platform so you never miss a conversation. Connect With UsIf you enjoyed this episode, please share it with a friend and subscribe to our show on your favorite podcast platform. You can also find show updates and nursing opportunities on our Instagram at @AMNnurse. About AnnAnn King, a seasoned travel nurse with a remarkable 14-year track record, has dedicated the past 13+ years to specializing in Neonatal ICU. Ann has been traveling with AMN Healthcare for 5+ years, enriching her expertise with diverse experiences. Currently residing in San Diego, Ann not only thrives in her nursing career but also serves as the host of the Nursing Uncharted podcast, where she shares invaluable insights and stories from the world of nursing. Connect with Ann on Instagram: @annifer05 Are you interested in coming on as a guest? Send us a message at podcasts@amnhealthcare.com Episode Sponsor:We're proudly sponsored by AMN Healthcare, the leader in healthcare staffing and workforce solutions. Explore their services at AMN Healthcare. Discover job opportunities and manage your assignments with ease using AMN Passport. Download the AMN Passport App today! Do you know a nurse looking to get into travel? Refer a friend to AMN today! Learn more about AMN Healthcare's Employee Assistance Program. Join Our Other Nursing Communities: YouTubeInstagramApple PodcastsSpotifyLinkedInFacebookPowered by AMN Healthcare Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
When Science Meets Politics: What Happened to the Dietary Guidelines? Ā The Dietary Guidelines for Americans are based on scientific review, but the final recommendations do not always align with the Advisory Committee's report. Ā In this episode, explore where and why those differences occur. From saturated fat language to alcohol guidance and cultural considerations, this discussion breaks down how science is translated into policy and what that means for public health messaging. Ā Read More: When Science Meets Politics: What Happened to the Advisory Committee's Recommendations Ā Read the whole series, starting with part 1: A Brief History of the Dietary Guidelines (1980ā2025): What Has Stayed the Same? Ā Listen to prior episodes:Ā Ā How the Dietary Guidelines Are Made and Why That Process Matters Ā What āModerationā Really Means for Alcohol and Your Health Ā The 2025ā2030 Dietary Guidelines: What They Got Right and Where They Fall Short A Brief History of the Dietary Guidelines (1980ā2025): What Has Stayed the Same? Ā What Changed in the Dietary Guidelines and Why It Matters
Charlie Ungemach of Gird Up Ministries talks with Dr Adam Koontz about putting political loyalties for the ChristianĀ in their right place, and how culture and media affects generational differences. Watch the full episode Visit our website - A Brief History of Power Sign up for Memento, a Lutheran devotional for men. Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
Dr Adam Koontz and Col Willie Grills talk about pastors taking calls and moving across the country, how to know when to leave for another church, and LCMS congregational culture and leadership. Visit our website - A Brief History of Power Thanks to our sponsors, Ad Crucem, Memento, and Gnesio Health Dr Adam Koontz - Redeemer Lutheran Church Pr. Willie Grills - Zion Lutheran Church Music thanks to Verny
Nope. Yep. Nope. Yep. Everybody got choices? Chipotle didn't just sell burritos - they rebuilt trust with two or three words and some really clear visuals. No freezers. No can openers. No microwaves. Just a brand that went back to its roots and dared to say one thing loudly instead of everything at once. In this episode, we dig into what B2B marketers can learn from Chipotle's "For Real" campaign with our special guest Alicia diVittorio, Head of Global Corporate Marketing at Silverfort. Together, we unpack why "confusion equals no sale," what it really means to take a competitive stand without being obvious about it, and why the best copy - like "Microwaves Not Welcome" - has a point of view that nobody else can own. About our guest, Alicia diVittorio Alicia diVittorio is Head of Global Corporate Marketing at Silverfort, where she oversees brand, communications, PR, analyst relations, and content marketing including web and social. With a background in both brand and comms, she brings a rare perspective on the intersection of provocative positioning and human storytelling in B2B marketing. What B2B Marketers Can Learn From Chipotle's "For Real" Campaign: Go back to your roots - that's why they fell in love with you. Chipotle didn't invent a new brand. They reminded people of the one they already had. Alicia's takeaway for B2B: "Sometimes you really have to remind yourselves of your core value and make sure that comes to the top. That's why people fell in love with you in the first place." Before you evolve your messaging, ask whether you've drifted from the thing that made you matter. You get one message. Use it. Chipotle's campaign works because it says one thing ā real ingredients - and doesn't look back. Ian's biggest takeaway says it plainly: "You get to tell people one thing at a time. Just stop trying to tell people two things or three things or whatever. You get one message and that's it." Everything else fades. Hit your one thing and make it interesting. Point of view beats positioning. "Real ingredients, real flavor" could be anyone. "Microwaves Not Welcome" can only be Chipotle. Alicia connects it directly to her comms background: "If we don't have a unique point of view, no one cares. You sound like everyone else. You gotta be provocative if you want to stand out." The difference between good copy and great copy is the same as the difference between a statement and a stance. Quote "Confusion does not equal a sale. We just do so much in B2B and it can be extremely overwhelming. I gotta take that back to the team." - Alicia diVittorio Time Stamps [1:12] Meet Alicia diVittorio, Head of Global Corporate Marketing at SilverfortĀ [2:22] Why the "For Real" Campaign: The Song, the Simplicity, the LessonĀ [4:12] What Is Chipotle's "For Real" Campaign? A Brief HistoryĀ [6:44] Going Back to Your Roots ā What Chipotle Did RightĀ [15:40] Competitive Positioning Without Being Gross About ItĀ [19:00] "Microwaves Not Welcome": The Power of a Point of ViewĀ [22:44] Targeting Multiple Demographics With One IdeaĀ [26:49] The Bag Problem: Great Campaign, Missed Real EstateĀ [30:13] What B2B Marketers Should Steal From ChipotleĀ [43:10] Final Thoughts and Takeaways Links Connect with Alicia on LinkedInĀ Learn more about Silverfort About Remarkable! Remarkable! is created by the team at Caspian Studios, the premier B2B Podcast-as-a-Service company. Caspian creates both nonfiction and fiction series for B2B companies. If you want a fiction series check out our new offering - The Business Thriller - Hollywood style storytelling for B2B. Learn more at CaspianStudios.com. In today's episode, you heard from Ian Faison (CEO of Caspian Studios) and Meredith Gooderham (Head of Production). Remarkable was produced this week by Meredith Gooderham, edited by Jon Goldberg, and our theme song is "Solomon" by FALAK. Create something remarkable. Rise above the noise. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
An Indian lawyer in 2000 could not have recognised the legal ecosystem of today. One firm took India marching forward into a new world. Akshay Jaitly joins Amit Varma in episode 443 of The Seen and the Unseen to describe the rise of the firm he founded, Trilegal -- and the lessons he learnt during that journey. (FOR FULL LINKED SHOW NOTES, GO TOĀ SEENUNSEEN.IN.) Also check out: 1. Akshay Jaitly onĀ Twitter,Ā LinkedinĀ andĀ Nicheless. 2.Ā Trilegal: The Making of a Modern Indian Law FirmĀ -- Akshay Jaitly. 3.Ā TrustBridge. 4.Ā Climate Change and Our Power SectorĀ ā Episode 278 of The Seen and the Unseen (w Akshay Jaitley and Ajay Shah). 5.Ā Blood on the TracksĀ -- Bob Dylan. 6.Ā The Art of ReadingĀ -- Episode 120 of Everything is Everything. 7.Ā Scrivener. 8.Ā The Creative ActĀ -- Rick Rubin. 9.Ā Testaments BetrayedĀ ā Milan Kundera. 10.Ā Amicus Curiae: Khaitan & Co is 100Ā -- Aditi Roy Ghatak. 11.Ā The Broken ScriptĀ ā Swapna Liddle. 12.Ā Swapna Liddle and the Many Shades of DelhiĀ ā Episode 367 of The Seen and the Unseen. 13.Ā The Tocqueville Effect. 14.Ā The Age of the Partial OutsiderĀ ā Janan Ganesh. 15.Ā Rahul Matthan Seeks the ProtocolĀ ā Episode 360 of The Seen and the Unseen. 16.Ā Privacy 3.0Ā ā Rahul Matthan. 17.Ā Letters To A Young PoetĀ --Ā Rainer Maria Rilke. 18.Ā Shattered Lands: Five Partitions and the Making of Modern AsiaĀ -- Sam Dalrymple. 19.Ā A Brief History of the World in 47 BordersĀ --Ā Jonn Elledge. 20.Ā The Beginning of InfinityĀ -- David Deutsch. 21.Ā The Fabric of RealityĀ -- David Deutsch. 22.Ā A Gentleman in MoscowĀ ā Amor Towles. (Also watchĀ the series!) 23.Ā MoblandĀ --Ā Ronan Bennett. 24.Ā The DiplomatĀ --Ā Debora Cahn. 25.Ā Fontaines DC,Ā Joy Division,Ā Massive Attack,Ā St Germain,Ā Kruder & DorfmeisterĀ andĀ ToscaĀ on Spotify. 26.Ā Rock en Seine. Amit VarmaĀ runs a course calledĀ Life Lessons, which aims to be a launchpad towards learning essential life skills all of you need. For more details, and to sign up,Ā click here. And have you read Amit's newsletter? It's madly active right now! Subscribe right away toĀ The India Uncut Newsletter! It's free! Also check out Amit's online course,Ā The Art of Clear Writing. Episode art: 'Disrupt' byĀ Simahina.
Dr Adam Koontz talks about growing in knowledge and wisdom, and the importance of reading and reflection. Visit our website - A Brief History of Power Sign up for Memento, a Lutheran devotional for men. Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
When petty criminals panicā¦ they run. In this episode of Live, Laugh, Larceny: A True Petty Crime Podcast, Trevin and Amanda explore chaotic escape attempts, strange history, and petty crime stories where fleeing only makes things worse. Trevin deals with a bedtime dilemma as his cat turns cuddles into sleep deprivation, while Amanda admits to driving on expired tags ā despite constant pressure from the cops at her workplace. Killer Facts highlights Dorothy Dietrich, a pioneering female escape artist known for performing a bullet catch with her teeth, while Trevin explores Jamtara, India ā widely known as a hub for phishing scams and cybercrime. Amanda's story takes us to Muskegon Heights, Michigan, where Kendra Aney escalates a drug-related incident by breaking out of a police car in a desperate attempt to flee. Trevin heads to Charleston, South Carolina, where a haunted carriage tour with Palmetto Carriage Works takes a bizarre turn when Nicole Wells' encounter introduces something far less historical ā and far more chaotic ā than expected. From prison breaks to panicked getaways, this episode proves running from the problem rarely ends well.
Humans have been exchanging tokens of friendship since before recorded history. From calling cards to Valentines to Christmas cards, the modern greeting card industry evolved. Research: āAmericaās First Christmas Card.ā Albany Institute of History and Art. https://www.albanyinstitute.org/online-exhibition/50-objects/section/america-s-first-christmas-card Britannica Editors. "scarab". Encyclopedia Britannica, 3 Apr. 2014, https://www.britannica.com/topic/scarab Britannica Editors. "greeting card". Encyclopedia Britannica, 15 Mar. 2024, https://www.britannica.com/topic/greeting-card Brown, Ellen F. āChristmas, Inc.: A Brief History of the Holiday Card.ā JSTOR Daily. Dec. 20, 2015. https://daily.jstor.org/history-christmas-card-holiday-card/ Chase, Ernest Dudley. āThe Romance of Greeting Cards.ā Rust Craft. Cambridge, MA. 1956. āDali at Hallmark.ā Hallmark Art Collection. https://www.hallmarkartcollection.com/creatively-thinking/stories/dali-at-hallmark/ āEsther Howland 1847.ā Mount Holyoke. https://www.mtholyoke.edu/directory/alum/esther-howland Evans, Elaine Altman. āThe Sacred Scarab, Occasional Paper.ā McClung Museum of Natural History and Culture. University of Tennessee. January 1, 1996. https://mcclungmuseum.utk.edu/1996/01/01/sacred-scarab/ Greeting Card Association. āThe History of Greeting Cards.ā https://www.greetingcard.org/history/ Hanc, John. āThe History of the Christmas Card.ā Smithsonian. Dec. 9, 2015. https://www.smithsonianmag.com/history/history-christmas-card-180957487/ Henry, William E. āArt and Cultural Symbolism: A Psychological Study of Greeting Cards.ā The Journal of Aesthetics and Art Criticism, vol. 6, no. 1, 1947, pp. 36ā44. JSTOR, https://doi.org/10.2307/426176 Kavanagh, Marybeth. āLouis Prang, Father of the American Christmas Card.ā The New York Historical. Dec. 19, 2012. https://www.nyhistory.org/blogs/prang Koon, Wee Kek. āHow ancient Chinese new year cards went from elitesā greetings to bribery instruments.ā South China Morning Post. Jan. 31, 2026. https://www.scmp.com/lifestyle/chinese-culture/article/3341675/how-ancient-chinese-new-year-cards-went-elites-greetings-bribery-instruments?module=perpetual_scroll_0&pgtype=article Korolkov, Maxim. āāGreeting Tabletsā in Early China: Some Traits of the Communicative Etiquette of Officialdom in Light of Newly Excavated Inscriptions.ā Tāoung Pao, vol. 98, no. 4/5, 2012, pp. 295ā348. JSTOR, http://www.jstor.org/stable/41725988 Lee, Ruth Webb. āA History of Valentines.ā 1984. Newberry, Percy E. āScarabs: An Introduction to the Study of Egyptian Seals and Signet Rings.ā London. Archibald Constable and Co. Ltd. 1908. https://dn790001.ca.archive.org/0/items/scarabsintroduc00newbuoft/scarabsintroduc00newbuoft.pdf Purcell, Denise. āAuthentic Messaging and Independent Makers Drive Greeting Cards' Next-Gen Relevance.ā U.S. Chamber of Commerce. https://www.uschamber.com/co/good-company/launch-pad/greeting-card-next-gen-relevance#:~:text=The%20category%20is%20massive:%20According,card%20market%20at%20$7%20billion. Grafton, Samuel. āHolly Leaf and Copper Plate.ā The North American Review, vol. 226, no. 6, 1928, pp. 660ā64. JSTOR, http://www.jstor.org/stable/25110633 Shoichet, Catherine E. āThis āvisionaryā woman changed the way many Americans celebrate Valentineās Day.ā CNN. Feb. 14, 2024. https://edition.cnn.com/2024/02/13/style/esther-howland-valentines-card-history-cec Schmidt, Leigh Eric. āThe Commercialization of the Calendar: American Holidays and the Culture of Consumption, 1870-1930.ā The Journal of American History, vol. 78, no. 3, 1991, pp. 887ā916. JSTOR, https://doi.org/10.2307/2078795 Stupperich, Andy. āArt Education: Louis Prang's Christmas Card Competitions.ā The Henry Ford Museum. January 29, 2026. https://www.thehenryford.org/collections/explore/articles/art-education-louis-prang%27s-christmas-card-competitions Terrell, Ellen. āEsther Howland and the Business of Love.ā Library of Congress. March 23, 2016. https://blogs.loc.gov/inside_adams/2016/03/esther-howland-and-the-business-of-love/ āWorld's first printed Valentine's Card.ā A History of the World. BBC. 2014. https://www.bbc.co.uk/ahistoryoftheworld/objects/L1NM_6mWRymAMKXcRDlXJA Wright, Helena E. āA winning design: Prangās Christmas card contests of the 1880s.ā National Museum of American History. December 23, 2019. https://americanhistory.si.edu/explore/stories/winning-design-prangs-christmas-card-contests-1880s See omnystudio.com/listener for privacy information.
Brian Yamabe talks with Pr Willie Grills on Synod Stories about his journey in the ministry, spiritual discipline, the history of pastoral formation, and the SMP program. Visit our website - A Brief History of Power Thanks to our sponsors, Ad Crucem, Memento, and Gnesio Health Music thanks to Verny
Dr Adam Koontz talks about the Roman Catholic positions on war and immigration since the Second Vatican Council. Visit our website - A Brief History of Power Sign up for Memento, a Lutheran devotional for men. Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
Dr Adam Koontz and Col Willie Grills talk about the establishment of Lutheran synods in America, the problem with elevating cultural norms to the level of Biblical standards, and caring too much about internal politics. Visit our website - A Brief History of Power Sign up for Memento, a Lutheran devotional for men. Thanks to our sponsors, Ad Crucem and Gnesio Health Dr Adam Koontz - Redeemer Lutheran Church Pr. Willie Grills - Zion Lutheran Church Music thanks to Verny
Weekend Edition for April 18-19, 2026 Show Notes: Germany / Switzerland - Study TourĀ Support 1517 Podcast Network 1517 Podcasts 1517 on YouTube 1517 Podcast Network on Apple Podcasts 1517 Events Schedule 1517 Academy - Free Theological Education What's New from 1517: 1517 Youtube: How God Still Speaks Today Being Family by Dr. Scott Keith A Reasoned Defense of the Faith by Adam Francisco Stretched: A Study for Lent and the Entire Christian Life by Dr. Christopher Richmann The Essential Nestingen: Essays on Preaching, Catechism, and the Reformation Philip Melanchthon's Commentary on Ecclesiastes, Translated by Dr. Derek Cooper More from the hosts: Dan van Voorhis SHOW TRANSCRIPTS are available: https://www.1517.org/podcasts/the-christian-history-almanac CONTACT: CHA@1517.org SUBSCRIBE: Apple Podcasts Spotify Stitcher Overcast Google Play FOLLOW US: Facebook Twitter Audio production by Christopher Gillespie (outerrimterritories.com).
Dr Adam Koontz talks about the duties of the pastor and helping those struggling in them. Visit our website - A Brief History of Power Sign up for Memento, a Lutheran devotional for men. Dr Adam Koontz - Redeemer Lutheran Church Music thanks to Verny
© 2020-2026 Ivy Podcast Discovery LLC
