✦Crazy Wisdom

Stewart Squared

Episode #47: The Cost of Knowing Everything

Episode #47 · July 24, 2025 · 46 min

MP3 · Apple Podcasts · Spotify

About this episode

Welcome to Stewart Squared podcast with the two Stewart Alsops. In this episode, they navigate a sprawling conversation that begins with the unruly complexity of the modern browser and spirals into deeper territory—from Google’s jealous leap into the browser wars with Chrome, to the philosophical implications of Neuralink and the idea of owning one’s own data and mind. Stewart Alsop interviews his co-host Stewart on themes like the architecture of the internet, the anti-fragility of figures like Musk and Trump, and the evolving coordination costs of technology in both business and AI. Along the way, they touch on acquisitions, database architecture, real-time systems, and the specter of machine self-coordination.

Check out this GPT we trained on the conversation


Timestamps

00:00 – Browser frustration leads into a discussion of browser complexity, operating systems, and why web environments remain chaotic.
05:00 – History of Chrome’s development, Google’s envy of Microsoft, and their early efforts to own user tools.
10:00 – Reflections on anti-fragility, using Musk and Trump as examples; intro to Neuralink and Musk’s emotional reactivity.
15:00 – Concerns about brain-computer interfaces and the ethical risks of having someone like Musk in control; the role of data collection in brain mapping.
20:00 – Importance of enterprise databases, real-time data, and how companies like United Airlines manage coordination better than others.
25:00 – Technical talk on vectorized databases, chunking, and Postgres SQL; Stewart Alsop shares his efforts to embed podcast transcripts.
30:00 – Discussion of relational database history, RDBMS, and how Salesforce and other CRM tools evolved to integrate siloed data.
35:00 – Breakdown of Facebook’s architecture, Messenger, WhatsApp, and why real-time systems break down under bloated coordination.
40:00 – Exploration of coordination costs, AI’s role in reducing them, and the philosophical implications of machine autonomy.

Key Insights
  1. Browser complexity reflects broader system tensions: The episode opens with a frustrating technical hiccup that segues into a deeper conversation about how modern computing environments—especially browsers—remain unruly due to inconsistent standards and fragmented development environments. This mirrors larger challenges in managing open systems versus tightly controlled ecosystems like Apple’s.
  2. Google’s empire-building was driven by competitive envy: Chrome’s inception is framed not as visionary but as reactive—Google’s way of competing with Microsoft’s hold over user environments via Explorer and Windows. Their acquisition strategy, including YouTube and Orcutt, reflects a relentless effort to own every layer of digital experience, often by replication rather than innovation.
  3. Musk exemplifies both genius and fragility: Neuralink prompts a critical look at Elon Musk—praised for technical brilliance and bold ambitions, but critiqued for emotional reactivity and lack of emotional intelligence. His vision of brain-computer interfaces raises ethical alarms when tied to someone perceived as having low empathy.
  4. Anti-fragility as a political and psychological frame: Nassim Taleb’s concept of anti-fragility becomes a lens through which Stewart Alsop views public figures like Trump and Musk—those who seem to gain strength through opposition. It also sparks reflection on cultural differences in social resilience, especially between U.S. and Latin American societies.
  5. The power of data architecture is political: The idea that building a database—whether of brains or enterprise processes—means wielding enormous influence. Stewart argues that control over structured, real-time data flows is key to both tech product success and organizational accountability, especially in AI compliance contexts.
  6. Startups thrive on focus, big companies collapse under coordination: A recurring theme is the difference between small, nimble teams with a single mission and sprawling organizations burdened by coordination costs. The “mythical man-month” is invoked to show how adding people often slows progress when architecture is weak.
  7. AI changes, but doesn’t erase, human complexity: Despite AI’s potential to reduce coordination costs, the conversation ends with caution. Machines managing themselves without human input evokes Terminator fears. The need for aligned, human-centered design remains vital, even in the face of immense computational power.
Episode transcript
Stewart Alsop III00:06

Everyone is wrong about AI, but if you know the history of technology, you can be wrong and still be right.

Stewart Alsop II00:13

I know the history of technology since I started with the personal computer in 1980. So listen in while we explore what is right about AI.

Stewart Alsop III00:26

Welcome to the Stuart Squared podcast. We're going to talk about the browser, how the browser came around, because both of us right now in this current moment have just spent the last 10 minutes going back and forth trying to turn off things and do other things in order to make the browser work with Riverside, but not only Riverside, it's like all these things and it's just so complex. And when are we going to get to a world where we never see the complexity again?

Stewart Alsop II00:53

Do you believe in your heart of hearts, because you're an iPhone user, that you don't see complexity on the iPhone?

Stewart Alsop III00:59

No, I see complexity, yeah.

Stewart Alsop II01:02

It's not the same. I mean, the browser is an app along with every other app, and the iPhone is a very tightly controlled environment, Even the Macintosh, but the PC, even worse, is uncontrolled. App developers can do anything they want, including, we're talking about Riverside Studio. They're choosing not to support Safari in their native Mac app, which is like, really weird. And so I have to use the native Mac app. I can't use Safari, which is my browser. Although you're used to using Studio inside Chrome browser. And so that's one level of complexity is just the operating system and how much application developers can violate the rules and mess around, create inconsistency from one app to the next, and potentially even crash apps as a result. The next level is in a web browser. There's no. How do I describe this? Every time you open a web browser window, you create an instance. It's different on PCs and Macs. So I don't know if I'm technically using the term instance. Don't worry about it. Yeah, yeah. But what I'm trying to get at is that it's a much more unruly environment. So the way that developers in the web use memory, how they interact with the machine be wildly different because it's a very loose standard HTTP with tcp, ip, et cetera, et cetera. All of the protocols we've talked about in the past is a much less well controlled environment. In fact, that's part of the whole design of it, is that you can drop a nuclear bomb and anybody that's nearby will lose their Internet, not just physically, but from the emp, but no one else will outside the blast range. So the Internet was designed to continue operating even if it lost whole chunks of itself that leads to an unruly environment because it's a very low level protocol relative to APIs in an operating system. Different levels of the operating system.

Your first full transcript is free. After that, an email opens every transcript in the index — a list of readers we can write to, not a guest book.

Subscribe