Podcasts about graphs

After decades of decline, many church leaders believe that religious life is on the upswing as some younger Americans flock to Christianity — including Vice President JD Vance, whose new book on his Catholic conversion drops this week. But the fuller picture is more complicated. Coming up, we'll talk to religion reporters and a church leader about what may be driving this shift, and what its lasting impacts could be. Guests: Michael O'Loughlin, executive editor, National Catholic Reporter; O'Loughlin has covered the Catholic church for both the Boston Globe and Crux; author, "Hidden Mercy: AIDS, Catholics and the Untold Stories of Compassion in the Face of Fear" Lauren Jackson, deputy editorial director for newsletters and the host of “Believing," The New York Times Ryan Burge, professor of practice at the John C. Danforth Center, Washington University; author, “Graphs about Religion” Danté Stewart, author, “Shoutin' in the Fire: An American Epistle;” an ordained minister at Tabernacle Baptist Church in Augusta, Ga. Learn more about your ad choices. Visit megaphone.fm/adchoices

Media Watch 2026 Episode 19: Musk's army; You're havin' a graph

Jure Leskovec, Professor of Computer Science at Stanford University and Chief Scientist at Kumo.ai, speaks with host Sriram Panyam about relational and graph language models and their transformative impact on enterprise decision-making and predictive modeling. Jure begins by establishing the critical importance of predictive modeling across industries - from fraud detection in financial institutions to customer churn prediction, lifetime value estimation, product recommendations, and healthcare risk assessment. He notes that while AI has made remarkable advances in natural language understanding and computer vision, predictive modeling over enterprise operational data stored in relational databases has been largely left behind, still relying on 30-year-old machine learning approaches that are expensive, time-consuming, and require manual feature engineering. His proposed solution to the fundamental problem with current approaches is relational deep learning and relational transformers. The discussion explores how this approach differs from traditional graph neural networks (GNNs), which Jure pioneered and deployed successfully at Pinterest. Jure concludes with practical guidance for software engineers and data scientists interested in exploring this technology.

Most AI tools are still just indexing documents. The Teamwork Graph has 150 billion connections. That difference is the whole game. I sat down with Jamil Valliani, the Head of AI Product at Atlassian, during Team '26 on The Ravit Show to understand why they are betting the next decade on this approach. Twenty years in Search before this role. Long before vector databases were trendy. Long before RAG was an acronym.A few things we got into:What the Teamwork Graph actually is. Why this architectural choice separates Atlassian's AI from everything else in the market.150 billion connections vs document indexing. Most enterprise AI tools search your text. This connects people, work, decisions, and outcomes across systems. The gap is bigger than I realized.Why connected data wins on accuracy. Atlassian's internal benchmark: 44% more accurate results using 48% fewer tokens. We broke down what is actually happening under the hood.A Search veteran's read on this moment. What makes this AI shift different from every other one. The most grounded take I heard at any conference this year.The line that stayed with me: in the next era of work, the company with the best context will win. Not the company with the best model. Models are getting commoditized. Context is not.If you work on retrieval, RAG, or graph-based AI inside an enterprise, this one is for you.#data #ai #atlassian #team26 #theravitshow

Why Supply Chain Visibility Is One of the Most Consequential and Underestimated Applications of AI in the EnterpriseGuest: Ilya Levtov, Founder and CEO at Craft.co Host: Seth Earley, CEO at Earley Information Science Published on: June 1, 2026In this episode, Seth Earley speaks with Ilya Levtov, Founder and CEO of Craft.co, a supplier intelligence platform that uses AI and knowledge graphs to give enterprises and government agencies visibility into their full supply networks. They explore why most organizations believe they have adequate supply chain visibility when they do not, why a simple risk score will always mislead, and how cross-correlating data streams surfaces risks that no human - and no generic LLM - would ever find alone. Ilya shares candid and specific insights on building knowledge graphs for mission-critical infrastructure, why only one percent of enterprise knowledge exists inside today's LLMs, and how the give-to-get model is turning supply chain intelligence into a shared strategic asset.Key Takeaways:Most enterprises believe their top-supplier relationships give them adequate visibility - but the middle and long tail of a supply network, which can run to 20,000 or 30,000 suppliers, remains almost entirely opaque.Supply chain is a misnomer - it is a complex, multi-dimensional network where companies are simultaneously suppliers, customers, and competitors to each other.A simple risk score is not meaningful and not actionable; supplier risk is deeply contextual and requires human judgment to weigh cost, probability, and consequence together.Cross-correlating data streams reveals hidden risks that no single source can surface - including correlations between employee morale and cybersecurity vulnerability that have proven highly predictive.Only approximately one percent of enterprise knowledge exists inside today's LLMs - which is exactly why a specialized knowledge graph grounded in proprietary data is essential before applying AI.AI has compressed analyst work on a supplier report from eight hours to under 30 minutes - but the decision of what to do with those findings still requires human judgment and always will.The give-to-get model and supplier passporting allow enterprises to share intelligence across a shared supply network without compromising their own competitive position.Insightful Quotes:"Only 1% of enterprise knowledge approximately exists inside the LLMs today. Companies don't want to give all of their data to the LLMs. Data providers don't want to give it for free either. That's why you need a specialized approach - leverage the power of the models on your own data set and on your knowledge graph." - Ilya Levtov"A financially vulnerable supplier becomes a target for adversarial capital - entities coming in from unfriendly nations looking to survive. You're connecting two different data sets, connecting entities, and getting to a very significant risk insight you need to act on before it becomes a problem for your enterprise." - Ilya Levtov"Organizations compete on their knowledge - knowledge of customers, knowledge of solutions, knowledge of supply chains, knowledge of routes to market. Those are competitive advantages. You do not want those inside an LLM. That is why doing this in a way that is internal and proprietary is so important." - Seth EarleyTune in to discover why supply chain visibility is one of the most important and most underestimated applications of AI in the enterprise today - and what it actually takes to build intelligence at the scale the problem demands.LinksLinkedIn: https://www.linkedin.com/in/ilya-levtov/ Website: https://www.craft.coThanks to our sponsors:VKTREarley Information ScienceAI Powered Enterprise Book

Immerse yourself in captivating science fiction short stories, delivered daily! Explore futuristic worlds, time travel, alien encounters, and mind-bending adventures. Perfect for sci-fi lovers looking for a quick and engaging listen each day.

In this episode of the Crazy Wisdom Podcast, host Stewart Alsop sits down with Joshua Bate, founder of Bonfires.ai and DeciWorld, for a wide-ranging conversation covering knowledge management, graph technology, ontologies, decentralized science, and the future of how humans organize and share information. They break down the differences between personal and enterprise knowledge management, explore why flat ontological graphs may be the key to making diverse knowledge bases interoperable, and get into why traditional RAG systems break down at scale and how graph RAG offers a more principled solution. The conversation expands into the philosophy of categorization, the slow death of basic "gentleman science" under institutional pressures, and how decentralized protocols might restore a kind of mycelial knowledge network connecting small groups of researchers, enthusiasts, and communities — much like the original spirit of the encyclopedia before it was co-opted by institutions. You can learn more about Joshua's work at bonfires.ai and deci.world or follow him on X at @Bonfiresai and @DeSciWorld.Timestamps00:00 - Stewart introduces Joshua Bate, founder of Bonfires.ai, discussing personal versus enterprise knowledge management and their fundamental differences at scale.05:00 - Joshua explains ontologies as classifiers for knowledge structures, describing their two-year search for a perfect ontology and ultimately building a flat, ontology-less graph protocol.10:00 - Stewart connects categorization to shamanic practice and intercategorical theory, noting how major companies like Netflix and Yahoo built graph-based ontologies while the discipline remains underappreciated philosophically.15:00 - Joshua traces Bonfires origins through decentralized science, explaining how NFT community excitement inspired redirecting capital toward funding unconventional researchers locked out of institutional systems.20:00 - Joshua describes building federated knowledge networks through hackathons and conferences, comparing the vision to what Wikipedia could have been with decentralized incentive structures.25:00 - Discussion shifts toward inevitable collapse of rigid scientific institutions, debating patchwork age theory, nation-state fragmentation, and rhizomatic versus arboreal knowledge structures.30:00 - Joshua articulates the mycelial network vision, enabling direct cross-cultural information access where individuals control their own narrative lens, warning against collective we thinking and authoritarianism.Key Insights1. Knowledge management exists on a spectrum from personal to enterprise, but the founder of Bonfires argues this split is artificial. He believes knowledge itself does not respect those boundaries, and that small groups, researchers, hobbyists, and large institutions all possess knowledge that can and should interoperate with each other.2. After two and a half years of searching for the perfect ontology to structure their knowledge graph, the team concluded that no perfect ontology exists. Their solution was to build the flattest possible graph structure with only events, entities, and edges, creating a base layer others can build specialized ontologies on top of.3. Graph-based knowledge systems are more efficient than traditional databases for AI traversal because once a graph is computed, it is relatively free to query. Graph RAG combines the discovery power of vector search with the structured precision of graph traversal, solving many hallucination problems associated with standard retrieval augmented generation.4. Basic scientific research, the soil from which applied discoveries grow, is deteriorating because institutional funding structures only reward commercially viable outcomes. The founder built his platform partly to redirect community-driven capital toward researchers who are doing important work without institutional support.5. The institutionalization of science has historically blocked the open exchange of ideas that drove the original scientific revolution. The human spirit for open inquiry has not changed, but people cannot pursue it without financial support, and building decentralized infrastructure could restore that possibility.6. A federated knowledge network would allow individuals to access information from any contributor and filter it through their own preferred lens, rather than receiving information pre-filtered by centralized platforms. This represents a form of information symmetry similar to how mycelial networks distribute nutrients across a forest.7. The concern is not whether current scientific and governmental institutions will change but in what direction the rebuilding goes. Those capitalizing on the transition carry the same incentives as the previous era, which risks reproducing the same problems inside new structures.

Send us Fan MailA father, two of his children, and a family friend — all mathematicians — made progress on a long-standing problem in group theory by coming together at the Isaac Newton Institute.Listen as Plus Magazine editors Rachel Thomas and Marianne Freiberger interview Roman Sauer, and Uri, Saar, and Shaked Bader to find out more about their research and paths to mathematics.The Operators, Groups, and Graphs programme was in residence at the INI from July to December 2025: https://www.newton.ac.uk/event/ogg/The Isaac Newton Institute is a national and international visitor research institute. It runs research programmes on selected themes in mathematics and the mathematical sciences with applications over a wide range of science and technology. It attracts leading mathematical scientists from the UK and overseas to interact in research over an extended period.newton.ac.uk

In Season 15 episode 2, Elixir Wizards Sundi Myint and Charles Suggs chat with Micah Cooper to talk about distributed systems, data replication, and what it actually looks like to build these ideas in Elixir.   Micah shares his journey from Ruby to Elixir and walks us through Visor, a library he's building based on the Viewstamps replication algorithm. Inspired by systems like TigerBeetle, Visor explores how you can replicate state across nodes using GenServers, giving you fault tolerance and recovery without relying entirely on traditional database patterns.   We talk about the difference between distributed systems and data replication, where things tend to get misunderstood, and what changes when you start thinking about state this way. The conversation also touches on event sourcing, tradeoffs in system design, and how Elixir's distributed model makes some of these concepts more approachable than you might expect.   Along the way, we talk about building for curiosity, experimenting with new ideas, and how projects like this push the ecosystem forward.   Topics discussed in this episode: Building Visor and working with the Viewstamps replication model Replicating GenServer state across nodes Distributed systems vs. data replication Lessons from TigerBeetle and financial system design Event sourcing challenges and tradeoffs Rethinking database-first architectures Snapshotting, recovery, and fault tolerance The role of Elixir's distributed model Experimentation, learning, and building for curiosity   Links mentioned: Micah's GitHub https://github.com/mrmicahcooper Micah's GitLab https://gitlab.com/mrmicahcooper The Visor repository: https://gitlab.com/mrmicahcooper/visor Visor Hex Package https://hex.pm/packages/visor Ruby on Rails https://rubyonrails.org/ Phoenix LiveView Framework https://www.phoenixframework.org/ Zig Programming Language https://ziglang.org/ TigerBeetle https://tigerbeetle.com/ TigerBeetle internal docs https://github.com/tigerbeetle/tigerbeetle/tree/main/docs/internals The BEAM https://www.erlang-solutions.com/blog/the-beam-erlangs-virtual-machine/ GenServer https://hexdocs.pm/elixir/GenServer.html Apache Kafka https://github.com/apache/kafka RabbitMQ https://www.rabbitmq.com/ Redpanda https://www.redpanda.com/ SQL https://www.ibm.com/think/topics/structured-query-language Kubernetes https://kubernetes.io/ YAML https://yaml.org/ Nomad Workload Orchestrator https://developer.hashicorp.com/nomad Flutter https://flutter.dev/ Commanded https://hexdocs.pm/commanded/Commanded.html Go Programming Language https://go.dev/ Clojure Programming Language https://clojure.org/ Nebulex https://hexdocs.pm/nebulex/Nebulex.html Mnesia https://www.erlang.org/doc/apps/mnesia/mnesia.html Cachex https://hexdocs.pm/cachex/Cachex.html libgraph https://hexdocs.pm/libgraph/Graph.html Horde https://hexdocs.pm/horde/Horde.Registry.html NocFree split keyboard https://www.nocfree.com/ Micah's LinkedIn https://www.linkedin.com/in/micah-cooper-4a737560/ 

Le festival Graf Zeppelin a une nouvelle fois mandaté Jack…Sans Bob cette fois.D'une mission simple et efficace. Donner envie aux gens de venir au festival qu'il affectionne tant.Etant un homme plutôt courageux que rien n'arrête, il a donc réalisé un petit entretien avec Jimbo et Tom du groupe Howard.Un échange qui espérons le vous donnera envie de découvrir le groupe et de venir également le voir se produire sur scène lors de la prochaine édition de ce festival qu'il est vachement pas mal…En joie

On the latest episode of Minor Issues, Mark Thornton opens with a detailed analysis of the gold correction. Is the three-month decline a sign that inflation is over, or a temporary reallocation driven by war? The answer is in the data: the CRB commodity index continues to climb, the money supply is at an all-time high, and there is no evidence of deflation anywhere in the price structure. The inflation regime remains firmly in place, and the gold correction is a normal feature of bull markets whose real-world zigzags get smoothed away on long-term charts.The second half features a panel interview from VRC Media with Rick Rule, hosted by Darrell Thomas. Rule lays out the case for a decade-long commodity super cycle driven by 30 years of underinvestment in productive capacity. He delivers a sobering calculation: $39 trillion in on-balance-sheet federal debt plus $120 trillion in off-balance-sheet unfunded entitlement promises (a combined $160 trillion against $170 trillion in total private American net worth). The only realistic resolution, Rule argues, is a "dishonest default," inflating away the purchasing power of the dollar, just as happened in the 1970s when the dollar lost 75% of its value. Mark concurs, noting that the money supply is growing at record pace even as Washington insists it's being "restrictive."Mark's "Gold vs CRB Index" graph is available here: https://mises.org/MI175_GraphThe original VRIC interview is online here: https://www.youtube.com/watch?v=3kMiiC08TNo20% off listener offer on the new insulated Minor Issues tumbler and three of Mark's books, signed if ordered by the end of April: https://mises.org/MinorIssuesTumbler. Use coupon code Thornton.Be sure to follow Minor Issues at https://Mises.org/MinorIssues

John and Josh look at a graph on how many Huskers have been drafted with the recent coaches.

This week on “Jesuitical,” Ashley and Zac speak with Ryan Burge, author of the “Graphs about Religion” Substack and the new book, The Vanishing Church: How the Hollowing Out of Moderate Congregations Is Hurting Democracy, Faith, and Us. They discuss the polarization of U.S. Christianity and the supposed Gen-Z “religious revival.” In Signs of the Times, Ashley and Zac discuss some highlights from Pope Leo's trip to Africa; what Pope Leo called the not-exactly-accurate media narrative around him and President Trump; and the first anniversary of Pope Francis' death. 00:00 A Gen-Z religious revival? 3:38 Highlights of Pope Leo's trip to Africa 10:05 VP Vance questions Pope Leo's theology 20:37 Remembering Pope Francis 22:50 Moderate Christianity is vanishing 25:49 U.S. religion is coded "conservative" 34:54 Catholic demographic trends 37:15 Political implications 40:53 Are young people going back to church? 48:18 Winner churches 52:56 Gen-Z religious trads 1:04:08 Faith Sharing: Pope Francis' humble tomb Links: ⁠Order Ryan's book, The Vanishing Church⁠ ⁠Graphs about Religion⁠ ⁠Pope Leo walks in the footsteps of St. Augustine in Hippo⁠ ⁠Pope Leo denounces those who use the name God for military gain⁠ ⁠Pope Leo named one of Time magazine's ‘100 Most Influential People of 2026'⁠ ⁠Pope Leo remembers ‘the great gift' of Pope Francis on the first anniversary of his death⁠ You can follow us on ⁠X⁠ and on ⁠Instagram⁠ @jesuiticalshow.   You can find us on Facebook at ⁠facebook.com/groups/jesuitical.⁠  Please consider supporting Jesuitical by becoming a digital subscriber to America magazine at ⁠americamagazine.org/subscribe⁠ Learn more about your ad choices. Visit megaphone.fm/adchoices

The Racing Dudes compare Beyer Speed Figures and Thoro-Graph numbers to determine which metric is more predictive when handicapping the 2026 Kentucky Derby. They break down key contenders through both lenses and discuss what bettors should actually trust heading into the Run for the Roses.

Welcome to Episode 426 of the Microsoft Cloud IT Pro Podcast.Ben and Scott are back together this week to talk through Microsoft 365 Copilot Cowork, including how it compares to Claude Cowork and where each one makes sense. The two products share a name but work pretty differently. Claude Cowork runs locally on your desktop and can access files on your machine, supports MCP server connections while M365 Copilot Cowork runs in the cloud, requires files to be in OneDrive, and does not support MCP connectors yet. On the flip side, the Microsoft version runs scheduled tasks without needing your machine to be on, has native access to all your M365 data through Graph, and fits inside your existing compliance and security controls through Purview, which matters a lot for regulated organizations. Your support makes this show possible! Please consider becoming a premium member for access to live shows and more. Check out our membership options. Show Notes Quentin Amaudry – As everyone knows, Cowork is coming within Copilot and it is extremely promising Copilot Cowork vs Claude Cowork: Same AI, Different Worlds Copilot Cowork: A new way of getting work done Cowork overview (Frontier) About the sponsors   TrustedTech is a leading Microsoft Cloud Solution Provider (CSP) specializing in Microsoft Cloud services, Microsoft perpetual licensing, and Microsoft Support Services for medium and enterprise-sized businesses. Our robust team of in-house, U.S-based Microsoft architects and engineers are certified in all 6/6 Microsoft Solutions Partner Designations in the Microsoft Cloud Partner Program. M365 Licensing Consultation M365 Tenant Assessment Copilot Readiness Assessment Your migration and governance solution for Microsoft 365. ShareGate helps your teams simplify tenant migrations, get Copilot-ready, and take control of Microsoft 365 governance. Nasuni is a leading unstructured data platform for enterprises where file data is mission-critical for both people and AI. We power the operational file layer where work happens — helping organizations manage, protect, and activate data so teams can work smarter, reduce costs, and operate securely without limits. Visit nasuni.com to learn more. Would you like to become the irreplaceable Microsoft 365 resource for your organization? Let us know!

Text us your thoughts!This month's debate is a recording from a LIVE debate that took place at the West Virginia Council of Teachers of Mathematics (WVCTM) Conference in March of 2026.In this quick follow-up to last week's episode, we invited each of our guests to model a short, fun classroom debate. In just a few minutes, you can hear a sample debate that captures the spirit of productive mathematical argumentation—thoughtful, curious, and includes reasoning. Tune in for a rapid-fire glimpse of what these debates can look like in action!You can reach Sissy Collins at the Harrison County Board of Education, via email at jecollin@k12.wv.us, or on Facebook.You can find Sarah McGivern via Jefferson County Schools or on Instagram: @SSMcGivernYou can reach Ellen Holt at Summers County HS, via email at eholt@k12.wv.us, or on LinkedInAnd find Jason Massie via Mountain View School.And thanks to the WVCTM Conference for inviting us in!Listened to the episode? Now, it's your turn to share! Find us on Social Media: @DebateMath to share your thoughts.Don't forget to check out the video version of this podcast on our YouTube channel!Keep up with all the latest info by following @DebateMath or going to debatemath.com. Follow us @Rob_Baier & @cluzniak. And don't forget to rate and review us on Apple Podcasts!

Monorepo, Polyrepo, Frontend hier, Backend dort, Mobile-App nochmal woanders. Klingt nach sauberer Trennung, führt in der Praxis aber oft zu genau dem, was wir als Entwickler:innen am wenigsten brauchen: Reibung. Abhängige Pull Requests, aufeinander wartende Releases, doppelte Tooling-Arbeit und jede Menge Koordination zwischen Teams. Die spannende Frage ist also nicht nur, ob Monorepos ein Comeback feiern, sondern ob sie heute, mit besserem Tooling und AI im Rücken, endlich ihr Versprechen einlösen.In dieser Episode sprechen wir mit Max Kless, Senior Software Engineer bei Nx, über den aktuellen Stand von Monorepos. Wir klären, was ein Monorepo eigentlich ist, warum Monorepo nicht gleich Monorepo ist und wieso ein pragmatischer, hybrider Ansatz für viele Teams sinnvoller ist als ein einziges gigantisches Repository. Außerdem schauen wir auf CI, Caching, Project Graphs, Code Ownership, Plattform-Teams und die kulturelle Seite hinter dem Thema. Denn Monorepos sind nicht nur Architektur und Tooling, sondern auch Zusammenarbeit, Standards und ein bisschen Inner Source im Alltag.Besonders spannend wird es bei AI, LLMs und Coding Agents. Wenn mehr Kontext zu besserer Unterstützung führt, werden Monorepos plötzlich wieder hochrelevant. Wir diskutieren, warum ein gemeinsamer Code-Kontext für AI-Systeme ein echter Hebel sein kann, wo die Grenzen liegen und worauf du bei einer Einführung achten solltest. Wenn du wissen willst, ob Monorepos 2026 mehr sind als alter Google-Glanz, dann bist du hier genau richtig.Bonus: Selbst Jenkins bekommt einen kleinen Ehrenmoment.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Download Nick's free second brain skill -- one-click install that sets up your entire Obsidian vault and ingestion workflow inside Claude Code: https://return-my-time.kit.com/286e11f7e6I brought on Nick Spisak to build a complete second brain live -- start to finish, in under 20 minutes. By the end of this episode, you'll know exactly how to build your own second brain -- and you can grab Nick's free skill to do it in one click.Timestamps00:00 - Intro and Karpathy's viral second brain tweet00:24 - What the second brain concept is03:28 - Obsidian Web Clipper: scraping pages into your vault04:41 - Nick's free skill: wizard, ingest, query, and lint commands05:53 - Live demo: running the setup wizard in Claude Code08:38 - How many vaults to manage: personal vs. business10:30 - Opening the vault and exploring the file structure12:21 - Graph view: seeing connections between your data15:38 - Ingest command: raw data into organized wiki16:29 - Automating ingestion on a cron schedule19:12 - Compounding value and syncing the vault across devices20:19 - Pruning the vault with the lint command21:53 - Your data set as a moat in the AI ageKey Points* Karpathy released a framework for building an LLM knowledge base. Nick turned it into a free Claude skill with a guided setup wizard, ingest, query, and lint commands -- works across Claude Code, Codex, Gemini CLI, and more. One-click install, no coding required.* The system runs on three tiers: raw (brain dump), wiki (AI-organized knowledge base), and outputs (answers from querying). Drop files into raw, run ingest, and the AI maps everything into structured wiki entries with relationship graphs.* You can automate ingestion using Claude Code's loop feature so the vault stays current without manual work. Pair with Obsidian's paid sync tier and a note captured on your phone is indexed before you're back at your desk.* The lint command health-checks your wiki for outdated entries and missing connections -- and tells you exactly what to clip next to close the gaps. The wiki tells you what it doesn't know yet.* Day zero this thing is basic. Day 90 it's a company asset no competitor can copy. Your private knowledge base is the foundation for every agent and skill you build -- and nobody else will have it.Join the Build With AI community - weekly AI implementations, live coaching, and templates built for non-technical entrepreneurs: https://www.skool.com/buildwithai/aboutFIND ME ON SOCIALX/Twitter: https://x.com/coreyganimInstagram: https://www.instagram.com/coreyganim/LinkedIn: https://www.linkedin.com/in/coreyganim/YouTube: https://www.youtube.com/@coreyganimFIND NICK ON SOCIALX: https://x.com/NickSpisak_LinkedIn: https://www.linkedin.com/in/nicholasspisak/YouTube: https://www.youtube.com/@nickspisak_

What I Did as a Child – Co robiłem jako dziecko "Co robiłem jako dziecko" means "what I did as a child," and in this nostalgic micro-lesson you'll say it like you're flipping through old photo albums with your Polish grandmother. First you hear the phrase at native speed, then slowed down so you can master the rolling "r" and the soft "dziecko." We drop it into three memory-lane-ready sentences: – "Kiedy byłem mały…" (When I was little…) – "Lubiłem się bawić." (I liked to play.) – "To było dawno temu." (That was a long time ago.) Repeat-along track included—perfect while you reminisce or share your own childhood stories. Challenge: Tell us in the comments what YOU did as a child—reply in Polish and Ania might sing your answer in the next episode     What we discussed:   0:00 Welcome & QR Code 0:45 "Dziecko" - The Polish Word for Child 1:30 Childhood Bedroom Memories 2:30 Sports & Experiments 3:30 School & Newspapers 4:30 University & Opinions 5:30 Wishes & Dashboards 6:30 Stars & Classrooms 7:30 Time & Dance 8:30 Building & Creating 9:30 Television & Media 10:30 Graphs & Grades 11:30 Comics & Parks 12:30 Photos & Memories 13:30 Games & Play 14:30 Suggestions & Ideas 15:30 Early Jobs & Studies 16:30 Army & Activities 17:30 Toys & Cars 18:30 Sunset & Evening Play 19:30 Mom's Voice & Family 20:30 Growing Up & Yesterday 21:30 Fitness & Sports 22:30 Comfort & Balm 23:30 National & Sharing 24:30 Adult Life & Planning 25:30 Vision & Yesterday's Story 26:30 Short Stories & Patches 27:30 Royal Games & Health 28:30 Memories & Reports 29:30 Calls & Moods 30:30 Sports & Chores 31:30 Swimming & Memories 32:30 Web & Changes 33:30 Books & People 34:30 School Initiatives 35:30 Travel & Problems 36:30 Chats & Opinions 37:30 Goals & School Sheets 38:30 Status & Movies 39:30 Platforms & QR Code 40:30 Your Turn to Practice!   English Polish Pronunciation Guide child dziecko dzyeh-tsoh childhood dzieciństwo dzyeh-cheen-stvo memory wspomnienie vspo-mnyeh-nyeh to remember pamiętać pah-myeh-tahch to forget zapomnieć zah-pom-nyehch to play bawić się / grać bah-veech sheh / grahch toy zabawka zah-bahf-kah game gra grah school szkoła shkoh-wah teacher nauczyciel / nauczycielka now-chi-tyel / now-chi-tyel-kah friend przyjaciel / przyjaciółka psi-ya-chyel / psi-ya-choow-kah family rodzina roh-jee-nah mom mama mah-mah dad tata tah-tah brother brat braht sister siostra syoh-strah home dom dohm room pokój poh-kooy bed łóżko woo-shkoh to sleep spać spahch to eat jeść yeshch favorite food ulubione jedzenie oo-loo-byoh-neh yeh-dzeh-nyeh sport sport sport football/soccer piłka nożna peew-kah nozh-nah ping pong ping pong ping pong swimming pływanie pwih-vah-nyeh bicycle rower roh-ver to read czytać chi-tahch book książka kyohnsh-kah comic book komiks koh-meeks TV telewizja teh-leh-veez-yah cartoon bajka bahy-kah video game gra wideo / gra komputerowa grah vyeh-deh-oh / grah kom-poo-teh-roh-vah to sing śpiewać shpyeh-vahch song piosenka pyoh-sen-kah to dance tańczyć tahyn-chich party impreza eem-preh-zah birthday urodziny oo-roh-jee-ni holiday wakacje / ferie vah-kah-tsyeh / feh-ryeh summer lato lah-toh winter zima zee-mah to grow up dorastać doh-rah-stahch adult dorosły / dorosła doh-roh-swi / doh-roh-swah young młody / młoda mwoh-di / mwoh-dah old stary / stara stah-ri / stah-rah yesterday wczoraj fchoh-rah-y today dziś dzeesh tomorrow jutro yoo-troh long ago dawno temu dahv-noh teh-moo always zawsze zahf-sheh never nigdy neeg-di sometimes czasami chah-sah-mee often często chen-stoh  

Juan and Tim have a rant session with a special guest in person, Jesús Barrasa, well known in the knowledge graph space. We covered AI trends, the balance between operational vs. strategic work, knowledge graphs, context graphs. The most valuable part of our rant was our pragmatic discussion about ontologies stripping them down to what they actually are and why they matter. Starting to work with ontologies? Think about these two dimensions: WHAT (Formal, Explicit and Shared Meaning) and WHY (Interoperability, Automation).See omnystudio.com/listener for privacy information.

Are you still relying on OCR for your enterprise AI? You're losing critical context.In this episode, Anaiya Raisinghani (Sr. Tech. Evangelist, AI Startups & Ventures at MongoDB) sits down with Adityavardhan Agrawal, Co-Founder and CEO of Morphik. They dive deep into how Morphik is helping developers and enterprises understand complex, unstructured data and automate high-leverage workflows.Adi breaks down the limitations of standard RAG pipelines and reveals why they turned to Vision Language Models (VLMs) to process complex documents like architectural floorplans.What you'll learn in this episode:The OCR Trap: Why text extraction is inherently lossy for complex documents and how VLMs generate better embeddings.The RAG Misconception: Why getting high-quality context requires much more than just plain vector search.Database Architecture: Why Morphik hit the limits of Postgres/JSONB for dynamic datasets and how migrating to MongoDB Atlas simplified their multi-tenancy and querying.Massive ROI: How one manufacturing customer used Morphik to slash their quote generation time from 7 days to under 2 minutes.The Future of Knowledge: Building self-healing, self-updating data layers that leverage MQL.(Want to start building? You can use Morphik's API, Python/TypeScript SDKs, or grab the Docker image from GitHub today!)⏱️ Chapter Timestamps00:00 - Intro: Meet Adi and Morphik01:18 - APIs, SDKs, and Getting Started with Morphik02:28 - The Lightbulb Moment: Why Standard AI Fails on Unstructured Data04:44 - The Biggest Misconception About RAG06:24 - Vision Language Models (VLMs) vs. Traditional OCR08:35 - Reducing Entropy: Combining Embeddings with Knowledge Graphs10:13 - Architecture Deep-Dive: Hitting the Limits of Postgres & JSONB12:06 - Why Morphik Migrated to MongoDB Atlas13:24 - Simplifying Multi-Tenancy at Scale15:13 - Ensuring Data Security and Reliability16:33 - Accelerating Growth with MongoDB for Startups18:10 - Real-World Impact: Cutting Quote Generation from 7 Days to 2 Minutes20:15 - The Future: Self-Healing Data Layers and Native MQL

Lorenzo Moriondo is a Technical Lead for AI at tuned.org.uk, working on AI agent protocols, graph-based search, and production-grade LLM systems.arrowspace: Vector Spaces and Graph Wiring // MLOps Podcast #365 with Lorenzo Moriondo, AI Research and Product EngineerJoin the Community: https://go.mlops.community/YTJoinInGet the newsletter: https://go.mlops.community/YTNewsletterMLOps GPU Guide: https://go.mlops.community/gpuguide// Abstract Meet arrowspace — an open-source library for curating and understanding LLM datasets across the entire lifecycle, from pre-training to inference.Instead of treating embeddings as static vectors, arrowspace turns them into graphs (“graph wiring”) so you can explore structure, not just similarity. That unlocks smarter RAG search (beyond basic semantic matching), dataset fingerprinting, and deeper insights into how different datasets behave.You can compare datasets, predict how changes will affect performance, detect drift early, and even safely mix data sources while measuring outcomes.In short: arrowspace helps you see your data — and make better decisions because of it.// BioWith over a decade of experience in software and data engineering across startups and early-stage projects, Lorenzo has recently turned his focus to the AI-assisted movement to automate software and data operations. He has contributed to and founded projects within various open-source communities, including work with Summer of Code, where he focused on the Semantic Web and REST APIs.A strong enthusiast of Python and Rust, he develops tools centered around LLMs and agentic systems. He is a maintainer of the SmartCore ML library, as well as the creator of Arrowspace and the Topological Transformer.// Related LinksWebsite: https://www.tuned.org.uk~~~~~~~~ ✌️Connect With Us ✌️ ~~~~~~~Catch all episodes, blogs, newsletters, and more: https://go.mlops.community/TYExploreJoin our Slack community [https://go.mlops.community/slack]Follow us on X/Twitter [@mlopscommunity](https://x.com/mlopscommunity) or [LinkedIn](https://go.mlops.community/linkedin)] Sign up for the next meetup: [https://go.mlops.community/register]MLOps Swag/Merch: [https://shop.mlops.community/]Connect with Demetrios on LinkedIn: /dpbrinkmConnect with Chris on LinkedIn: /lorenzomoriondo

Rodrigo Coelho is CEO of Edge & Node. In this episode, recorded live at Merge Sao Paulo, joins host Aaron Stanley to explore the cutting edge of agentic commerce and blockchain data infrastructure. Rodrigo shares how Edge & Node, the original team behind The Graph protocol - built the indexing layer that quietly powers much of Web3 today, and how their new product, AMP, is modernizing that infrastructure for institutional adoption. The conversation digs into why crypto rails are uniquely suited for the agentic economy: from micro-payments between AI agents to ephemeral virtual cards bridging the gap for everyday merchants, and why agents paying each other via stablecoins may be closer than we think.You can connect with Rodrigo on https://www.linkedin.com/in/rodrigoco/------------------------------------------------------------------Figment is the leading independent provider of staking infrastructure with $18B assets under stake and provides the complete solution for over 1000 institutional clients in Latin America and globally. Through its enterprise-grade infrastructure, Figment enables clients such as banks and exchanges, to earn rewards on Proof-of-Stake assets such as Ethereum and Solana, while maintaining the highest standards of security, compliance, and performance.Learn more at ⁠⁠⁠⁠⁠⁠⁠⁠figment.io⁠⁠⁠⁠⁠⁠⁠⁠-------------------------------------------------------------------

New Data about New Sets! YouTube version: https://youtu.be/_1ZTxcjWXcY MERCH STORE: https://shop.spacecowmedia.com/Decklists: https://archidekt.com/edhrecastExclusive content on Patreon! https://patreon.com/edhrecastGet new cards on Cardsphere! https://www.cardsphere.com/welcome?referrer=edhrecastProud partners with DragonShield: https://www.dragonshield.com/?ref=edhrecastSocials:@EDHRECast@JosephMSchultz@danaroach@mathimus5500:00 Highest Spikes07:22 Biggest Drops09:26 Graph #213:12 Sidebar15:42 Conclusions17:38 Challenge the Stats!Title sequence by Daniel Woodling / MTG Explainers: https://bit.ly/3982yYaCard images courtesy of Scryfall: https://scryfall.com/Elevate by LiQWYD https://soundcloud.com/liqwydCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: https://bit.ly/liqwyd-elevateMusic promoted by Audio Library https://youtu.be/nwSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

If my podcast has helped, ⁠my new book, The Light Between the Leaves⁠, goes even deeper“I'm a failure.” “I'm worthless.” “I'm behind everyone else.” If you've ever had thoughts like these, I want to show you how your mind might be distorting reality.In this video, I break down how depression uses black-and-white thinking, overgeneralization, and selective evidence to convince you that you're at the bottom. Then I walk you through one of my favorite tools—the Continuum Exercise—so you can actually test those thoughts.In my experience, you're almost never where your depression says you are. And seeing where you actually fall can give you just enough space to start moving forward again.Next Steps:

No-one knows when AI will begin having transformative impacts upon the world. People aren't sure and shouldn't be sure: there just isn't enough evidence to pin it down. But we don't need to wait for certainty. I want to explore what happens if we take our uncertainty seriously — if we act with epistemic humility. What does wise planning look like in a world of deeply uncertain AI timelines? I'll conclude that taking the uncertainty seriously has real implications for how one can contribute to making this AI transition go well. And it has even more implications for how we act together — for our portfolio of work aimed towards this end.   AI Timelines By AI timelines, I refer to how long it will be before AI has truly transformative effects on the world. People often think about this using terms such as artificial general intelligence (AGI), human level AI, transformative AI, or superintelligence. Each term is used differently by different people, making it challenging to compare their stated timelines. Indeed even an individual's own definition of their favoured term will be somewhat vague, such that even after their threshold has been crossed, they might have [...] ---Outline:(00:58) AI Timelines(04:38) Short vs Long Timelines(07:05) Broad Timelines(17:55) Implications(19:46) Hedging(20:58) A Different World(24:00) Longterm Actions(28:33) Conclusions --- First published: March 19th, 2026 Source: https://forum.effectivealtruism.org/posts/HCR2AE9it279ggiZT/broad-timelines --- Narrated by TYPE III AUDIO. ---Images from the article:Apple Podcasts and Spotify do not show images in the episode description. Try Pocket Casts, or another podcast app.

Self-monitoring is the skill that quietly changes everything: focus, impulse control, distress tolerance, and even conflict at home and school. In this Overpowering Emotions episode, Dr. Caroline teaches educators, parents, and mental health professionals how to build self-monitoring as a trainable skill—not a sticker chart, not a punishment, and not a “catch them when they're already melting down” plan.You'll learn how to start with behaviours kids already know (think: a task they can do on autopilot), set a clear target using Dr. Caroline's SOAP criteria, create a simple tracking system, and use cues like timers or classroom chimes to help kids “pause and check.” You'll also hear how to reinforce the right thing early on: accurate awareness, even when the child wasn't on task.If you support kids with ADHD, anxiety, big feelings, classroom disruptions, or sibling conflict, this episode gives you practical language, ready-to-use examples, and a step-by-step way to grow independence—without nagging, shame, or power struggles.Homework activities for adults (plus resources to prep)Homework A: Pick the “easy win” targetChoose a behaviour during a task the child already knows well (not new learning).Write the target using SOAP:Specific: exactly what they will doObservable: you can see/hear itAppropriate: fits the settingPersonal: fits the child's levelResource: a one-sentence target + a short list of examples/non-examples.Homework B: Build a simple self-monitoring formPick ONE method:Checklist (multi-step tasks like chores/writing)Rating scale (how well did I stay in my seat?)Tally count (each time I raised my hand)Resource: a paper tracking card or a simple note page; add smiley faces/stickers for younger kids.Homework C: Add a cueUse a timer, smartwatch, chime, or an adult signal (thumbs up).Start frequent (short intervals), then stretch it out gradually.Resource: phone timer or classroom chime; choose a cue word (“focus check,” “chore check”).Homework D: Reinforce accuracy, not perfectionWhen the cue goes off, compare adult rating + child rating.Reward matching ratings, even if the child marked “No, I wasn't on track.”Resource: a small, immediate reinforcer list (attention, short break, points, sticker, choice).Homework E: Baseline + graph (optional, powerful)Track the behaviour for 3–5 occasions across several days.Graph it so the child can see progress.Resource: a simple bar chart on paper, or dots on a chart.Enjoying the show? Help out by rating this podcast on Apple to help others get access to this information too! apple.co/3ysFijh Follow Dr. Caroline YouTube: https://www.youtube.com/@dr.carolinebuzankoIG: https://www.instagram.com/dr.carolinebuzanko/ LinkedIn: https://ca.linkedin.com/in/dr-caroline-buzankoFacebook: https://www.facebook.com/DrCarolineBuzanko/Website: https://drcarolinebuzanko.com/Resources: https://drcarolinebuzanko.com/resources/articles-child-resilience-well-being-psychology/ Business inquiries: https://korupsychology.ca/contact-us/Want to learn more about helping kids strengthen their emotion regulation skills and problem-solving brains while boosting their confidence, independence, and resilience? Check out my many training opportunities! https://drcarolinebuzanko.com/upcoming-events/

Greetings from SXSW, where I'm learning, recording, and eating... You'll hear all about it soon... For now, enjoy this short, sweet, and geeky bonus episode.Have you seen that weird graph about all the jobs that AI is going to kill? It looks like an ink blot or a Rorschach test... It's from an Anthropic report and it's really making the rounds. If you follow tech stuff on social media you've probably seen it. The report is interested, but I'm convinced people are only sharing it because the graph looks cool and people will think they're smart if they share this inscrutable data visualization... Anyway, here's a very short excerpt of my upcoming interview with Paul Ford (@ftrain), one of my favorite tech writers and the founder of Aboard. He and I took a break from talking AI and such to geek out on this data visualization and why it's so bad, plus I told him about how I used AI to make my own version of a radar graph (about how many, and which kinds of, tacos I will and could theoretically eat in Austin). ---Subscribe to the Future Around & Find Out newsletter!

In this episode, Sid Pardeshi, co-founder and CTO of Blitzy, joins us to discuss building autonomous development systems able to deliver production-ready software at enterprise scale. Sid contrasts AI-assisted coding with end-to-end autonomy, arguing that “code is a commodity” and acceptance is the real metric—security, standards, tests, and maintainability included. We explore Blitzy's hybrid graph-plus-vector approach, which grounds agents and combines semantic signals with keyword search to navigate large repositories efficiently. Sid breaks down context and agent engineering, how effective context windows have plateaued, and why dynamic agent personas, tool selection, and model-specific prompting matter at scale. He details their orchestration of large swarms of AI agents to collaboratively analyze codebases, plan tasks, and execute complex tasks in parallel. We also dig into why Agents.md and flat memories break down, storing feedback in the knowledge graph, and building real-world evals beyond leaderboards to choose the right model for each task. The complete show notes for this episode can be found at https://twimlai.com/go/763.

In this episode of Screaming in the Cloud, host Corey Quinn sits down with Roi Lipman, CTO and co-founder of Falco DB, to unpack the evolving role of graph databases in a world overflowing with data stores. Roi shares his journey from building RedisGraph at Redis to spinning it out into Falco DB, along with his enduring love of the C programming language (dad jokes included). The conversation explores why graph databases remain niche, but powerful, especially for pathfinding problems like supply chains and access management, how vector search became a feature rather than a standalone database, and what AI-assisted development means for modern engineering. Along the way, they tackle open source sustainability, Rust rewrites, AI-generated pull request chaos, and the looming question of where the next generation of senior engineers will come from.Highlights: (00:00) C Language(00:27) Welcome(01:18) Database Landscape Overview(03:17) Why Graph Databases Matter(07:25) AI Built Apps and Data Choices(10:29) How FalcoDB Fits In(12:20) Vector Search as a Feature(16:48) FalcoDB Origin Story(19:54) Open Source Business and Rust Rewrite(25:23) Toy Graph Problems and Closing ThoughtsSponsored by: duckbillhq.com

The reception to our recent post on Code Reviews has been strong. Catch up!Amid a maelstrom of discussion on whether or not AI is killing SaaS, one of the top publicly listed SaaS companies in the world has just reported record revenues, clearing well over $1.1B in ARR for the first time with a 28% margin. As we comment on the pod, Aaron Levie is the rare public company CEO equally at home in both worlds of Silicon Valley and Wall Street/Main Street, by day helping 70% of the Fortune 500 with their Enterprise Advanced Suite, and yet by night is often found in the basements of early startups and tweeting viral insights about the future of agents.Now that both Cursor, Cloudflare, Perplexity, Anthropic and more have made Filesystems and Sandboxes and various forms of “Just Give the Agent a Box” cool (not just cool; it is now one of the single hottest areas in AI infrastructure growing 100% MoM), we find it a delightfully appropriate time to do the episode with the OG CEO who has been giving humans and computers Boxes since he was a college dropout pitching VCs at a Michael Arrington house party.Enjoy our special pod, with fan favorite returning guest/guest cohost Jeff Huber!Note: We didn't directly discuss the AI vs SaaS debate - Aaron has done many, many, many other podcasts on that, and you should read his definitive essay on it. Most commentators do not understand SaaS businesses because they have never scaled one themselves, and deeply reflected on what the true value proposition of SaaS is.We also discuss Your Company is a Filesystem:We also shoutout CTO Ben Kus' and the AI team, who talked about the technical architecture and will return for AIE WF 2026.Full Video EpisodeTimestamps* 00:00 Adapting Work for Agents* 01:29 Why Every Agent Needs a Box* 04:38 Agent Governance and Identity* 11:28 Why Coding Agents Took Off First* 21:42 Context Engineering and Search Limits* 31:29 Inside Agent Evals* 33:23 Industries and Datasets* 35:22 Building the Agent Team* 38:50 Read Write Agent Workflows* 41:54 Docs Graphs and Founder Mode* 55:38 Token FOMO Culture* 56:31 Production Function Secrets* 01:01:08 Film Roots to Box* 01:03:38 AI Future of Movies* 01:06:47 Media DevRel and EngineeringTranscriptAdapting Work for AgentsAaron Levie: Like you don't write code, you talk to an agent and it goes and does it for you, and you may be at best review it. That's even probably like, like largely not even what you're doing. What's happening is we are changing our work to make the agents effective. In that model, the agent didn't really adapt to how we work.We basically adapted to how the agent works. All of the economy has to go through that exact same evolution. Right now, it's a huge asset and an advantage for the teams that do it early and that are kinda wired into doing this ‘cause you'll see compounding returns. But that's just gonna take a while for most companies to actually go and get this deployed.swyx: Welcome to the Lane Space Pod. We're back in the chroma studio with uh, chroma, CEO, Jeff Hoover. Welcome returning guest now guest host.Aaron Levie: It's a pleasure. Wow. How'd you get upgraded to, uh, to that?swyx: Because he's like the perfect guy to be guest those for you.Aaron Levie: That makes sense actually, for We love context. We, we both really love context le we really do.We really do.swyx: Uh, and we're here with, uh, Aaron Levy. Welcome.Aaron Levie: Thank you. Good to, uh, good to be [00:01:00] here.swyx: Uh, yeah. So we've all met offline and like chatted a little bit, but like, it's always nice to get these things in person and conversation. Yeah. You just started off with so much energy. You're, you're super excited about agents.I loveAaron Levie: agents.swyx: Yeah. Open claw. Just got by, got bought by OpenAI. No, not bought, but you know, you know what I mean?Aaron Levie: Some, some, you know, acquihire. Executiveswyx: hire.Aaron Levie: Executive hire. Okay. Executive hire. Say,swyx: hey, that's my term. Okay. Um, what are you pounding the table on on agents? You have so many insightful tweets.Why Every Agent Needs a BoxAaron Levie: Well, the thing that, that we get super excited by that I think is probably, you know, should be relatively obvious is we've, we've built a platform to help enterprises manage their files and their, their corporate files and the permissions of who has access to those files and the sharing collaboration of those files.All of those files contain really, really important information for the enterprise. It might have your contracts, it might have your research materials, it might have marketing information, it might have your memos. All that data obviously has, you know, predominantly been used by humans. [00:02:00] But there's been one really interesting problem, which is that, you know, humans only really work with their files during an active engagement with them, and they kind of go away and you don't really see them for a long time.And all of a sudden, uh, with the power of AI and AI agents, all of that data becomes extremely relevant as this ongoing source of, of answers to new questions of data that will transform into, into something else that, that produces value in your organization. It, it contains the answer to the new employee that's onboarding, that needs to ramp up on a project.Um, it contains the answer to the right thing to sell a customer when you're having a conversation to them, with them contains the roadmap information that's gonna produce the next feature. So all that data. That previously we've been just sort of storing and, and you know, occasionally forgetting about, ‘cause we're only working on the new active stuff.All of that information becomes valuable to the enterprise and it's gonna become extremely valuable to end users because now they can have agents go find what they're looking for and produce new, new [00:03:00] value and new data on that information. And it's gonna become incredibly valuable to agents because agents can roam around and do a bunch of work and they're gonna need access to that data as well.And um, and you know, sometimes that will be an agent that is sort of working on behalf of, of, of you and, and effectively as you as and, and they are kind of accessing all of the same information that you have access to and, and operating as you in the system. And then sometimes there's gonna be agents that are just.Effectively autonomous and kind of run on their own and, and you're gonna collaborate and work with them kind of like you did another person. Open Claw being the most recent and maybe first real sort of, you know, kind of, you know, up updating everybody's, you know, views of this landscape version of, of what that could look like, which is, okay, I have an agent.It's on its own system, it's on its own computer, it has access to its own tools. I probably don't give it access to my entire life. I probably communicate with it like I would an assistant or a colleague and then it, it sort of has this sandbox environment. So all of that has massive implications for a platform that manage that [00:04:00] enterprise data.We think it's gonna just transform how we work with all of the enterprise content that we work with, and we just have to make sure we're building the right platform to support that.swyx: The sort of shorthand I put it is as people build agents, everybody's just realizing that every agent needs a box. Yes.And it's nice to be called box and just give everyone a box.Aaron Levie: Hey, I if I, you know, if we can make that go viral, uh, like I, I think that that terminology, I, that's theswyx: tagline. Every agentAaron Levie: needs a box. Every agent needs a box. If we can make that the headline of this, I'm fine with this. And that's the billboard I wanna like Yeah, exactly.Every agent needs a box. Um, I like it. Can we ship this? Like,swyx: okay, let's do it. Yeah.Aaron Levie: Uh, my work here is done and I got the value I needed outta this podcast Drinks.swyx: Yeah.Agent Governance and IdentityAaron Levie: But, but, um, but, but, you know, so the thing that we, we kind of think about is, um, is, you know, whether you think the number 10 x or a hundred x or whatever the number is, we're gonna have some order of magnitude more agents than people.That's inevitable. It has to happen. So then the question is, what is the infrastructure that's needed to make all those agents effective in the enterprise? Make sure that they are well governed. Make sure they're only doing [00:05:00] safe things on your information. Make sure that they're not getting exposed. The data that they shouldn't have access to.There's gonna be just incredibly spectacularly crazy security incidents that will happen with agents because you'll prompt, inject an agent and sort of find your way through the CRM system and pull out data that you shouldn't have access to. Oh, weJeff Huber: have God,Aaron Levie: right? I mean, that's just gonna happen all over the place, right?So, so then the thing is, is how do you make sure you have the right security, the permissions, the access controls, the data governance. Um, we actually don't yet exactly know in many cases how we're gonna regulate some of these agents, right? If you think about an agent in financial services, does it have the exact same financial sort of, uh, requirements that a human did?Or is it, is the risk fully on the human that was interacting or created the agent? All open questions, but no matter what, there's gonna need to be a layer that manages the, the data they have access to, the workflows that they're involved in, pulling up data from multiple systems. This is the new infrastructure opportunity in the era of agents.swyx: You have a piece on agent identities, [00:06:00] which I think was today, um, which I think a lot of breaking news, the security, security people are talking about, right? Like you basically, I, I always think of this as like, well you need the human you and then there you need the agent. YouAaron Levie: Yes.swyx: And uh, well, I don't know if it's that simple, but is box going to have an opinion on that or you're just gonna be like, well we're just the sort of the, the source layer.Yeah. Let's Okta of zero handle that.Aaron Levie: I think we're gonna have an opinion and we will work with generally wherever the contours of the market end up. Um, and the reason that we're gonna have an opinion more than other topics probably is because one of the biggest use cases for why your agent might need it, an identity is for file system access.So thus we have to kind of think about this pretty deeply. And I think, uh, unless you're like in our world thinking about this particular problem all day long, it might be, you know, like, why is this such a big deal? And the reason why it's a really big deal is because sometimes sort of say, well just give the agent an, an account on the system and it just treats, treat it like every other type of user on the system.The [00:07:00] problem is, is that I as Aaron don't really have any responsibility over anybody else's box account in our organization. I can't see the box account of any other employee that I work with. I am not liable for anything that they do. And they have, I have, I have, you know, strict privacy requirements on everything that they're able to, you know, that, that, that they work on.Agents don't have that, you know, don't have those properties. The person who creates the agent probably is gonna, for the foreseeable future, take on a lot of the liability of what that agent does. That agent doesn't deserve any privacy because, because it's, you know, it can't fully be autonomously operated and it doesn't have any legal, you know, kind of, you know, responsibility.So thus you can't just be like, oh, well I'll just create a bunch of accounts and then I'll, I'll kind of work with that agent and I'll talk to it occasionally. Like you need oversight of that. And so then the question is, how do you have a world where the agent, sometimes you have oversight of, but what if that agent goes and works with other people?That person over there is collaborating with the agent on something you shouldn't have [00:08:00] access to what they're doing. So we have all of these new boundaries that we're gonna have to figure out of, of, you know, it's really, really easy. So far we've been in, in easy mode. We've hit the easy button with ai, which is the agent just is you.And when you're in quad code and you're in cursor, and you're in Codex, you're just, the agent is you. You're offing into your services. It can do everything you can do. That's the easy mode. The hard mode is agents are kind of running on their own. People check in with them occasionally, they're doing things autonomously.How do you give them access to resources in the enterprise and not dramatically increased the security risk and the risk that you might expose the wrong thing to somebody. These are all the new problems that we have to get solved. I like the identity layer and, and identity vendors as being a solution to that, but we'll, we'll need some opinions as well because so many of the use cases are these collaborative file system use cases, which is how do I give it an agent, a subset of my data?Give it its own workspace as well. ‘cause it's gonna need to store off its own information that would be relevant for it. And how do I have the right oversight into that? [00:09:00]Jeff Huber: One thing, which, um, I think is kind interesting, think about is that you know, how humans work, right? Like I may not also just like give you access to the whole file.I might like sit next to you and like scroll to this like one part of the file and just show you that like one part and like, you know,swyx: partial file access.Jeff Huber: I'm just saying I think like our, like RA does seem to be dead, right? Like you wanna say something is dead uhhuh probably RA is dead. And uh, like the auth story to me seems like incredibly unsolved and unaddressed by like the existing state of like AI vendors.ButAaron Levie: yeah, I think, um, we're, I mean you're taking obviously really to level limit that we probably need to solve for. Yeah. And we built an access control system that was, was kind of like, you know, its own little world for, for a long time. And um, and the idea was this, it's a many to many collaboration system where I can give you any part of the file system.And it's a waterfall model. So if I give you higher up in the, in the, in the system, you get everything below. And that, that kind of created immense flexibility because I can kind of point you to any layer in the, in the tree, but then you're gonna get access to everything kind of below it. And that [00:10:00] mostly is, is working in this, in this world.But you do have to manage this issue, which is how do I create an agent that has access to some of my stuff and somebody else's stuff as well. Mm-hmm. And which parts do I get to look at as the creator of the agent? And, and these are just brand new problems? Yeah. Crazy. And humans, when there was a human there that was really easy to do.Like, like if the three of us were all sharing, there'd be a Venn diagram where we'd have an overlapping set of things we've shared, but then we'd have our own ways that we shared with each other. In an agent world, somebody needs to take responsibility for what that agent has access to and what they're working on.These are like the, some of the most probably, you know, boring problems for 98% of people on, on the internet, but they will be the problems that are the difference between can you actually have autonomous agents in an enterprise contextswyx: Yeah.Aaron Levie: That are not leaking your data constantly.swyx: No. Like, I mean, you know, I run a very, very small company for my conference and like we already have data sensitivity issues.Yes. And some of my team members cannot see Yes. Uh, the others and like, I can't imagine what it's like to run a Fortune 500 and like, you have to [00:11:00] worry about this. I'm just kinda curious, like you, you talked to a lot like, like 70, 80% of your cus uh, of the Fortune 500, your customers.Aaron Levie: Yep. 67%. Just so we're being verySEswyx: precise.So Yeah. I'm notAaron Levie: Okay. Okay.swyx: Something I'm rounding up. Yes. Round up. I'm projecting to, forAaron Levie: the government.swyx: I'm projecting to the end of the year.Aaron Levie: Okay.swyx: There you go.Aaron Levie: You do make it sound like, like we, we, well we've gotta be on this. Like we're, we're taking way too long to get to 80%. Well,swyx: no, I mean, so like. How are they approaching it?Right? Because you're, you don't have a, you don't have a final answer yet.Why Coding Agents Took Off FirstAaron Levie: Well, okay, so, so this is actually, this is the stark reality that like, unfortunately is the kinda like pouring the water on the party a little bit.swyx: Yes.Aaron Levie: We all in Silicon Valley are like, have the absolute best conditions possible for AI ever.And I think we all saw the dke, you know, kind of Dario podcast and this idea of AI coding. Why is that taken off? And, and we're not yet fully seeing it everywhere else. Well, look, if you just like enumerated the list of properties that AI coding has and then compared it to other [00:12:00] knowledge work, let's just, let's just go through a few of them.Generally speaking, you bring on a new engineer, they have access to a large swath of the code base. Like, there's like very, like you, just, like new engineer comes on, they can just go and find the, the, the stuff that they, they need to work with. It's a fully text in text out. Medium. It's only, it's just gonna be text at the end of the day.So it's like really great from a, from just a, uh, you know, kinda what the agent can work with. Obviously the models are super trained on that dataset. The labs themselves have a really strong, kind of self-reinforcing positive flywheel of why they need to do, you know, agent coding deeply. So then you get just better tooling, better services.The actual developers of the AI are daily users of the, of the thing that they're we're working on versus like the, you know, probably there's only like seven Claude Cowork legal plugin users at Anthropic any given day, but there's like a couple thousand Claude code and you know, users every single day.So just like, think about which one are they getting more feedback on. All day long. So you just go through this list. You have a, you know, everybody who's a [00:13:00] developer by definition is technical so they can go install the latest thing. We're all generally online, or at least, you know, kinda the weird ones are, and we're all talking to each other, sharing best practices, like that's like already eight differences.Versus the rest of the economy. Every other part of the economy has like, like six to seven headwinds relative to that list. You go into a company, you're a banker in financial services, you have access to like a, a tiny little subset of the total data that's gonna be relevant to do your job. And you're have to start to go and talk to a bunch of people to get the right data to do your job because Sally didn't add you to that deal room, you know, folder.And that that, you know, the information is actually in a completely different organization that you now have to go in and, and sort of run into. And it's like you have this endless list of access controls and security. As, as you talked about, you have a medium, which is not, it's not just text, right? You have, you have a zoom call that, that you're getting all of the requirements from the customer.You have a lot of in-person conversations and you're doing in-person sales and like how do you ever [00:14:00] digitize all of that information? Um, you know, I think a lot of people got upset with this idea that the code base has all the context, um, that I don't know if you follow, you know, did you follow some of that conversation that that went viral?Is like, you know, it's not that simple that, that the code base doesn't have all the knowledge, but like it's a lot, you're a lot better off than you are with other areas of knowledge work. Like you, we like, we like have documentation practices, you write specifications. Those things don't exist for like 80% of work that happens in the enterprise.That's the divide that we have, which is, which is AI coding has, has just fully, you know, where we've reached escape velocity of how powerful this stuff is, and then we're gonna have to find a way to bring that same energy and momentum, but to all these other areas of knowledge work. Where the tools aren't there, the data's not set up to be there.The access controls don't make it that easy. The context engineering is an incredibly hard problem because again, you have access control challenges, you have different data formats. You have end users that are gonna need to kind of be kind of trained through this as opposed to their adopting [00:15:00] these tools in their free time.That's where the Fortune 500 is. And so we, I think, you know, have to be prepared as an industry where we are gonna be on a multi-year march to, to be able to bring agents to the enterprise for these workflows. And I think probably the, the thing that we've learned most in coding that, that the rest of the world is not yet, I think ready for, I mean, we're, they'll, they'll have to be ready for it because it's just gonna inevitably happen is I think in coding.What, what's interesting is if you think about the practice of coding today versus two years ago. It's probably the most changed workflow in maybe the history of time from the amount of time it's changed, right? Yeah. Like, like has any, has any workflow in the entire economy changed that quickly in terms of the amount of change?I just, you know, at least in any knowledge worker workflow, there's like very rarely been an event where one piece of technology and work practice has so fundamentally, you know, changed, changed what you do. Like you don't write code, you talk to an agent and it goes and [00:16:00] does it for you, and you may be at best review it.And even that's even probably like, like largely not even what you're doing. What's happening is we are changing our work to make the agents effective. In that model, the agent didn't really adapt to how we work. We basically adapted to how the agent works. Mm-hmm. All of the economy has to go through that exact same evolution.The rest of the economy is gonna have to update its workflows to make agents effective. And to give agents the context that they need and to actually figure out what kind of prompting works and to figure out how do you ensure that the agent has the right access to information to be able to execute on its work.I, you know, this is not the panacea that people were hoping for, of the agent drops in, just automates your life. Like you have to basically re-engineer your workflow to get the most out of agents and, uh, and that, that's just gonna take, you know, multiple years across the economy. Right now it's a huge asset and an advantage for the teams that do it early and that are kinda wired into doing this.‘cause [00:17:00] you'll see compounding returns, but that's just gonna take a while for most companies to actually go and get this deployed.swyx: I love, I love pushing back. I think that. That is what a lot of technology consultants love to hear this sort of thing, right? Yeah, yeah, yeah. First to, to embrace the ai. Yes. To get to the promised land, you must pay me so much money to a hundred percent to adopt the prescribed way of, uh, conforming to the agents.Yes. And I worry that you will be eclipsed by someone else who says, no, come as you are.Aaron Levie: Yeah.swyx: And we'll meet you where you are.Aaron Levie: And, and, and and what was the thing that went viral a week ago? OpenAI probably, uh, is hiring F Dees. Yeah. Uh, to go into the enterprise. Yeah. Yeah. And then philanthropic is embedded at Goldman Sachs.Yeah. So if the labs are having to do this, if, if the labs have decided that they need to hire FDE and professional services, then I think that's a pretty clear indication that this, there's no easy mode of workflow transformation. Yeah. Yeah. So, so to your point, I think actually this is a market opportunity for, you know, new professional services and consulting [00:18:00] firms that are like Agent Build and they, and they kind of, you know, go into organizations and they figure out how to re-engineer your workflows to make them more agent ready and get your data into the right format and, you know, reconstruct your business process.So you're, you're not doing most of the work. You're telling agents how to do the work and then you're reviewing it. But I haven't seen the thing that can just drop in and, and kinda let you not go through those changes.swyx: I don't know how that kind of sales pitch goes over. Yeah. You know, you're, you're saying things like, well, in my sort of nice beautiful walled garden, here's, there's, uh, because here's this, here's this beautiful box account that has everything.Yes. And I'm like, well, most, most real life is extremely messy. Sure. And like, poorly named and there duplicate this outdated s**tAaron Levie: a hundred percent. And so No, no, a hundred percent. And so this is actually No. So, so this is, I mean, we agree that, that getting to the beautiful garden is gonna be tough.swyx: Yeah.Aaron Levie: There's also the other end of the spectrum where I, I just like, it's a technical impossibility to solve. The agent is, is truly cannot get enough context to make the right decision in, in the, in the incredibly messy land. Like there's [00:19:00] no a GI that will solve that. So, so we're gonna have to kind of land in somewhere in between, which is like we all collectively get better at.Documentation practices and, and having authoritative relatively up-to-date information and putting it in the right place like agents will, will certainly cause us to be much better organized around how we work with our information, simply because the severity of the agent pulling the wrong data will be too high and the productivity gain of that you'll miss out on by not doing this will be too high as well, that you, that your competition will just do it and they'll just have higher velocity.So, uh, and, and we, we see this a lot firsthand. So we, we build a series of agents internally that they can kind of have access to your full box account and go off and you give it a task and it can go find whatever information you're looking for and work with. And, you know, thank God for the model progress, but like, if, if you gave that task to an agent.Nine months ago, you're just gonna get lots of bogus answers because it's gonna, it's gonna say, Hey, here's, here are fi [00:20:00] five, you know, documents that all kind of smell like the right thing. And I'm gonna, but I, but you're, you're putting me on the clock. ‘cause my assistant prompt says like, you know, be pretty smart, but also try and respond to the user and it's gonna respond.And it's like, ah, it got the wrong document. And then you do that once or twice as a knowledge worker and you're just neverswyx: again,Aaron Levie: never again. You're just like done with the system.swyx: Yeah. It doesn't work.Aaron Levie: It doesn't work. And so, you know, Opus four six and Gemini three one Pro and you know, whatever the latest five 3G BT will be, like, those things are getting better and better and it's using better judgment.And this sort of like the, all of these updates to the agentic tool and search systems are, are, we're seeing, we're seeing very real progress where the agent. Kind of can, can almost smell some things a little bit fishy when it's getting, you know, we, we have this process where we, we have it go fan out, do a bunch of searches, pull up a bunch of data, and then it has to sort of do its own ranking of, you know, what are the right documents that, that it should be working with.And again, like, you know, the intelligence level of a model six months ago, [00:21:00] it'd be just throwing a dart at like, I'm just, I'm gonna grab these seven files and I, I pray, I hope that that's the right answer. And something like an opus first four five, and now four six is like, oh, it's like, no, that one doesn't seem right relative to this question because I'm seeing some signal that is making that, you know, that's contradicting the document where it would normally be in the tree and who should have access.Like it's doing all of that kind of work for you. But like, it still doesn't work if you just have a total wasteland of data. Like, it's just not, it's just not possible. Partly ‘cause a human wouldn't even be able to do it. So basically if a, if a really, really smart human. Could not do that task in five or 10 minutes for a search retrieval type task.Look, you know, your agent's not gonna be able to do it any better. You see this all day long. SoContext Engineering and Search Limitsswyx: this touches on a thing that just passionate about it was just context engineering. I, I'm just gonna let you ramble or riff on, on context engineering. If, if, if there's anything like he, he did really good work on context fraud, which has really taken over as like the term that people use and the referenceAaron Levie: a hundred percent.We, we all we think about is, is the context rob problem. [00:22:00]Jeff Huber: Yeah, there's certainly a lot of like ranking considerations. Gentech surgery think is incredibly promising. Um, yeah, I was trying to generate a question though. I think I have a question right now. Swyx.Aaron Levie: Yeah, no, but like, like I think there was this moment, um, you know, like, I don't know, two years ago before, before we knew like where the, the gotchas were gonna be in ai and I think someone was like, was like, well, infinite context windows will just solve all of these problems and ‘cause you'll just, you'll just give the context window like all the data and.It's just like, okay, I mean, maybe in 2035, like this is a viable solution. First of all, it, it would just, it would just simply cost too much. Like we just can't give the model like the 5,000 documents that might be relevant and it's gonna read them all. And I've seen enough to, to start believing in crazy stuff.So like, I'm willing to just say, sure. Like in, in 10 years from now,swyx: never say, never, never.Aaron Levie: In, in 10 years from now, we'll have infinite context windows at, at a thousandth of the price of today. Like, let's just like believe that that's possible, but Right. We're in reality today. So today we have a context engineering [00:23:00] problem, which is, I got, I got, you know, 200,000 tokens that I can work with, or prob, I don't even know what the latest graph is before, like massive degradation.16. Okay. I have 60,000 tokens that I get to work with where I'm gonna get accurate information. That's not a lot of tokens for a corpus of 10 million documents that a knowledge worker might have across all of the teams and all the projects and all the people they work with. I have, I have 10 million documents.Which, you know, maybe is times five pages per document or something like that. I'm at 50 million pages of information and I have 60,000 tokens. Like, holy s**t. Yeah. This is like, how do I bridge the 50 million pages of information with, you know, the couple hundred that I get to work with in that, in that token window.Yeah. This is like, this is like such an interesting problem and that's why actually so much work is actually like, just like search systems and the databases and that layer has to just get so locked in, but models getting better and importantly [00:24:00] knowing when they've done a search, they found the wrong thing, they go back, they check their work, they, they find a way to balance sort of appeasing the user versus double checking.We have this one, we have this one test case where we ask the agent to go find. 10 pieces of information.swyx: Is this the complex work eval?Aaron Levie: Uh, this is actually not in the eval. This is, this is sort of just like we have a bunch of different, we have a bunch of internal benchmark kind of scenarios. Every time we, we update our agent, we have one, which is, I ask it to find all of our office addresses, and I give it the list of 10 offices that we have.And there's not one document that has this, maybe there should be, that would be a great example of the kind of thing that like maybe over time companies start to, you know, have these sort of like, what are the canonical, you know, kind of key areas of knowledge that we need to have. We don't seem to have this one document that says, here are all of our offices.We have a bunch of documents that have like, here's the New York office and whatever. So you task this agent and you, you get, you say, I need the addresses for these 10 offices. Okay. And by the way, if you do this on any, you know, [00:25:00] public chat model, the same outcome is gonna happen. But for a different kind of query, you give it, you say, I need these 10 addresses.How many times should the agent go and do its search before it decides whether or not, there's just no answer to this question. Often, and especially the, the, let's say lower tier models, it'll come back and it'll give you six of the 10 addresses. And it'll, and I'll just say I couldn't find the otherswyx: four.It, it doesn't know what It doesn't know. ItAaron Levie: doesn't know what It doesn't know. Yeah. So the model is just like, like when should it stop? When should it stop doing? Like should it, should it do that task for literally an hour and just keep cranking through? Maybe I actually made up an office location and it doesn't know that I made it up and I didn't even know that I made it up.Like, should it just keep, re should it read every single file in your entire box account until it, until it should exhaust every single piece of information.swyx: Expensive.Aaron Levie: These are the new problems that we have. So, you know, something like, let's say a new opus model is sort of like, okay, I'm gonna try these types of queries.I didn't get exactly what I wanted. I'm gonna try again. I'm gonna, at [00:26:00] some point I'm gonna stop searching. ‘cause I've determined that that no amount of searching is gonna solve this problem. I'm just not able to do it. And that judgment is like a really new thing that the model needs to be able to have.It's like, when should it give up on a task? ‘cause, ‘cause you just don't, it's a can't find the thing. That's the real world of knowledge, work problems. And this is the stuff that the coding agents don't have to deal with. Because they, it just doesn't like, like you're not usually asking it about, you're, you're always creating net new information coming right outta the model for the most part.Obviously it has to know about your code base and your specs and your documentation, but, but when you deploy an agent on all of your data that now you have all of these new problems that you're dealing withJeff Huber: our, uh, follow follow-up research to context ride is actually on a genetic search. Ah. Um, and we've like right, sort of stress tested like frontier models and their ability to search.Um, and they're not actually that good at searching. Right. Uh, so you're sort of highlighting this like explore, exploit.swyx: You're just say, Debbie, Donna say everything doesn't work. Like,Aaron Levie: well,Jeff Huber: somebody has to be,Aaron Levie: um, can I just throw out one more thing? Yeah. That is different from coding and, and the rest [00:27:00] of the knowledge work that I, I failed to mention.So one other kind of key point is, is that, you know, at the end of the day. Whether you believe we're in a slop apocalypse or, or whatever. At the end of the day, if you, if you build a working product at the end of, if you, if you've built a working solution that is ultimately what the customer is paying for, like whether I have a lot of slop, a little slop or whatever, I'm sure there's lots of code bases we could go into in enterprise software companies where it's like just crazy slop that humans did over a 20 year period, but the end customer just gets this little interface.They can, they can type into it, it does its thing. Knowledge work, uh, doesn't have that property. If I have an AI model, go generate a contract and I generate a contract 20 times and, you know, all 20 times it's just 3% different and like that I, that, that kind of lop introduces all new kinds of risk for my organization that the code version of that LOP didn't, didn't introduce.These are, and so like, so how do you constrain these models to just the part that you want [00:28:00] them to work on and just do the thing that you want them to do? And, and, you know, in engineering, we don't, you can't be disbarred as an engineer, but you could be disbarred as a lawyer. Like you can do the wrong medical thing In healthcare, you, there's no, there's no equivalent to that of engineering.Like, doswyx: you want there to be, because I've considered softwareJeff Huber: engineer. What's that? Civil engineering there is, right? NotAaron Levie: software civil engineer. Sure. Oh yeah, for sure. But like in any of our companies, you like, you know, you'll be forgiven if you took down the site and, and we, we will do a rollback and you'll, you'll be in a meeting, but you have not been disbarred as an engineer.We don't, we don't change your, you know, your computer science, uh, blameJeff Huber: degree, this postmortem.Aaron Levie: Yeah, exactly. Exactly. So, so, uh, now maybe we collectively as an industry need to figure out like, what are you liable for? Not legally, but like in a, in a management sense, uh, of these agents. All sorts of interesting problems that, that, that, uh, that have to come out.But in knowledge work, that's the real hostile environments that we're operating in. Hmm.swyx: I do think like, uh, a lot of the last year's, 2025 story was the rise of coding agents and I think [00:29:00] 2026 story is definitely knowledge work agents. Yes. A hundredAaron Levie: percent.swyx: Right. Like that would, and I think open claw core work are just the beginning.Yes. Like it's, the next one's gonna just gonna be absolute craziness.Aaron Levie: It it is. And, and, uh, and it's gonna be, I mean, again, like this is gonna be this, this wave where we, we are gonna try and bring as many of the practices from coding because that, that will clearly be the forefront, which is tell an agent to go do something and has an access to a set of resources.You need to be responsible for reviewing it at the end of the process. That to me is the, is the kind of template that I just think goes across knowledge, work and odd. Cowork is a great example. Open Closet's a great example. You can kind of, sort of see what Codex could become over time. These are some, some really interesting kind of platforms that are emerging.swyx: Okay. Um, I wanted to, we touched on evals a little bit. You had, you had the report that you're gonna go bring up and then I was gonna go into like, uh, boxes, evals, but uh, go ahead. Talk about your genetic search thing.Jeff Huber: Yeah. Mostly I think kinda a few of the insights. It's like number one frontier model is not good at search.Humans have this [00:30:00] natural explore, exploit trade off where we kinda understand like when to stop doing something. Also, humans are pretty good at like forgetting actually, and like pruning their own context, whereas agents are not, and actually an agent in their kind of context history, if they knew something was bad and they even, you could see in the trace the reason you trace, Hey, that probably wasn't a good idea.If it's still in the trace, still in the context, they'll still do it again. Uhhuh. Uh, and so like, I think pruning is also gonna be like, really, it's already becoming a thing, right? But like, letting self prune the con windowsswyx: be a big deal. Yeah. So, so don't leave the mistake. Don't leave the mistake in there.Cut out the mistake but tell it that you made a mistake in the past and so it doesn't repeat it.Jeff Huber: Yeah. But like cut it out so it doesn't get like distracted by it again. ‘cause really, you know, what is so, so it will repeat its mistake just because it's been, it's inswyx: theJeff Huber: context. It'sAaron Levie: in the context so much.That's a few shot example. Even if it, yeah.Jeff Huber: It's like oh thisAaron Levie: is a great thing to go try even ifJeff Huber: it didn't work.Aaron Levie: Yeah,Jeff Huber: exactly.Aaron Levie: SoJeff Huber: there's like a bunch of stuff there. JustAaron Levie: Groundhogs Day inside these models. Yeah. I'm gonna go keep doing the same wrongJeff Huber: thing. Covering sense. I feel like, you know, some creator analogy you're trying like fit a manifold in latent space, which kind is doing break program synthesis, which is kinda one we think about we're doing right.Like, you know, certain [00:31:00] facts might be like sort of overly pitting it. There are certain, you know, sec sectors of latent space and so like plug clean space. Yeah. And, uh, andswyx: so we have a bell, our editor as a bell every time you say that. SoJeff Huber: you have, you have to like remove those, likeswyx: you shoulda a gong like TPN or something.IfJeff Huber: we gong, you either remove those links to like kinda give it the freedom, kind of do what you need to do. So, but yeah. We'll, we'll release more soon. That'sAaron Levie: awesome.Jeff Huber: That'll, that'll be cool.swyx: We're a cerebral podcast that people listen to us and, and sort of think really deep. So yeah, we try to keep it subtle.Okay. We try to keep it.Aaron Levie: Okay, fine.Inside Agent Evalsswyx: Um, you, you guys do, you guys do have EVs, you talked about your, your office thing, but, uh, you've been also promoting APEX agents and complex work. Uh, yeah, whatever you, wherever you wanna take this just Yeah. How youAaron Levie: Apex is, is obviously me, core's, uh, uh, kind of, um, agent eval.We, we supported that by sort of. Opening up some data for them around how we kind of see these, um, data workspaces in, in the, you know, kind of regular economy. So how do lawyers have a workspace? How do investment bankers have a workspace? What kind of data goes into those? And so we, [00:32:00] we partner with them on their, their apex eval.Our own, um, eval is, it's actually relatively straightforward. We have a, a set of, of documents in a, in a range of industries. We give the agent previously did this as a one shot test of just purely the model. And then we just realized we, we need to, based on where everything's going, it's just gotta be more agentic.So now it's a bit more of a test of both our harness and the model. And we have a rubric of a set of things that has to get right and we score it. Um, and you're just seeing, you know, these incredible jumps in almost every single model in its own family of, you know, opus four, um, you know, sonnet four six versus sonnet four five.swyx: Yeah. We have this up on screen.Aaron Levie: Okay, cool. So some, you're seeing it somewhere like. I, I forget the to, it was like 15 point jump, I think on the main, on the overall,swyx: yes.Aaron Levie: And it's just like, you know, these incredible leaps that, that are starting to happen. Um,swyx: and OP doesn't know any, like any, it's completely held out from op.Aaron Levie: This is not in any, there's no public data which has, you know, Ben benefits and this is just a private eval that we [00:33:00] do, and then we just happen to show it to, to the world. Hmm. So you can't, you can't train against it. And I think it's just as representative of. It's obviously reasoning capabilities, what it's doing at, at, you know, kind of test time, compute capabilities, thinking levels, all like the context rot issues.So many interesting, you know, kind of, uh, uh, capabilities that are, that are now improvingswyx: one sector that you have. That's interesting.Industries and Datasetsswyx: Uh, people are roughly familiar with healthcare and legal, but you have public sector in there.Aaron Levie: Yeah.swyx: Uh, what's that? Like, what, what, what is that?Aaron Levie: Yeah, and, and we actually test against, I dunno, maybe 10 industries.We, we end up usually just cutting a few that we think have interesting gains. All extras, won a lot of like government type documents. Um,swyx: what is that? What is it? Government type documents?Aaron Levie: Government filings. Like a taxswyx: return, likeAaron Levie: a probably not tax returns. It would be more of what would go the government be using, uh, as data.So, okay. Um, so think about research that, that type of, of, of data sets. And then we have financial services for things like data rooms and what would be in an investment prospectus. Uhhuh,swyx: that one you can dog food.Aaron Levie: Yeah, exactly. Exactly. Yes. Yes. [00:34:00] So, uh, so we, we run the models, um, in now, you know, more of an agent mode, but, but still with, with kinda limited capacity and just try and see like on a, like, for like basis, what are the improvements?And, and again, we just continue to be blown away by. How, how good these models are getting.swyx: Yeah, I mean, I think every serious AI company needs something like that where like, well, this is the work we do. Here's our company eval. Yeah. And if you don't have it, well, you're not a serious AI company.Aaron Levie: There's two dimensions, right?So there's, there's like, how are the models improving? And so which models should you either recommend a customer use, which one should you adopt? But then every single day, we're making changes to our agents. And you need to knowswyx: if you regressed,Aaron Levie: if you know. Yeah. You know, I've been fully convinced that the whole agent observability and eval space is gonna be a massive space.Um, super excited for what Braintrust is doing, excited for, you know, Lang Smith, all the things. And I think what you're going to, I mean, this is like every enter like literally every enterprise right now. It's like the AI companies are the customers of these tools. Every enterprise will have this. Yeah, you'll just [00:35:00] have to have an eval.Of all of your work and like, we'll, you'll have an eval of your RFP generation, you'll have an eval of your sales material creation. You'll have an eval of your, uh, invoice processing. And, and as you, you know, buy or use new agentic systems, you are gonna need to know like, what's the quality of your, of your pipeline.swyx: Yeah.Aaron Levie: Um, so huge, huge market with agent evals.swyx: Yeah.Building the Agent Teamswyx: And, and you know, I'm gonna shout out your, your team a bit, uh, your CTO, Ben, uh, did a great talk with us last year. Awesome. And he's gonna come back again. Oh, cool. For World's Fair.Aaron Levie: Yep.swyx: Just talk about your team, like brag a little bit. I think I, I think people take these eval numbers in pretty charts for granted, but No, there, I mean, there's, there's lots of really smart people at work during all this.Aaron Levie: Biggest shout out, uh, is we have a, we have a couple folks at Dya, uh, Sidarth, uh, that, that kind of run this. They're like a, you know, kind of tag tag team duo on our evals, Ben, our CTO, heavily involved Yasha, head of ai, uh, you know, a bunch of folks. And, um, evals is one part of the story. And then just like the full, you know, kind of AI.An agent team [00:36:00] is, uh, is a, is a pretty, you know, is core to this whole effort. So there's probably, I don't know, like maybe a few dozen people that are like the epicenter. And then you just have like layers and layers of, of kind of concentric circles of okay, then there's a search team that supports them and an infrastructure team that supports them.And it's starting to ripple through the entire company. But there's that kind of core agent team, um, that's a pretty, pretty close, uh, close knit group.swyx: The search team is separate from the infra team.Aaron Levie: I mean, we have like every, every layer of the stack we have to kind of do, except for just pure public cloud.Um, but um, you know, we, we store, I don't even know what our public numbers are in, you know, but like, you can just think about it as like a lot of data is, is stored in box. And so we have, and you have every layer of the, of the stack of, you know, how do you manage the data, the file system, the metadata system, the search system, just all of those components.And then they all are having to understand that now you've got this new customer. Which is the agent, and they've been building for two types of customers in the past. They've been building for users and they've been building for like applications. [00:37:00] And now you've got this new agent user, and it comes in with a difference of it, of property sometimes, like, hey, maybe sometimes we should do embeddings, an embedding based, you know, kind of search versus, you know, your, your typical semantic search.Like, it's just like you have to build the, the capabilities to support all of this. And we're testing stuff, throwing things away, something doesn't work and, and not relevant. It's like just, you know, total chaos. But all of those teams are supporting the agent team that is kind of coming up with its requirements of what, what do we need?swyx: Yeah. No, uh, we just came from, uh, fireside chat where you did, and you, you talked about how you're doing this. It's, it's kind of like an internal startup. Yeah. Within the broader company. The broader company's like 3000 people. Yeah. But you know, there's, there's a, this is a core team of like, well, here's the innovation center.Aaron Levie: Yeah.swyx: And like that every company kind of is run this way.Aaron Levie: Yeah. I wanna be sensitive. I don't call it the innovation center. Yeah. Only because I think everybody has to do innovation. Um, there, there's a part of the, the, the company that is, is sort of do or die for the agent wave.swyx: Yeah.Aaron Levie: And it only happens to be more of my focus simply because it's existential that [00:38:00] we get it right.swyx: Yeah.Aaron Levie: All of the supporting systems are necessary. All of the surrounding adjacent capabilities are necessary. Like the only reason we get to be a platform where you'd run an agent is because we have a security feature or a compliance feature, or a governance feature that, that some team is working on.But that's not gonna be the make or break of, of whether we get agents right. Like that already exists and we need to keep innovating there. I don't know what the right, exact precise number is, but it's not a thousand people and it's not 10 people. There's a number of people that are like the, the kind of like, you know, startup within the company that are the make or break on everything related to AI agents, you know, leveraging our platform and letting you work with your data.And that's where I spend a lot of my time, and Ben and Yosh and Diego and Teri, you know, these are just, you know, people that, that, you know, kind of across the team. Are working.swyx: Yeah. Amazing.Read Write Agent WorkflowsJeff Huber: How do you, how do you think about, I mean, you talked a lot about like kinda read workflows over your box data. Yep.Right. You know, gen search questions, queries, et cetera. But like, what about like, write or like authoring workflows?Aaron Levie: Yes. I've [00:39:00] already probably revealed too much actually now that I think about it. So, um, I've talked about whatever,Jeff Huber: whatever you can.Aaron Levie: Okay. It's just us. It's just us. Yeah. Okay. Of course, of course.So I, I guess I would just, uh, I'll make it a little bit conceptual, uh, because again, I've already, I've already said things that are not even ga but, but we've, we've kinda like danced around it publicly, so I, yeah, yeah. Okay. Just like, hopefully nobody watches this, um, episode. No.swyx: It's tidbits for the Heidi engaged to go figure out like what exactly, um, you know, is, is your sort of line of thinking.Sure. They can connect the dots.Aaron Levie: Yeah. So, so I would say that, that, uh, we, you know, as a, as a place where you have your enterprise content, there's a use case where I want to, you know, have an agent read that data and answer questions for me. And then there's a use case where I want the agent to create something.And use the file system to create something or store off data that it's working on, or be able to have, you know, various files that it's writing to about the work it's doing. So we do see it as a total read write. The harder problem has so far been the read only because, because again, you have that kind of like 10 [00:40:00] million to one ratio problem, whereas rights are a lot of, that's just gonna come from the model and, and we just like, we'll just put it in the file system and kinda use it.So it's a little bit of a technically easier problem, but the only part that's like, not necessarily technically hard, it is just like it's not yet perfected in the state of the ecosystem is, you know, building a beautiful PowerPoint presentation. It's still a hard problem for these models. Like, like we still, you know, like, like these formats are just, we're not built for.They'reswyx: working on it.Aaron Levie: They're, they're working on it. Everybody's working on it.swyx: Every launch is like, well, we do PowerPoint now.Aaron Levie: We're getting, yeah, getting a lot, getting a lot of better each time. But then you'll do this thing where you'll ask the update one slide and all of a sudden, like the fonts will be just like a little bit different, you know, on two of the slides, or it moved, you know, some shape over to the left a little bit.And again, these are the kind of things that, like in code, obviously you could really care about if you really care about, you know, how beautiful is the code, but at the end, user doesn't notice all those problems and file creation, the end user instantly sees it. You're [00:41:00] like, ah, like paragraph three, like, you literally just changed the font on me.Like it's a totally different font and like midway through the document. Mm-hmm. Those are the kind of things that you run into a lot of in the, in the content creation side. So, mm-hmm. We are gonna have native agents. That do all of those things, they'll be powered by the leading kind of models and labs.But the thing that I think is, is probably gonna be a much bigger idea over time is any agent on any system, again, using Box as a file system for its work, and in that kind of scenario, we don't necessarily care what it's putting in the file system. It could put its memory files, it could put its, you know, specification, you know, documents.It could put, you know, whatever its markdown files are, or it could, you know, generate PDFs. It's just like, it's a workspace that is, is sort of sandboxed off for its work. People can collaborate into it, it can share with other people. And, and so we, we were thinking a lot about what's the right, you know, kind of way to, to deliver that at scale.Docs Graphs and Founder Modeswyx: I wanted to come into sort of the sort of AI transformation or AI sort of, uh, operations things. [00:42:00] Um, one of the tweets that you, that you wanted to talk about, this is just me going through your tweets, by the way. Oh, okay. I mean, like, this is, you readAaron Levie: one by one,swyx: you're the, you're the easiest guest to prep for because you, you already have like, this is the, this is what I'm interested in.I'm like, okay, well, areAaron Levie: we gonna get to like, like February, January or something? Where are we in the, in the timelines? How far back are we going?swyx: Can you, can you describe boxes? A set of skills? Right? Like that, that's like, that's like one of the extremes of like, well if you, you just turn everything into a markdown file.Yeah. Then your agent can run your company. Uh, like you just have to write, find the right sequence of words toAaron Levie: Yes.swyx: To do it.Aaron Levie: Sorry, isthatswyx: the question? So I think the question is like, what if we documented everything? Yes. The way that you exactly said like,Aaron Levie: yes.swyx: Um, let's get all the Fortune five hundreds, uh, prepared for agents.Yes. And like, you know, everything's in golden and, and nicely filed away and everything. Yes. What's missing? Like, what's left, right? LikeAaron Levie: Yeah.swyx: You've, you've run your company for a decade. LikeAaron Levie: Yeah. I think the challenge is that, that that information changes a week later. And because something happened in the market for that [00:43:00] customer, or us as a company that now has to go get updated, and so these systems are living and breathing and they have to experience reality and updates to reality, which right now is probably gonna be humans, you know, kinda giving those, giving them the updates.And, you know, there is this piece about context graphs as as, uh, that kinda went very viral. Yeah. And I, I, I was like a, i, I, I thought it was super provocative. I agreed with many parts of it. I disagree with a few parts around. You know, it's not gonna be as easy as as just if we just had the agent traces, then we can finally do that work because there's just like, there's so much more other stuff that that's happening that, that we haven't been able to capture and digitize.And I think they actually represented that in the piece to be clear. But like there's just a lot of work, you know, that that has to, you just can't have only skills files, you know, for your company because it's just gonna be like, there's gonna be a lot of other stuff that happens. Yeah. Change over time.Yeah. Most companies are practically apprenticeships.swyx: Most companies are practically apprenticeships. LikeJeff Huber: every new employee who joins the team, [00:44:00] like you span one to three months. Like ramping them up.Aaron Levie: Yes. AllJeff Huber: that tat knowledgeAaron Levie: isJeff Huber: not written down.Aaron Levie: Yes.Jeff Huber: But like, it would have to be if you wanted to like give it to an Asian.Right. And so like that seems to me like to beAaron Levie: one is I think you're gonna see again a premium on companies that can document this. Mm-hmm. Much. There'll be a huge premium on that because, because you know, can you shorten that three month ramp cycle to a two week ramp cycle? That's an instant productivity gain.Can you re dramatically reduce rework in the organization because you've documented where all the stuff is and where the answers are. Can you make your average employee as good as your 90th percentile employee because you've captured the knowledge that's sort of in the heads of, of those top employees and make that available.So like you can see some very clear productivity benefits. Mm-hmm. If you had a company culture of making sure you know your information was captured, digitized, put in a format that was agent ready and then made available to agents to work with, and then you just, again, have this reality of like add a 10,000 person [00:45:00] company.Mapping that to the, you know, access structure of the company is just a hard problem. Is like, is like, yeah, well, you just, not every piece of information that's digitized can be shared to everybody. And so now you have to organize that in a way that actually works. There was a pretty good piece, um, this, this, uh, this piece called your company as a file is a file system.I, did you see that one?swyx: Nope.Aaron Levie: Uh, yes. You saw it. Yeah. And, and, uh, I actually be curious your thoughts on it. Um, like, like an interesting kind of like, we, we agree with it because, because that's how we see the world and, uh,swyx: okay. We, we have it up on screen. Oh,Aaron Levie: okay. Yeah. But, but it's all about basically like, you know, we've already, we, we, we already organized in this kind of like, you know, permission structure way.Uh, and, and these are the kind of, you know, natural ways that, that agents can now work with data. So it's kind of like this, this, you know, kind of interesting metaphor, but I do think companies will have to start to think about how they start to digitize more, more of that data. What was your take?Jeff Huber: Yeah, I mean, like the company's probably like an acid compliant file system.Aaron Levie: Uh,Jeff Huber: yeah. Which I'm guessing boxes, right? So, yeah. Yes.swyx: Yeah. [00:46:00]Jeff Huber: Which you have a great piece on, but,swyx: uh, yeah. Well, uh, I, I, my, my, my direction is a little bit like, I wanna rewind a little bit to the graph word you said that there, that's a magic trigger word for us. I always ask what's your take on knowledge graphs?Yeah. Uh, ‘cause every, especially at every data database person, I just wanna see what they think. There's been knowledge graphs, hype cycles, and you've seen it all. So.Aaron Levie: Hmm. I actually am not the expert in knowledge graphs, so, so that you might need toswyx: research, you don't need to be an expert. Yeah. I think it's just like, well, how, how seriously do people take it?Yeah. Like, is is, is there a lot of potential in the, in the HOVI?Aaron Levie: Uh, well, can I, can I, uh, understand first if it's, um, is this a loaded question in the sense of are you super pro, super con, super anti medium? Iswyx: see pro, I see pros and cons. Okay. Uh, but I, I think your opinion should be independent of mine.Aaron Levie: Yeah. No, no, totally. Yeah. I just want to see what I'm stepping into.swyx: No, I know. It's a, and it's a huge trigger word for a lot of people out Yeah. In our audience. And they're, they're trying to figure out why is that? Because whyAaron Levie: is this such aswyx: hot item for them? Because a lot of people get graph religion.And they're like, everything's a graph. Of course you have to represent it as a graph. Well, [00:47:00] how do you solve your knowledge? Um, changing over time? Well, it's a graph.Aaron Levie: Yeah.swyx: And, and I think there, there's that line of work and then there's, there's a lot of people who are like, well, you don't need it. And both are right.Aaron Levie: Yeah. And what do the people who say you don't need it, what are theyswyx: arguing for Mark down files. Oh, sure, sure. Simplicity.Aaron Levie: Yeah.swyx: Versus it's, it's structure versus less structure. Right. That's, that's all what it is. I do.Aaron Levie: I think the tricky thing is, um, is, is again, when this gets met with real humans, they're just going to their computer.They're just working with some people on Slack or teams. They're just sharing some data through a collaborative file system and Google Docs or Box or whatever. I certainly like the vision of most, most knowledge graph, you know, kind of futuristic kind of ways of thinking about it. Uh, it's just like, you know, it's 2026.We haven't seen it yet. Kind of play out as as, I mean, I remember. Do you remember the, um, in like, actually I don't, I don't even know how old you guys are, but I'll for, for to show my age. I remember 17 years ago, everybody thought enterprises would just run on [00:48:00] Wikis. Yeah. And, uh, confluence and, and not even, I mean, confluence actually took off for engineering for sure.Like unquestionably. But like, this was like everything would be in the w. And I think based on our, uh, our, uh, general style of, of, of what we were building, like we were just like, I don't know, people just like wanna workspace. They're gonna collaborate with other people.swyx: Exactly. Yeah. So you were, you were anti-knowledge graph.Aaron Levie: Not anti, not anti. Soswyx: not nonAaron Levie: I'm not, I'm not anti. ‘cause I think, I think your search system, I just think these are two systems that probably, but like, I'm, I'm not in any religious war. I don't want to be in anybody's YouTube comments on this. There's not a fight for me.swyx: We, we love YouTube comments. We're, we're, we're get into comments.Aaron Levie: Okay. Uh, but like, but I, I, it's mostly just a virtue of what we built. Yeah. And we just continued down that path. Yeah.swyx: Yeah.Aaron Levie: And, um, and that, that was what we pursued. But I'm not, this is not a, you know, kind of, this is not a, uh, it'sswyx: not existential for you. Great.Aaron Levie: We're happy to plug into somebody else's graph.We're happy to feed data into it. We're happy for [00:49:00] agents to, to talk to multiple systems. Not, not our fight.swyx: Yeah.Aaron Levie: But I need your answer. Yeah. Graphs or nerd Snipes is very effective nerd.swyx: See this is, this is one, one opinion and then I've,Jeff Huber: and I think that the actual graph structure is emergent in the mind of the agent.Ah, in the same way it is in the mind of the human. And that's a more powerful graph ‘cause it actually involved over time.swyx: So don't tell me how to graph. I'll, I'll figure it out myself. Exactly. Okay. All right. AndJeff Huber: what's yours?swyx: I like the, the Wiki approach. Uh, my, I'm actually

I sit down with Cody Schneider, growth engineer and co-founder of Graph, for a live, hands-on crash course in GTM (go-to-market) engineering powered by Claude Code. Cody walks through how he runs multiple AI agents simultaneously to handle everything from bulk Facebook ad creation and LinkedIn outreach to cold email campaigns and live data analysis — tasks that used to require a team of dozens. By the end of the episode, you'll have a full understanding of how to set up your own agent workflow, the specific tools involved, and why domain expertise paired with AI is the real competitive advantage right now. Cody's GTM Toolkit: AI/Agent Tools: Claude Code, Perplexity API, OpenAI Codex Marketing & Outreach: Instantly AI (cold email), Phantom Buster (LinkedIn scraping/automation), Apollo API (data enrichment), Million Verifier (email verification), Raphonic (podcast host scraping): Advertising: Facebook Ads API, Facebook Ads Library (competitor research), Nano Banana Pro (AI image generation), Kai AI (bulk image generation), HeyGen API (UGC/video generation) Infrastructure & Deployment: Railway.com (servers, on-the-fly databases/Postgres), Vercel (deployment) Data & Analytics: Graphed / Graphed MCP (data warehouse, live data feeds), Google Analytics 4 CRM & Communication: Salesforce (mentioned as comparison), Intercom, SendGrid API, Slack, Cal.com API Productivity & Design: Notion, Super Whisper (voice transcription), Claude Code front-end design skill, HTML to Canvas (for converting React components to PNGs) Timestamps 00:00 – Intro 02:02 – What Is GTM Engineering? 05:12 – Setting Up Your Agent Workspace & Environment File 07:54 – Live Demo: LinkedIn Auto-Responder 09:56 – Live Demo: Bulk Facebook Ad Generator 12:31 – Live Demo: Cold Email Campaign Automation (Raphonic + Instantly) 14:47 – Live Demo: Creating Notion Documents via Claude Code 16:46 – Live Demo: Bulk Ad Creative Generator 26:05 – Live Demo: LinkedIn Engagement Scraper to Cold Email Pipeline 28:16 – Context Switching Across Tasks 29:19 – Live Demo: Bulk Ad Generator 31:41 – Live Demo: Data Analysis: Turning Off Low-Performing Ads 35:28 – Summary of GTM Engineering Workflow 37:48 – Deploying Agents and On-the-Fly Databases with Railway for Data Analysis 41:28 – The Dream of Autonomous Marketing 48:50 – Building API-First Products and Agent-Native Infrastructure Key Points GTM engineering has evolved from Clay-style data enrichment workflows into full-stack agent orchestration — where one person running multiple Claude Code agents can replace the output of a large team. The practical setup starts with a single folder containing your environment file (API keys for every tool in your stack), transcription software like Super Whisper, and Claude Code. Cody demonstrates running seven or more agents simultaneously across LinkedIn outreach, Facebook ad creation, cold email campaigns, Notion document generation, and live data dashboards. Code-generated ad creative (React components exported as PNGs) costs nearly nothing to produce at scale and allows rapid testing of messaging variations before investing in polished visuals. Deploying proven workflows to Railway turns one-off agent tasks into always-on, autonomous processes that run 24/7. Domain expertise is the real multiplier — the vocabulary you bring from your field determines the quality of output you can extract from these tools. The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/ FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/ FIND CODY ON SOCIAL: Cody's startup: https://www.graphed.com/ X/Twitter: https://x.com/codyschneiderxx Youtube: https://www.youtube.com/@codyschneiderx

In this episode of the Crazy Wisdom podcast, host Stewart Alsop sits down with Markus Buehler, the McAfee Professor of Engineering at MIT, to explore how seemingly different systems—from proteins and music to knowledge structures and AI reasoning—share underlying patterns through hierarchy, self-organization, and scale-free networks. The conversation ranges from the limits of current AI interpolation versus true discovery (using the fire-to-fusion example), to the emergence of agent swarms and their non-linear effects, to practical questions about ontologies, knowledge graphs, and whether humans will remain necessary in the creative discovery process. Markus discusses his lab's work automating scientific discovery through AI agents that can generate hypotheses, run simulations, and even retrain themselves, while Stewart shares his own experiences building applications with AI coding agents and grapples with questions about intellectual property, material science constraints, and the future of human creativity in an AI-abundant world.Timestamps00:00 - Introduction to Marcus Buehler's work on knowledge graphs, structural grammar across proteins, music, and AI reasoning05:00 - Discussion of AI discovery versus interpolation, using fire and fusion as examples of fundamental versus incremental innovation10:00 - Language models as connective glue between agents, enabling communication despite imperfect outputs and canonical averaging15:00 - Embodiment and agency in AI systems, creating adversarial agents that challenge theories and expand world models20:00 - Emergent properties in materials and AI, comparing dislocations in metals to behaviors in agent swarms25:00 - Human role-playing and phase separation in society, parallels to composite materials and heterogeneity30:00 - Physical world challenges, atom-by-atom manufacturing at MIT.nano, limitations of lithography machines35:00 - Synthetic biology as alternative to nanotechnology, programming microorganisms for materials discovery40:00 - Intellectual property debates, commodification of AI models, control layers more valuable than model architecture45:00 - Automation of ontologies, agent self-testing, daughter's coding success at age 1150:00 - Graph theory for knowledge compression, neurosymbolic approaches combining symbolic and neural methods55:00 - Nonlinear acceleration in AI, emergence from accumulated innovations, restaurant owner embracing AI01:00:00 - Future generations possibly rejecting AI, democratization of knowledge, social media as real-time scientific discourseKey Insights1. Universal Patterns Across Disciplines: Seemingly different systems in nature—proteins, music, social networks, and knowledge itself—share fundamental structural patterns including hierarchy, self-organization, and scale-free networks. This commonality allows creative thinkers to draw insights across disciplines, applying principles from one domain to solve problems in another. As an engineer and materials scientist, Buehler has leveraged these isomorphisms to advance scientific understanding by mapping the "plumbing" of different systems onto each other, revealing hidden relationships that enable extrapolation beyond what's observable in any single domain.2. The Discovery Versus Interpolation Problem: Current AI systems, particularly large language models, excel at interpolation—recombining existing knowledge in new ways—but struggle with genuine discovery that requires fundamental rewiring of world models. Using the example of fire versus fusion, Buehler explains that an AI trained on combustion chemistry would propose bigger fires or new fuels, but couldn't conceive of fusion because that requires stepping back to more fundamental physics. True discovery demands the ability to recognize when existing theories have boundaries and to develop entirely new frameworks, something current AI architectures aren't designed to achieve due to their training objective of predicting the most likely outcome.3. The Role of Ontologies and Knowledge Graphs: While some AI researchers argue that ontologies are unnecessary because models form internal representations, Buehler advocates for explicit knowledge graphs as essential discovery tools. External ontologies provide sharp, analytical, symbolic representations that complement the fuzzy internal representations of neural networks. They enable verification of rare connections—like obscure papers that might hold key insights—which would be averaged away in standard AI training. This neurosymbolic approach combines the generalization capabilities of neural networks with the precision of formal knowledge structures, creating more powerful discovery systems.4. Emergent Properties and Agent Swarms: Just as materials science shows that collections of atoms exhibit properties impossible to predict from individual components, AI agent swarms demonstrate emergent behaviors beyond single models. When agents are incentivized not just to answer questions but to challenge each other adversarially, propose theories, and test hypotheses, they can spawn new copies of themselves and evolve understanding beyond their initial programming. This emergence isn't surprising from a materials science perspective—dislocations, grain boundaries, and other collective phenomena only appear at scale, fundamentally determining material behavior in ways unpredictable from studying just a few atoms.5. The Commoditization of Intelligence: The fundamental AI models themselves are becoming commodities, as evidenced by events like the Moldbug phenomenon where people built agents using various providers interchangeably. The real value is shifting from who has the smartest model to how models are orchestrated, integrated, and deployed. This parallels historical technology adoption patterns—just as we moved past debating who makes the best electricity to focusing on applications, AI is transitioning from a horse race over model capabilities to questions of infrastructure, energy, access speed, and agent coordination at the systems level.6. Human-AI Collaboration and Creative Control: Rather than wholesale replacement, AI enables humans to operate in an intensely creative space as orchestrators sampling from vast possibility spaces. Similar to how Buehler's 11-year-old daughter now builds sophisticated applications that would have required professional developers years ago, AI democratizes access to capabilities while humans retain the creative judgment about direction and meaning. The human role becomes curating emergence, finding rare connections, playing at the edges of knowledge, and exercising the kind of curiosity-driven exploration that AI systems lack without embodied stakes in their own survival and continuation.7. Technology as Evolutionary Inevitability: The development of AI represents not an unnatural threat but the next stage of human evolution—an extension of our innate drive to build models of ourselves and our world. From cave paintings to partial differential equations to artificial intelligence, humans continuously create increasingly sophisticated representations and tools. Attempting to stop this technological evolution is futile; instead, the focus should be on steering it ...

Ben Clemens of FanGraphs joins the show to break down where the 2026 St. Louis Cardinals are headed, from win expectations and outfield needs to Chaim Bloom's “down to the studs” rebuild and the strategy behind recent trades and draft-pick flexibility. We dive into the upside-heavy approach highlighted by Jurrangelo Cijntje and other recent additions, react to FanGraphs' updated Cardinals prospect rankings, see a sneak preview of a new feature on Fangraphs, and wrap with a quick spin around the latest league news.Have a question or comment for the show? Text or leave us a voicemail at: (848) 48-BIRDS (848-482-4737)Talking About Birds is listener supported on Patreon. Support the show and join our private discord server at: www.patreon.com/talkingaboutbirds.

Send a textImagine an autonomous agent that dreams up a business, raises funds, ships code, and starts earning—all without a human in the loop. That's no longer sci‑fi. We sit down with Rodrigo Coelho to map the rails that make it plausible: reliable blockchain data, open payment standards, and human‑grade controls that keep machine spenders on track.We start with a myth many still believe: blockchains are easy to read. Rodrigo explains why they were write‑first, and how The Graph became a quiet backbone of DeFi by turning messy ledgers into queryable data. Years of running high‑throughput infrastructure set the stage for AMP, a SQL‑first, local‑first approach that unifies access across chains, runs on‑prem for banks, and proves that internal datasets match on‑chain truth—fuel for compliance, audit, and real‑world finance moving on blockchain rails.Then we connect the dots with AI. Leaders who once shrugged at crypto now see agents as the perfect fit: low fees, transparency, and observability. With X402 enabling open micropayments over HTTP, the next missing piece was control. Enter "ampersend", a dashboard and policy plane for agent wallets, spend limits, batching, and reputation‑aware routing. Think: “only transact with agents above a reputation threshold,” “cap this task at 50 cents,” or “enforce daily budgets,” all verifiable and auditable. We also unpack emerging standards like ERC‑8004 for reputation and the Advanced AI Society's proof of control, outlining the identity, trust, and policy stack enterprises need before they unleash agents at scale.By 2026, expect major institutions to settle on blockchain rails, blending privacy with auditability, and tokenizing everything from bonds to real estate. The opportunity is clear: give agents the autonomy to create value while giving humans the levers to define, observe, and verify. If you care about AI agents, Web3 data, enterprise compliance, and the future of payments, this conversation connects the technical dots to the business outcomes.Enjoyed the episode? Follow the show, share it with a friend who loves AI or Web3, and leave a 5‑star review to help more people find us.This episode was recorded through a Descript call on February 5, 2026. Read the blog article and show notes here: https://webdrie.net/how-ai-agents-will-spend-earn-and-prove-trust-on-blockchain-rails/..........................................................................

AI-Powered Knowledge Graph Generator & APTs https://isc.sans.edu/diary/AI-Powered%20Knowledge%20Graph%20Generator%20%26%20APTs/32712 nslookup and ClickFix https://x.com/MsftSecIntel/status/2022456612120629742 Google Chrome 0-Day Patch https://chromereleases.googleblog.com/2026/02/stable-channel-update-for-desktop_13.html TURN Security Threats https://www.enablesecurity.com/blog/turn-server-security-threats/

@GeneSohoForum coming through with the Graphs and walkthrough of the real story in American Labor markets. Are American's underpaid by greedy corporations? Find out on today's episode.

@GeneSohoForum coming through with the Graphs and walkthrough of the real story in American Labor markets. Are American's underpaid by greedy corporations? Find out on today's episode.

In this interview I'm joined by Dr. Ryan Burge (aka, Graphs about Religion) to discuss the state of religion in America. We cover claims of a Gen Z revival, the decline of mainline Protestantism, and what the data tells us about polarization. Read the Book: https://amzn.to/3ZrUpqnWant to support the channel? Here's how!Give monthly: https://patreon.com/gospelsimplicity  Make a one-time donation: https://paypal.me/gospelsimplicityBook a meeting: https://calendly.com/gospelsimplicity/meet-with-austinRead my writings: https://austinsuggs.substack.com/Support the show

In this episode of the Crazy Wisdom Podcast, host Stewart Alsop explores the complex world of context and knowledge graphs with guest Youssef Tharwat, the founder of NoodlBox who is building dot get for context. Their conversation spans from the philosophical nature of context and its crucial role in AI development, to the technical challenges of creating deterministic tools for software development. Tharwat explains how his product creates portable, versionable knowledge graphs from code repositories, leveraging the semantic relationships already present in programming languages to provide agents with better contextual understanding. They discuss the limitations of large context windows, the advantages of Rust for AI-assisted development, the recent Claude/Bun acquisition, and the broader geopolitical implications of the AI race between big tech companies and open-source alternatives. The conversation also touches on the sustainability of current AI business models and the potential for more efficient, locally-run solutions to challenge the dominance of compute-heavy approaches.For more information about NoodlBox and to join the beta, visit NoodlBox.io.Timestamps00:00 Stewart introduces Youssef Tharwat, founder of NoodlBox, building context management tools for programming05:00 Context as relevant information for reasoning; importance when hitting coding barriers10:00 Knowledge graphs enable semantic traversal through meaning vs keywords/files15:00 Deterministic vs probabilistic systems; why critical applications need 100% reliability20:00 CLI tool makes knowledge graphs portable, versionable artifacts with code repos25:00 Compiler front-ends, syntax trees, and Rust's superior feedback for AI-assisted coding30:00 Claude's Bun acquisition signals potential shift toward runtime compilation and graph-based context35:00 Open source vs proprietary models; user frustration with rate limits and subscription tactics40:00 Singularity path vs distributed sovereignty of developers building alternative architectures45:00 Global economics and why brute force compute isn't sustainable worldwide50:00 Corporate inefficiencies vs independent engineering; changing workplace dynamics55:00 February open beta for NoodlBox.io; vision for new development tool standardsKey Insights1. Context is semantic information that enables proper reasoning, and traditional LLM approaches miss the mark. Youssef defines context as the information you need to reason correctly about something. He argues that larger context windows don't scale because quality degrades with more input, similar to human cognitive limitations. This insight challenges the Silicon Valley approach of throwing more compute at the problem and suggests that semantic separation of information is more optimal than brute force methods.2. Code naturally contains semantic boundaries that can be modeled into knowledge graphs without LLM intervention. Unlike other domains where knowledge graphs require complex labeling, code already has inherent relationships like function calls, imports, and dependencies. Youssef leverages these existing semantic structures to automatically build knowledge graphs, making his approach deterministic rather than probabilistic. This provides the reliability that software development has historically required.3. Knowledge graphs can be made portable, versionable, and shareable as artifacts alongside code repositories. Youssef's vision treats context as a first-class citizen in version control, similar to how Git manages code. Each commit gets a knowledge graph snapshot, allowing developers to see conceptual changes over time and share semantic understanding with collaborators. This transforms context from an ephemeral concept into a concrete, manageable asset.4. The dependency problem in modern development can be solved through pre-indexed knowledge graphs of popular packages. Rather than agents struggling with outdated API documentation, Youssef pre-indexes popular npm packages into knowledge graphs that automatically integrate with developers' projects. This federated approach ensures agents understand exact APIs and current versions, eliminating common frustrations with deprecated methods and unclear documentation.5. Rust provides superior feedback loops for AI-assisted programming due to its explicit compiler constraints. Youssef rebuilt his tool multiple times in different languages, ultimately settling on Rust because its picky compiler provides constant feedback to LLMs about subtle issues. This creates a natural quality control mechanism that helps AI generate more reliable code, making Rust an ideal candidate for AI-assisted development workflows.6. The current AI landscape faces a fundamental tension between expensive centralized models and the need for global accessibility. The conversation reveals growing frustration with rate limiting and subscription costs from major providers like Claude and Google. Youssef believes something must fundamentally change because $200-300 monthly plans only serve a fraction of the world's developers, creating pressure for more efficient architectures and open alternatives.7. Deterministic tooling built on semantic understanding may provide a competitive advantage against probabilistic AI monopolies. While big tech companies pursue brute force scaling with massive data centers, Youssef's approach suggests that clever architecture using existing semantic structures could level the playing field. This represents a broader philosophical divide between the "singularity" path of infinite compute and the "disagreeably autistic engineer" path of elegant solutions that work locally and affordably.

Blitzy founders Brian and Sid break down how their “infinite code context” system lets AI autonomously complete over 80% of major enterprise software projects in days. They dive into their dynamic agent architecture, how they choose and cross-check different models, and why they prioritize advances in AI memory over fine-tuning. The conversation also covers their 20¢/line pricing model, the path to 99%+ autonomous project completion, and what this all means for the future software engineering job market. Sponsors: Blitzy: Blitzy is the autonomous code generation platform that ingests millions of lines of code to accelerate enterprise software development by up to 5x with premium, spec-driven output. Schedule a strategy session with their AI solutions consultants at https://blitzy.com Tasklet: Tasklet is an AI agent that automates your work 24/7; just describe what you want in plain English and it gets the job done. Try it for free and use code COGREV for 50% off your first month at https://tasklet.ai Serval: Serval uses AI-powered automations to cut IT help desk tickets by more than 50%, freeing your team from repetitive tasks like password resets and onboarding. Book your free pilot and guarantee 50% help desk automation by week four at https://serval.com/cognitive CHAPTERS: (00:00) About the Episode (03:02) AGI effects without AGI (07:07) Domain-specific context engineering (16:54) Dynamic harness and evals (Part 1) (17:00) Sponsors: Blitzy | Tasklet (20:00) Dynamic harness and evals (Part 2) (30:42) Graphs, RAG, and memory (Part 1) (30:49) Sponsor: Serval (32:26) Graphs, RAG, and memory (Part 2) (41:17) Model zoo and memory (50:07) Planning, scaling, and parallelism (56:13) Pricing, onboarding, and autonomy (01:04:24) Closing the last 20% (01:12:34) Strange behaviors and judges (01:22:23) Reasoning budgets and autonomy (01:33:36) Fine-tuning, benchmarks, and training (01:42:31) Securing AI-generated code (01:49:52) Future of software work (01:57:05) Outro PRODUCED BY: https://aipodcast.ing SOCIAL LINKS: Website: https://www.cognitiverevolution.ai Twitter (Podcast): https://x.com/cogrev_podcast Twitter (Nathan): https://x.com/labenz LinkedIn: https://linkedin.com/in/nathanlabenz/ Youtube: https://youtube.com/@CognitiveRevolutionPodcast Apple: https://podcasts.apple.com/de/podcast/the-cognitive-revolution-ai-builders-researchers-and/id1669813431 Spotify: https://open.spotify.com/show/6yHyok3M3BjqzR0VB5MSyk

Send us a textPrasad Calyam, Curators' Distinguished Professor and Center Director at the University of Missouri, joins the show to explore how knowledge graphs, modern data platforms, and AI are reshaping power grids and cybersecurity. He breaks down graph database fundamentals, real-world research projects, and how industry can tap into cutting-edge university work—all in language that engineers, data folks, and developers can put to use.Timestamps 01:30 Meet Prasad Calyam 02:57 Why Higher Education? 05:22 Data Analytics 06:59 The Modern Power Grid 09:40 Graph DB Fundamentals 12:21 Cybersecurity via Graphs and RAG 13:45 Research Projects 14:38 Industry Leveraging University Research 16:07 Advice for Students 17:16 What's Fun for ProfessorsLinks LinkedIn: linkedin.com/in/prasadcalyam Website: http://www.missouri.edu#KnowledgeGraphs #GraphDatabase #RAG #Cybersecurity #PowerGrid #DataEngineering #AI #MLOps #TechPodcast #Developers #ResearchToProduction #UniversityResearchWant to be featured as a guest on Making Data Simple? Reach out to us at almartintalksdata@gmail.com and tell us why you should be next. The Making Data Simple Podcast is hosted by Al Martin, WW VP Technical Sales, IBM, where we explore trending technologies, business innovation, and leadership ... while keeping it simple & fun.

Send us a textPrasad Calyam, Curators' Distinguished Professor and Center Director at the University of Missouri, joins the show to explore how knowledge graphs, modern data platforms, and AI are reshaping power grids and cybersecurity. He breaks down graph database fundamentals, real-world research projects, and how industry can tap into cutting-edge university work—all in language that engineers, data folks, and developers can put to use.Timestamps 01:30 Meet Prasad Calyam 02:57 Why Higher Education? 05:22 Data Analytics 06:59 The Modern Power Grid 09:40 Graph DB Fundamentals 12:21 Cybersecurity via Graphs and RAG 13:45 Research Projects 14:38 Industry Leveraging University Research 16:07 Advice for Students 17:16 What's Fun for ProfessorsLinks LinkedIn: linkedin.com/in/prasadcalyam Website: http://www.missouri.edu#KnowledgeGraphs #GraphDatabase #RAG #Cybersecurity #PowerGrid #DataEngineering #AI #MLOps #TechPodcast #Developers #ResearchToProduction #UniversityResearchWant to be featured as a guest on Making Data Simple? Reach out to us at almartintalksdata@gmail.com and tell us why you should be next. The Making Data Simple Podcast is hosted by Al Martin, WW VP Technical Sales, IBM, where we explore trending technologies, business innovation, and leadership ... while keeping it simple & fun.

We're joined by droqen (The End of Gameplay, Starseed Pilgrim), Darius Kazemi (Tiny Subversions, Harvard Applied Social Media Lab), and Tara Macalister (mathematician, composer) to discuss Vertex Dispenser, the second game in our year-long exploration of the work of Michael Brough. Next Month: Kompendium Audio edited by Dylan Shumway. Discussed in this episode: Vertex Dispenser https://store.steampowered.com/app/102400/Vertex_Dispenser/ Michael Brough's Website https://www.smestorp.com/ Four color theorem https://en.wikipedia.org/wiki/Four_color_theorem Graph coloring https://en.wikipedia.org/wiki/Graph_coloring  Starcraft II https://starcraft2.blizzard.com/en-us/ Splatoon https://splatoon.nintendo.com/  Dota 2 https://www.dota2.com/home  Droqen's rare color graph/explanation https://discord.com/channels/690388280767807518/1442554518092120186/1465039921147412510  lots of michael brough games https://smestorp.itch.io/lots-of-michael-brough-games  The Sense of Connectedness https://forums.tigsource.com/index.php?topic=16151.0  Kompendium https://mightyvision.blogspot.com/2012/06/kompendium.html The End of Gameplay https://droqen.itch.io/the-end-of-gameplay Utopia Clicker https://tinysubversions.com/game/utopia/ A Jackpot of Skulls https://brainfruit.studio/games/jackpot _update() Jam https://adamatomic.itch.io/update-jam   https://secretlives.games/  https://discord.gg/tslog https://www.patreon.com/tslog https://www.youtube.com/eggplantshow

Submit your CPR Report here. Get a call from Dr. Zeeshan or Nurse Brittany fill out form here!https://docs.google.com/forms/d/e/1FAIpQLSeAO_cq5OE6ONYgDFSz0HHrUqKt2Nk1JfC-3D7eXUl8LlzGdg/viewformOur February course is $149.99 JOIN ASAP!~https://nclexhighyield.com/collections/february-coursesOur Self-Paced Online Videos are on sale for $44.99 and has updated notes, videos, and practice questions! You can join at https://nclexhighyieldcourse.com/p/full-nclex-course7

My guests today are Animesh Koratana and Jamin Ball. Animesh is the founder and CEO of our portfolio company PlayerZero, which is building AI production engineers that operate complex enterprise software autonomously - resolving production incidents, catching defects before release, and building durable models of how systems actually behave.Jamin is a partner at Altimeter Capital and the writer behind Clouded Judgement, a Substack where he analyzes emerging trends in enterprise software. Jamin recently sparked a debate with an essay titled “Long Live Systems of Record.” His core argument is that while agents are changing how software is used and where value accrues, they still depend on ground truth. Systems of record won't disappear so much as get pushed down the stack as new agent-native interfaces emerge on top.My partner Jaya and I felt compelled to respond, with Animesh contributing insights based on what he's seeing on the ground as he builds PlayerZero. From our perspective, the missing layer is what happens inside the workflow itself: the judgment, exceptions, and reasoning that agents and humans apply as work gets done. We call these decision traces, and we believe the context graph they form over time will become the most valuable asset for companies building and deploying AI systems.It's a genuine debate - and one that's only going to matter more as agents move from demos to production.Looking forward to keeping the conversation going!Chapters00:00 Why Jamin's essay sparked debate00:35 Jamin's thesis: why agents need ground truth02:00 Animesh on why context graphs become the new source of leverage07:58 What current systems of record miss08:28 PlayerZero's perspective: context graphs in practice10:00 How context graphs could change org structures11:10 How to capture decision traces without forcing humans to log it?14:35 Which systems of record are most at risk17:04 Two workflows ripe for disruption: GTM and software development22:31 Animesh on where context graphs can add most value 28:50 Why context graphs create durability vs short-lived point solutions30:00 Will context graphs be verticalized or universal?34:00 Bear case: do context graphs fail like semantic layers?43:27 2026 predictions: big AI IPOs, world models, enterprise agent adoption45:00 Hot takes: point solutions die; AI job-loss discourse hits a fever pitch47:30 Jevons paradox: why agents create more work, not less

Graphs and charts: One dealt with the average life span. I still have 17 years left according to statistical data. Another dealt with how much time we have left after arriving at age 65 to enjoy good health.

Why “context graphs” have suddenly become one of the most important ideas in enterprise AI, and what they reveal about why agents fail or succeed at real work. This episode explains the core idea behind context graphs, how they differ from systems of record and knowledge graphs, and why capturing decision traces — the why, not just the what — may be the key to scalable autonomy inside organizations. In the headlines: AI wearables make another run at relevance, China reports early success using AI for cancer detection, X faces global backlash over Grok moderation failures, and Yann LeCun publicly breaks with Meta's AI strategy. Brought to you by:KPMG – Discover how AI is transforming possibility into reality. Tune into the new KPMG 'You Can with AI' podcast and unlock insights that will inform smarter decisions inside your enterprise. Listen now and start shaping your future with every episode. ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.kpmg.us/AIpodcasts⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Zencoder - From vibe coding to AI-first engineering - ⁠http://zencoder.ai/zenflow⁠Robots & Pencils - Cloud-native AI solutions that power results ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://robotsandpencils.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠The Agent Readiness Audit from Superintelligent - Go to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://besuper.ai/ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠to request your company's agent readiness score.The AI Daily Brief helps you understand the most important news and discussions in AI. Subscribe to the podcast version of The AI Daily Brief wherever you listen: https://pod.link/1680633614Interested in sponsoring the show? sponsors@aidailybrief.ai

The late Robert Solow was a giant among economists. When he was 98 years old he told Steve about cracking German codes in World War II, why it's so hard to reduce inequality, and how his field lost its way.  SOURCES:Robert Solow, professor emeritus of economics at the Massachusetts Institute of Technology. RESOURCES:"Secrecy, Cigars, and a Venetian Wedding: How the P.G.A. Tour Made a Deal with Saudi Arabia," by Alan Blinder, Lauren Hirsch, Kevin Draper, and Kate Kelly (The New York Times, 2023)."Global Assessment of Environmental-Economic Accounting and Supporting Statistics: 2020," by United Nations Committee of Experts on Environmental-Economic Accounting (2021)."Where Modern Macroeconomics Went Wrong," by Joseph E. Stiglitz (Oxford Review of Economic Policy, 2015)."As Inequality Grows, So Does the Political Influence of the Rich," (The Economist, 2018)."Big Bang Financial Deregulation and Income Inequality: Evidence From U.K. and Japan," by Daniel Waldenstrom and Julia Tanndal (VoxEU, 2016)."The Fall And Rise Of U.S. Inequality, In 2 Graphs," by Quoctrung Bui (Planet Money, 2015).Nobel Prize Biographical, by Robert Solow (1987).Principles of Political Economy, by John Stuart Mills (1848). EXTRAS:"Is Economic Growth the Wrong Goal? (Update)," by Freakonomics Radio (2023). Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.