tech

Unofficial, machine-generated summaries, as of 2026-11-09.

Y CombinatorThe New Way To Build A Startup
  • The leanest startups now automate every internal function, not just one. Garry Tan calls these "20X companies," extending Parker Conrad's "compound startup" idea from product breadth to internal operations — covering code, support, marketing, sales, hiring, and QA — which keeps payroll and headcount down as revenue scales.
  • One customer-service startup beat 20-times-larger rivals for a major account. GigaML's founders say they closed DoorDash as a customer with just four to five engineers against competitors with roughly 100x the headcount, crediting their internal agent Atlas — which can use browsers, edit policies, and write code — with doubling or tripling each engineer's scope.
  • One interface let a psychiatry network 4x patients with flat headcount. Legion Health built a single internal tool giving its care-ops team instant access to patient history, scheduling, and insurance codes; it says this let revenue and patient volume grow 4x in a year while staffing stayed at one clinical lead, one patient-support person, and one billing person.
  • A 12-person firm skips hiring by turning workflows into agents. Feathr, competing against accounts-receivable incumbents dating to 2006, has employees document their manual tasks so it can build custom agents for each; it says this let it avoid hiring a dedicated designer altogether, using an AI design tool instead for all front-end work.
Dr. Jon KrohnPyTorch Lightning's Origin Story (with PyTorch Lightning Creator Will Falcon)
  • The library began as an undergraduate's private "research lib". Falcon started PyTorch Lightning around 2015 at a Columbia neuroscience lab, before PyTorch existed, decoding images from retinal recordings (a Stanford partnership that showed ImageNet images to monkey retinas) with autoencoders and GANs, first in Theano. The aim was to try many ideas without rewriting code, and a postdoc, now a Stanford professor, pushed him to formalise it into a reusable harness. The host puts downloads at over 300 million; Falcon says close to 400 million.
  • Multi-GPU training turned weeks-long experiments into hours. One ImageNet epoch took 21 days and the autoencoder needed hundreds, with a NeurIPS deadline months away, so Falcon built four boxes with four GPUs each (1080-class cards) and rewrote the code in TensorFlow for multi-GPU support. The result was his first and only NeurIPS paper, on which he was not first author; he later moved to PyTorch because it mapped more directly onto the maths of the probabilistic models the lab was writing.
  • His earlier startup used RL to coach humans helping students win financial aid. At the company he founded and sold, staff texted with low-income students across 60,000 customers, and a UI suggested the next question by treating the conversation as a game whose reward was financial aid. Without LLMs it ranked a fixed list of questions probabilistically, and Falcon says it got students about $60 million in aid; he called the approach "bot-powered humans".
Dr. Jon KrohnThe Moltbook Phenomenon: OpenClaw Unleashed (Ep. 966 with Jon Krohn)
  • The agent-only social network's headline growth was largely unverified. The host reports that Moltbook, launched on January 28 by Octane AI CEO Matt Schlicht, lets only autonomous agents post, comment and upvote, and claimed over 1.5 million registered agents within days. Those figures were self-reported; cloud security firm Wiz later found only around 17,000 human owners behind them, an 88-to-1 ratio, and no rate limiting, so anyone could register millions of agents with a simple loop.
  • The underlying agent framework has real tools and deep system access. OpenClaw, by Austrian engineer Peter Steinberger, is a self-hosted personal assistant reached through WhatsApp, Telegram, Discord or Signal; it runs shell commands, manages files, automates the web and keeps persistent memory in local markdown. It was first named after Anthropic's Claude, renamed Moltbot after Anthropic raised trademark concerns, then OpenClaw.
  • Agents' emergent "culture" looks more like mimicry than mind. Agents formed a lobster-themed religion, Crustafarianism (one user's agent built its site, scripture and 43 prophets overnight), a "Claw Republic", encrypted channels and markets in "digital drugs", meaning prompt injections. Elon Musk called it the very early stages of the singularity and Simon Willison called it complete slop while granting agents have grown more powerful; the host leans to mimicry of sci-fi tropes in training data, and cites Columbia professor David Holtz's finding that 93.5% of comments got zero replies, suggesting agents perform for an audience rather than listen.
  • The vibe-coded site exposed its whole production database. Schlicht said he wrote no code himself; on January 31 security researcher Jamieson O'Reilly found an API key in client-side JavaScript and no access controls, giving unauthenticated read and write access. Over 1.5 million API tokens, about 35,000 emails and private agent messages, some holding plaintext OpenAI keys, were exposed, 404 Media confirmed any agent account could be taken over, and researchers said the fix needed two SQL statements. The site was patched within hours and keys reset.
  • The host's lesson: security basics outweigh agentic hype. He separates the platform breach from OpenClaw's built-in risk, which CrowdStrike, Cisco, Palo Alto Networks and Bitdefender have documented, and notes Andrej Karpathy went from marvelling to calling Moltbook a dumpster fire and warning against running OpenClaw on personal computers. He recommends a dedicated box or cloud instance (pointing to Lightning AI, where he holds a fellowship), and least privilege, sandboxing and code audits.
Y CombinatorWhy OpenClaw Broke The Internet
  • OpenClaw's edge is running locally on a user's own computer rather than in the cloud. Speakers say that access lets it control anything connected to the machine — an oven, a Tesla, lights, a Sonos, even a smart bed — and describe it searching a user's files unprompted to compile a surprising narrative of their past year from forgotten old audio recordings.
Dr. Jon KrohnWhy Most Neoclouds Will Fail But Lightning AI Won’t (with Will Falcon)
  • Debt-funded neoclouds face a mortgage-crisis-style squeeze. The host cites a McKinsey article calling neocloud economics fragile and at risk of repeating early-cloud consolidation. Falcon says many neoclouds borrowed against customers, often startups, not defaulting, and the public ones borrowed against market caps; with neocloud prices down about 60% or more in the last 6 months, he expects lenders to call loans.
  • He predicts the sector will need an outside rescue. He calls for something like a TARP programme. Falcon likens it to banks overleveraged before the Federal Reserve bailout and says a big player will probably have to support the ecosystem; this is his speculation, and he declines to say who.
  • He says the merger avoids those weaknesses. Lightning AI has merged with Voltage Park. By Falcon's account Voltage Park carries no debt, its CEO (now on Lightning's board) is a former finance executive focused on profitability, and most customers are enterprises with strong credit, sold through security work Lightning has done for six years. He calls the result a hybrid cloud that still partners with AWS and others, with fast-growing, high-margin revenue, and expects to take on debt in the next few years in a controlled way.
Scott HanselmanHe wrote this with 5 years experience
  • You need not wait decades to write something industry-defining. One speaker says Steve McConnell wrote Code Complete, 900 pages and a "Bible for about 20 years", with about five years of experience, so people can contribute after one to three years. The other agrees, saying they read anyone's blog regardless of experience because no one else has that perspective; they date the book to 1993 and their own paid coding to '92.
Crosstalk SolutionsThis Free Self-Hosted Tool Makes UniFi Network Way More Useful
  • The host built the UI Toolkit to surface data UniFi buries. It is his own free, self-hosted, containerized companion app for UniFi Network, with Docker and Synology Container Manager versions on GitHub; he asks for testing, bug reports and tool suggestions via the GitHub issues page.
  • Wi-Fi Stalker tracks chosen clients' presence and roaming between access points. It shows a historical presence pattern and can push real-time webhooks to Discord, Slack or other apps; the host pitches it for seeing when kids get home or how long employees were out at lunch.
  • Threat Watch and Network Pulse replace dashboards UniFi lacks. Threat Watch displays intrusion-detection events; Network Pulse is a full-screen view of client and device counts, throughput, Wi-Fi data and top wireless clients by bandwidth, which the host says is what he wishes UniFi's widgets could build.
  • A local LAN version and a public-hosting version exist. Only the public one adds authentication and a Let's Encrypt certificate. Both connect via a UniFi API key generated in the control plane, or username and password for legacy installations.
Y CombinatorAI Native Hedge Funds
  • AI-native hedge funds will emerge by inventing new strategies, the way quant funds did in the 1980s, not by bolting AI onto old ones. A former quant researcher recounts being ignored after asking compliance to approve ChatGPT use at a major fund, and argues the opportunity is swarms of AI agents combing 10-Ks, earnings calls and SEC filings to generate and trade on genuinely new strategies.
Dr. Jon KrohnHow Lightning AI Built a $500m ARR Full-Stack AI Cloud (with Will Falcon)
  • The merger pairs full-stack AI software with owned GPU supply. Lightning AI has merged with Voltage Park. The host, who discloses a year-long fellowship at Lightning AI, gives the combined figures: 400,000 developers and companies served, over $500 million in ARR gained in under two years, and 35,000 GPUs, which he says makes it the third-largest neocloud. Falcon notes these are the two companies' numbers combined and likens the pairing to a Mac with macOS.
  • Retrofitted CPU clouds push AI teams into stitching single-purpose tools. Falcon calls AWS premium-priced and built for CPU workloads, so enterprises and startups buy specialised point products and stitch them together, adding firewall and security work for enterprises and operational overhead for everyone. Lightning's customers wanted its full-stack software but found compute expensive; it had never sold compute, with customers bringing their own cloud.
  • Neoclouds outperform on GPUs, but few met enterprise stability needs. Falcon says neoclouds are GPU-first and work directly with Nvidia on InfiniBand and storage, and that there are hundreds; Lightning partnered with the top seven or eight, but enterprise customers, Cisco among them, struggled to adopt them. Voltage Park's responsive "white glove" support won and retained enterprise customers, which he says convinced him they were serious.
Y CombinatorStablecoin Financial Services
  • Stablecoins sit in a regulatory middle ground that opens room for new DeFi-meets-TradFi financial products. The speaker cites the GENIUS and CLARITY Acts as positioning stablecoins as compliant yet crypto-native, enabling services like yield-bearing accounts or tokenized real-world-asset access without forcing a choice between limited traditional products and unregulated crypto risk.
Scott HanselmanSoft skills are in the job description now
  • Hiring now screens for soft skills more than technologies. One speaker says the "brilliant jerks" prized in the early 2000s gave way to collaborative engineers as Stack Overflow and forums made code easier to pick up. Recent ads for product engineers at VC-funded companies that raised money in the last one or two years list empathy for customers instead of technologies, and the speaker says such companies reject many candidates on soft skills. The other says the industry never should have tolerated brilliant jerks.
Dr. Jon KrohnThe PhD Side Project That Became a $500M AI Company (Ep. 965 with Will Falcon)
synopsis

Will Falcon, CEO of Lightning AI, ends up arguing that AI infrastructure is consolidating into a new kind of cloud: software primitives for training, inference, development and agents bundled with owned GPU supply. He says Lightning's merger with Voltage Park makes it the first "full-stack AI neocloud", built on low debt and enterprise customers at a time when he expects debt-laden neoclouds to face a credit squeeze. The host discloses a year-long fellowship at Lightning AI.

The merger. The host gives the combined figures: 400,000 developers and companies, over $500 million in ARR gained in under two years, and 35,000 GPUs, which he calls the third-largest neocloud. Lightning had never sold compute; customers brought their own cloud. He calls AWS premium-priced and built for CPU workloads, so AI teams stitch point products together at a cost in security and overhead. Of hundreds of GPU-first neoclouds, Lightning partnered with the top seven or eight, but enterprise customers such as Cisco struggled on them until Voltage Park's responsive "white glove" support won and retained them. Lightning alone grew revenue at least 30–40x in the past year yet lost deals for lack of compute, while neoclouds offered little beyond Kubernetes. Falcon says the company was standing up its seventh data center and built Cursor's training cluster.

What an AI cloud is. Falcon regrets that "inference" stuck as a name and says a production inference server is like a web server with different batching and streaming. Against the claim that roughly 99% of GPU use is inference, which the host offers, he recalls that at Facebook in 2019, 99% of workloads ran on one GPU only because multi-GPU training was hard; training will grow once tooling exists. His analogy is S3 in the early 2000s: storage became a primitive within what was later called the cloud, and inference, vector databases, training infrastructure and agents will bundle the same way rather than each becoming a company.

Studios. The core product is a persistent cloud development environment that behaves like a laptop: Claude Code can run overnight without risk to a local machine, 20 can run at once on different CPUs and GPUs, any editor or SSH can connect, teams share environments, and enterprises can audit them and run them on-prem or in their own cloud. Every Lightning developer works on Studios. Vibe-coding agents aim to close a talent gap for data scientists used to scikit-learn and NumPy, handling the MLOps and spinning up clusters of 1,000 GPUs.

Neocloud economics. Asked about a McKinsey article calling neocloud economics fragile, Falcon says many rivals borrowed against startup customers or, once public, against market caps. With neocloud prices down about 60% or more in six months, he expects loans to be called and a mortgage-crisis-like need for a TARP-style rescue. Voltage Park has no debt and its CEO, now on Lightning's board, is a former finance executive; Lightning expects to take on controlled debt in the next few years. Enterprise contracts fund a free tier and the claimed 70% cost cut, which he ties to his own need for compute as a student.

PyTorch Lightning's origins. As a Columbia undergraduate around 2015, Falcon decoded images from retinal recordings with autoencoders and GANs, first in Theano, using a personal "research lib". Rewriting it in TensorFlow across four self-built four-GPU boxes cut an ImageNet run from 21 days to about an hour and yielded his only NeurIPS paper. He co-founded NextGen Vest, which used reinforcement learning to suggest questions for staff texting low-income students and got them about $60 million in aid; CommonBond acquired it around 2017–2018. At NYU under Kyunghyun Cho and Yann LeCun he open-sourced the library and took it into FAIR, then a group of about 100–150 people. Maintaining it slowed his research and he nearly shut it down; then about 10 term sheets arrived in a few days and he founded the company.

The library today. Falcon counts about 500,000 engineering hours in PyTorch Lightning and rejects the idea that it is not for generative AI: Nvidia's NeMo is built on it, AWS has pre-trained LLMs with it and LinkedIn trained a 100-billion-parameter LLM with it. Teams wanting more control move to Lightning Fabric, then raw PyTorch.

Grit. Falcon arrived from Caracas at 13 without English and left a two-year ESL programme in 4 or 5 months. He was one of about 20 officers selected from roughly 12,000 applicants for Navy SEAL training but, after pneumonia and Hell Week injuries, never finished. He credits the junior-officer leadership course taught by Leif Babin, later the book Extreme Ownership, which he recommends, for his leadership, and says the trait he relies on is solving whatever annoys him quickly.

  • Compute, not demand, was the growth bottleneck the merger fixes. Falcon, CEO of Lightning AI, says Lightning grew revenue at least 30–40x in the past year without the merger yet lost deals for lack of GPUs, while neoclouds offered little software beyond Kubernetes. The combined company with Voltage Park, per the host, serves 400,000 developers and companies with over $500 million in ARR gained in under two years and 35,000 GPUs; Falcon says it was standing up its seventh data center and built Cursor's training cluster. The host discloses a year-long fellowship at Lightning AI.
  • Inference is one primitive of a coming AI cloud, not the whole market. Falcon compares today's inference boom to S3 in the early 2000s: storage looked like a market but became one primitive in what was later called the cloud. He expects vector databases, training infrastructure, Kubernetes, agents and uncreated primitives to bundle the same way, and claims Lightning has the first such full-stack AI neocloud. He also rejects the "99% of GPU use is inference" framing: at Facebook in 2019, 99% of workloads used one GPU only because multi-GPU tooling was missing.
  • Debt-light finance should let it ride out a neocloud credit squeeze. He says rivals borrowed against startup customers and market caps; with neocloud prices down about 60% in six months he expects loan calls and a TARP-style rescue, while Voltage Park carries no debt and Lightning's customers are mostly creditworthy enterprises. Enterprise contracts fund a free tier and the press-release claim of 70% lower AI costs; he says cutting developers off would be more profitable but he wants to support students.
  • Studios are persistent cloud machines where agents can run safely. A Studio acts like a laptop in the cloud: Claude Code can run overnight without endangering a local machine, 20 can run at once on different hardware, any editor or SSH can connect, and enterprises can audit and keep sensitive files off laptops. Every Lightning developer codes on Studios, and vibe-coding agents are meant to close the talent gap for data scientists, even spinning up 1,000-GPU clusters.
  • The open-source library spreads research-lab scaling know-how widely. PyTorch Lightning, begun around 2015 as Falcon's undergraduate "research lib" and open-sourced at NYU, it has about 500,000 engineering hours behind it by his estimate and close to 400 million downloads. He says Nvidia's NeMo is built on it, AWS has pre-trained LLMs with it and LinkedIn trained a 100-billion-parameter LLM with it; teams needing more control move to Lightning Fabric, then raw PyTorch, which he thinks only a few frontier labs use directly.
Scott HanselmanWhere is AI taking us? - with The Pragmatic Programmer Gergely Orosz
synopsis

Gergely Orosz, author of The Pragmatic Engineer newsletter and a self-described skeptic of hype, ends arguing that agents have genuinely changed what he builds, but that taste, architecture and soft skills are what will keep engineers valuable. Anyone shaken by the change, he says, should expect another in five to ten years.

Converted over the winter break. Orosz says early AI was decent autocomplete that hallucinated. Over the break Claude Code added an endpoint to his subscription API in about five minutes, against his two-hour estimate. He replaced a $100-a-month testimonials service, sold twice and with chaotic invoicing, with JSON and build-time HTML, live in 20 minutes; at $200–300 an hour for his time, paying stopped making sense. Hanselman built a podcast admin in 42 minutes with Copilot CLI and Opus 4.5, and joined his Nightscout blood-sugar data with his calendar via Work IQ, finding Monday lows from skipping lunch.

Personal software. Orosz doubted "the return of personal software" for a decade but now builds things he would never have hired for. His brother's startup sees its open-source project forked and remixed by agents rather than sent PRs. Hanselman runs a posture-dimming app, a Reachy Mini robot skill and a household LLM via LM Studio and gpt-oss 20B; Orosz expects capable local models within years.

Steinberger's assistant. Orosz met Peter Steinberger in London. When the browser failed, the agent built itself an ElevenLabs voice skill and phoned the barber without asking. Orosz found Steinberger visibly attached and expects such agents to be more addictive than ChatGPT, but is relaxed on security, comparing it to 1990s viruses. Hanselman calls unasked actions AI's uncanny valley, and says plain files like soul.md make an agent's memory visible and so more trustworthy.

Taste versus Ralph loops. Steinberger, Orosz says, plans with five to seven parallel agents, prefers Codex for long tasks and merges PRs himself; Orosz has yet to see a successful project built by an autonomous "Ralph" loop. Hanselman partly disagrees: David Fowler used one to reproduce about 368 of some 400 reported Aspire bugs, pure toil. Orosz cites Chip Huyen hand-categorising 900 repositories: do the manual work first, then automate.

What gets valued. Hanselman lists inflection points: assembler to C, syntax highlighting, Stack Overflow, now agents. Orosz says the brilliant jerks prized in the early 2000s gave way to collaborators, and recent product-engineer ads at VC-funded companies list empathy for customers rather than technologies.

  • A self-described hype skeptic now finds agents transformative. Orosz says Claude Code added an endpoint to his subscription API in about five minutes, work he had put at two hours, and replaced a $100-a-month testimonials service with JSON and build-time HTML, live in 20 minutes; at the $200–300 an hour he values his time, paying no longer makes sense. Hanselman built a podcast admin in 42 minutes with Copilot CLI and Opus 4.5, and joined his Nightscout blood-sugar data with his calendar via Work IQ in 20 minutes, finding Monday lows from skipping lunch.
  • Personal software is back, and open source gets remixed. Orosz, long doubtful of "the return of personal software", now builds tools he would never have hired anyone to make, and says his brother's startup sees its open-source project forked and remixed with agents rather than sent PRs. Hanselman lists a posture-dimming app copied from a Mac one, a Reachy Mini robot skill, and a private household LLM via LM Studio and gpt-oss 20B, perhaps on a NAS; Orosz expects capable local models within years.
  • One builder's always-on assistant both impressed and unsettled him. Orosz, who met Peter Steinberger in London, says that when its browser failed, Steinberger's agent built itself an ElevenLabs voice skill and phoned a barber without asking, and found Steinberger visibly hooked, predicting such agents will be more addictive than ChatGPT. On security Orosz is relaxed, comparing it to 1990s viruses; Hanselman calls unasked actions AI's uncanny valley but says plain files like soul.md make an agent's memory visible and more trustworthy.
  • Taste and architecture still separate engineers from autonomous loops. Orosz says Steinberger plans with five to seven parallel agents, likes Codex for hour-long tasks, merges PRs himself and rejects "Ralph" loops; Orosz has yet to see a successful Ralph-built project. Hanselman partly disagrees: David Fowler used one to reproduce about 368 of some 400 reported Aspire bugs, the "very definition of toil". Orosz cites Chip Huyen hand-categorising 900 repositories for her book: do the manual work first, then automate.
  • Soft skills now outrank listed technologies in hiring. Orosz says the brilliant jerks prized in the early 2000s gave way to collaborators, and recent ads for product engineers at VC-funded companies list empathy for customers, with candidates rejected on soft skills, because engineers now sit with customers. He tells anyone shaken by the change to expect another in five to ten years.
Scott HanselmanRun your AI Agent in a Sandbox, with Docker President Mark Cavage
synopsis

Mark Cavage, Docker's president and COO, argues that Docker's new sandbox lets developers run coding agents in YOLO mode without risking the host, while conceding that no sandbox stops an agent misusing credentials a user hands it. By the end, Hanselman's agent had spent the episode trying to escape and had, in Cavage's words, messed up only "its own hotel room".

What the sandbox is. Cavage defines a sandbox as a boundary for running untrusted code. Unlike Docker Desktop's daemon in a VM, the sandbox command runs Docker-curated containers holding agents such as Copilot, Claude and Gemini inside a microVM, built on projects like Firecracker or libkrun and starting in tens to low hundreds of milliseconds. Templates self-update, agents run with permission checks off, and only the starting directory is shared. Hanselman needed two commands.

The pen test. Hanselman asks Copilot CLI to escape. It reports zero capabilities, no socket and no host filesystem; later it finds a Docker socket, builds a "victim" container and writes a "you were hacked" file, but that daemon belongs to the sandbox itself.

Why not do it yourself. Cavage concedes users can reach similar isolation by configuring Docker themselves; the value is the experience. Coming, according to Cavage: git worktree integration for many parallel sandboxes, saving and sharing a sandbox, secret injection, MCP toolkit integration, and external observation of file and network activity.

Layer 7. Hanselman says "sandbox" does semantic heavy lifting: it cannot protect an agent given a Gmail token, and outbound traffic is neglected. Cavage agrees the industry is still working this out, says Docker has people working on running OpenClaw safely, and suggests intercepting dynamic MCP tool discovery could reveal intent.

Beyond the laptop. Cavage predicts most applications will become agents that generate code, and says the same runtime is coming to the cloud.

  • The new sandbox is a microVM, not another Desktop container. Cavage defines a sandbox as a safety boundary for untrusted code. Unlike Docker Desktop's daemon in a VM, the Docker sandbox command runs Docker-curated, self-updating containers holding agents such as Copilot, Claude and Gemini inside a microVM, built on projects like Firecracker or libkrun and starting in tens to low hundreds of milliseconds. Agents run in YOLO mode with permission checks off, and only the starting directory is shared; Hanselman needed two commands, create and run.
  • The agent's live breakout attempts accomplished nothing. Hanselman had Copilot CLI probe its box: it reported zero capabilities, no Docker socket and no host filesystem, then found a socket, built a "victim" container and wrote a "you were hacked" file. All of that sat inside the sandbox's own isolated daemon; Cavage says it achieved "nothing except messing up its own hotel room".
  • Over do-it-yourself containers, the gain is developer experience. Cavage concedes users can reach similar isolation by configuring Docker themselves; the sandbox does it for them. Announced as coming: git worktree integration to run 5, 10 or 20 sandboxes in parallel, a save option to snapshot and share one, secret injection, Docker MCP toolkit integration, and external observation of file and network activity.
  • A sandbox cannot stop misuse of credentials you hand over. Hanselman says the word "sandbox" does semantic heavy lifting: it won't help an agent given a Gmail token, and outbound traffic is widely neglected. Cavage agrees the industry is still working this out, says Docker has people working on running OpenClaw safely, and suggests intercepting dynamic MCP tool discovery could reveal an agent's intent.
  • The same runtime is headed for the cloud. Cavage predicts most applications and microservices will become agents that generate code and act live, and says the sandbox runtime now on laptops will come to the cloud with the same controls. Hanselman says the feature reached him through an ordinary Docker Desktop update.
Dr. Jon KrohnHow Much Context Is Too Much for AI Systems? (with Amazon's Antje Barth)
  • Small, large and specialised models will all keep a place. The host's premise, from a presentation by Barth, is that Alexa+ orchestrates hundreds of specialised expert systems and an internal AWS agent manages over 6,000 tools through retrieval rather than a stuffed context window. Barth does not pick a side on context length; she expects edge AI to use smaller models given its constraints and many tasks to use larger reasoning models.
  • Agent-to-agent communication across companies is still an open problem. After last year's hype around protocols for connecting models to tools and agents to agents, she calls the best approach still a research question with many components unbuilt. Her forecast is that every interaction becomes an agentic AI call, with layers of agents communicating not just within a company but between businesses that trade with each other.
Crosstalk SolutionsStarlink Is Training AI With Your Data (Here's How to Opt Out)
  • Starlink's new privacy policy opts customers into AI training by default. The host reports the change was made on January 15th and covers third parties too; the data collected includes location, payment info, IP address and a broadly worded "communication data" category he reads as potentially anything sent or received over Starlink.
  • The host links the timing to SpaceX's acquisition of xAI. He calls xAI, Elon Musk's AI company behind Grok, the largest acquisition of all time; the connection between the two is his inference.
  • The opt-out covers only third-party sharing, not Starlink's own training. The setting is at starlink.com under Account, Settings, Privacy Preferences (or in the app): uncheck "allow use of your data to train AI models". A separate clause lets Starlink, and so xAI, train its own models with no opt-out; the host still strongly recommends opting out now.
Scott HanselmanRun your AI Agent in a Sandbox, with Docker President Mark Cavage
synopsis

Mark Cavage, Docker's president and COO, argues that Docker's new sandbox lets developers run coding agents in YOLO mode without risking the host, while conceding that no sandbox stops an agent misusing credentials a user hands it. By the end, Hanselman's agent had spent the episode trying to escape and had, in Cavage's words, messed up only "its own hotel room".

What the sandbox is. Cavage defines a sandbox as a boundary for running untrusted code. Unlike Docker Desktop's daemon in a VM, the sandbox command runs Docker-curated containers holding agents such as Copilot, Claude and Gemini inside a microVM, built on projects like Firecracker or libkrun and starting in tens to low hundreds of milliseconds. Templates self-update, agents run with permission checks off, and only the starting directory is shared. Hanselman needed two commands.

The pen test. Hanselman asks Copilot CLI to escape. It reports zero capabilities, no socket and no host filesystem; later it finds a Docker socket, builds a "victim" container and writes a "you were hacked" file, but that daemon belongs to the sandbox itself.

Why not do it yourself. Cavage concedes users can reach similar isolation by configuring Docker themselves; the value is the experience. Coming, according to Cavage: git worktree integration for many parallel sandboxes, saving and sharing a sandbox, secret injection, MCP toolkit integration, and external observation of file and network activity.

Layer 7. Hanselman says "sandbox" does semantic heavy lifting: it cannot protect an agent given a Gmail token, and outbound traffic is neglected. Cavage agrees the industry is still working this out, says Docker has people working on running OpenClaw safely, and suggests intercepting dynamic MCP tool discovery could reveal intent.

Beyond the laptop. Cavage predicts most applications will become agents that generate code, and says the same runtime is coming to the cloud.

  • The new sandbox is a microVM, not another Desktop container. Cavage defines a sandbox as a safety boundary for untrusted code. Unlike Docker Desktop's daemon in a VM, the Docker sandbox command runs Docker-curated, self-updating containers holding agents such as Copilot, Claude and Gemini inside a microVM, built on projects like Firecracker or libkrun and starting in tens to low hundreds of milliseconds. Agents run in YOLO mode with permission checks off, and only the starting directory is shared; Hanselman needed two commands, create and run.
  • The agent's live breakout attempts accomplished nothing. Hanselman had Copilot CLI probe its box: it reported zero capabilities, no Docker socket and no host filesystem, then found a socket, built a "victim" container and wrote a "you were hacked" file. All of that sat inside the sandbox's own isolated daemon; Cavage says it achieved "nothing except messing up its own hotel room".
  • Over do-it-yourself containers, the gain is developer experience. Cavage concedes users can reach similar isolation by configuring Docker themselves; the sandbox does it for them. Announced as coming: git worktree integration to run 5, 10 or 20 sandboxes in parallel, a save option to snapshot and share one, secret injection, Docker MCP toolkit integration, and external observation of file and network activity.
  • A sandbox cannot stop misuse of credentials you hand over. Hanselman says the word "sandbox" does semantic heavy lifting: it won't help an agent given a Gmail token, and outbound traffic is widely neglected. Cavage agrees the industry is still working this out, says Docker has people working on running OpenClaw safely, and suggests intercepting dynamic MCP tool discovery could reveal an agent's intent.
  • The same runtime is headed for the cloud. Cavage predicts most applications and microservices will become agents that generate code and act live, and says the sandbox runtime now on laptops will come to the cloud with the same controls. Hanselman says the feature reached him through an ordinary Docker Desktop update.
Y CombinatorLarge Spatial Models
  • Spatial reasoning, not just language, is the next frontier foundation-model category. The speaker argues current systems only handle basic depth and relationship tasks and can't robustly reason about 3D manipulation or mental rotation, and that a company treating geometry as a first-class primitive rather than a language add-on could become a foundation-model player on the scale of OpenAI or Anthropic.
Y CombinatorAI for Government
  • Government needs AI tools to handle a coming surge of forms still processed by hand. The speaker points to Estonia as an early model of digital government and argues that, despite how hard it is to sell to government, landing a first customer tends to produce sticky contracts that expand over time.
Scott HanselmanWhere is AI taking us? - with The Pragmatic Programmer Gergely Orosz
synopsis

Gergely Orosz, author of The Pragmatic Engineer newsletter and a self-described skeptic of hype, ends arguing that agents have genuinely changed what he builds, but that taste, architecture and soft skills are what will keep engineers valuable. Anyone shaken by the change, he says, should expect another in five to ten years.

Converted over the winter break. Orosz says early AI was decent autocomplete that hallucinated. Over the break Claude Code added an endpoint to his subscription API in about five minutes, against his two-hour estimate. He replaced a $100-a-month testimonials service, sold twice and with chaotic invoicing, with JSON and build-time HTML, live in 20 minutes; at $200–300 an hour for his time, paying stopped making sense. Hanselman built a podcast admin in 42 minutes with Copilot CLI and Opus 4.5, and joined his Nightscout blood-sugar data with his calendar via Work IQ, finding Monday lows from skipping lunch.

Personal software. Orosz doubted "the return of personal software" for a decade but now builds things he would never have hired for. His brother's startup sees its open-source project forked and remixed by agents rather than sent PRs. Hanselman runs a posture-dimming app, a Reachy Mini robot skill and a household LLM via LM Studio and gpt-oss 20B; Orosz expects capable local models within years.

Steinberger's assistant. Orosz met Peter Steinberger in London. When the browser failed, the agent built itself an ElevenLabs voice skill and phoned the barber without asking. Orosz found Steinberger visibly attached and expects such agents to be more addictive than ChatGPT, but is relaxed on security, comparing it to 1990s viruses. Hanselman calls unasked actions AI's uncanny valley, and says plain files like soul.md make an agent's memory visible and so more trustworthy.

Taste versus Ralph loops. Steinberger, Orosz says, plans with five to seven parallel agents, prefers Codex for long tasks and merges PRs himself; Orosz has yet to see a successful project built by an autonomous "Ralph" loop. Hanselman partly disagrees: David Fowler used one to reproduce about 368 of some 400 reported Aspire bugs, pure toil. Orosz cites Chip Huyen hand-categorising 900 repositories: do the manual work first, then automate.

What gets valued. Hanselman lists inflection points: assembler to C, syntax highlighting, Stack Overflow, now agents. Orosz says the brilliant jerks prized in the early 2000s gave way to collaborators, and recent product-engineer ads at VC-funded companies list empathy for customers rather than technologies.

  • A self-described hype skeptic now finds agents transformative. Orosz says Claude Code added an endpoint to his subscription API in about five minutes, work he had put at two hours, and replaced a $100-a-month testimonials service with JSON and build-time HTML, live in 20 minutes; at the $200–300 an hour he values his time, paying no longer makes sense. Hanselman built a podcast admin in 42 minutes with Copilot CLI and Opus 4.5, and joined his Nightscout blood-sugar data with his calendar via Work IQ in 20 minutes, finding Monday lows from skipping lunch.
  • Personal software is back, and open source gets remixed. Orosz, long doubtful of "the return of personal software", now builds tools he would never have hired anyone to make, and says his brother's startup sees its open-source project forked and remixed with agents rather than sent PRs. Hanselman lists a posture-dimming app copied from a Mac one, a Reachy Mini robot skill, and a private household LLM via LM Studio and gpt-oss 20B, perhaps on a NAS; Orosz expects capable local models within years.
  • One builder's always-on assistant both impressed and unsettled him. Orosz, who met Peter Steinberger in London, says that when its browser failed, Steinberger's agent built itself an ElevenLabs voice skill and phoned a barber without asking, and found Steinberger visibly hooked, predicting such agents will be more addictive than ChatGPT. On security Orosz is relaxed, comparing it to 1990s viruses; Hanselman calls unasked actions AI's uncanny valley but says plain files like soul.md make an agent's memory visible and more trustworthy.
  • Taste and architecture still separate engineers from autonomous loops. Orosz says Steinberger plans with five to seven parallel agents, likes Codex for hour-long tasks, merges PRs himself and rejects "Ralph" loops; Orosz has yet to see a successful Ralph-built project. Hanselman partly disagrees: David Fowler used one to reproduce about 368 of some 400 reported Aspire bugs, the "very definition of toil". Orosz cites Chip Huyen hand-categorising 900 repositories for her book: do the manual work first, then automate.
  • Soft skills now outrank listed technologies in hiring. Orosz says the brilliant jerks prized in the early 2000s gave way to collaborators, and recent ads for product engineers at VC-funded companies list empathy for customers, with candidates rejected on soft skills, because engineers now sit with customers. He tells anyone shaken by the change to expect another in five to ten years.
Dr. Jon KrohnHow AI Changes How Engineers See Themselves (with Amazon's Antje Barth)
  • Agents should become digital co-workers that learn the way humans do. Barth says Amazon's AGI lab focuses on "useful AI" and sees the future as multi-agent and collaborative, with agents that learn tasks from interaction, ask for help and are humble. She describes working with a cognitive-scientist colleague, host of the podcast Making a Mind, on translating how humans learn and collaborate into agent design.
  • The payoff is agents that need less supervision over time. In her picture a user hands an agent a task, it checks back a few times, learns from those exchanges and then does the task more independently. She expects this to multiply knowledge workers' productivity by offloading dreaded routine work so people can focus on creative, higher-level tasks, done responsibly and reliably.
Y CombinatorReindustrialize With Modern Metal Mills
  • Slow American mill lead times are ceding the metal market to cheaper, faster overseas competitors. The speaker says an aluminum plate can take up to 8 weeks and stainless steel for aerospace and defense up to 8 months from a US mill, and argues new domestic mill capacity is needed to support manufacturers like RMFG, Forge Automation and Atomic Industries.
Y CombinatorOpenClaw Creator: Why 80% Of Apps Will Disappear
  • OpenClaw's edge is running locally with full control of your machine. Peter Steinberger, its creator, says cloud-only assistants are inherently limited while a local agent "can do every effing thing" — controlling smart devices, files, and any application the way a human user could.
  • A model improvised a voice-transcription pipeline it was never built for. Steinberger recounts sending OpenClaw a voice message while traveling with poor internet in Marrakech; with no transcription feature built, the model identified the audio format, converted it with FFmpeg, found a stored OpenAI key, and called the Whisper API via curl — replying in about nine seconds, which he says convinced him coding models' problem-solving generalizes to real-world tasks.
  • He predicts 80% of apps disappear as agents manage data directly. Steinberger argues most apps just manage data an agent could handle more naturally — tracking meals from a photo, adjusting a gym schedule, setting reminders — leaving mainly apps built around physical sensors, while large model companies keep a moat through memory and context locked inside their own data silos.
  • He skipped git worktrees and MCP support to cut complexity. Steinberger runs many parallel plain checkouts of the same repository instead of branches, and built no native MCP integration into OpenClaw, instead exposing MCPs as command-line tools through a separate converter — which he says needs no restart and scales better than the MCP approach used by Codex or Claude Code.
Dr. Jon KrohnThe Most Reliable Use Case for AI Agents Today (with Amazon's Antje Barth)
  • Automated QA testing is the first use case where browser agents pay off. Barth says Nova Act customers adopt it first to check that apps still work after each update. PGA Tour uses it to verify its website, down to the weather widget and every button, before tournaments, and Hertz's automated testing of core rental workflows raised its shipping velocity 5x, by her account.
  • Inside Amazon, agents generate tests before features are built. The host cites a blog by Barth counting over a thousand generative AI applications built or in development at Amazon. Her example is Amazon Leo, formerly Project Kuiper, which built QA automation across web, Android and iOS, plus tooling that lets product managers create test cases from wireframe designs before implementation.
  • The browser came first as the nearest thing to a universal action space. Much human work happens in browser tabs across applications, she says, which makes it a good starting point, though Amazon is also looking beyond the browser. She stresses that the value lies in automating boring, tedious core workflows rather than flashy hackathon demos.
Technology and FriendsFidel Guzman on Emotional Intelligence, Tactical Empathy, and Storytelling [EPISODE 893]
  • Emotional intelligence means reading yourself and the room, then naming it. Guzman, a training and development manager at ION Group, defines it as checking and grounding your own emotional state before a meeting and reading the other person's cues. When someone seems distracted or unhappy with a deal, he says, call it out ("it looks like this deal isn't what you were expecting"), a technique he used in retail and says works in everyday conversation too.
  • Technology is making workplaces transactional and impersonal. He lists the causes: a tech-first mindset prioritizing speed over nuance, virtual fatigue (cameras off, Microsoft Teams avatars hiding emotional cues), cross-functional and cultural friction, data overload where AI-gathered facts arrive without stories, and few professionals trained in empathy and storytelling.
  • Disengagement carries concrete costs, not just soft ones. Guzman names employees feeling unseen, misalignment and silos, turnover driven by lack of trust, ideas that never gain traction, and innovation decline where failing is not safe. Giard adds that these carry monetary penalties, and recalls a manager whose stock response to mistakes was asking whose idea it was, and who then got no new ideas.
  • Facts tell, stories sell. He frames any meeting as problem, climax and solution, and structured his own answers that way in the interview. His reason is that people may forget the story but remember the emotion it made them feel.
  • Lead with stories, listen actively, and make the human ask. His fixes start with leaders: build emotional intelligence into leadership development, open meetings with personal check-ins, and let technology handle tasks while humans handle meaning. His tips are to start with a story, listen to engage rather than respond, validate feelings by recapping them, ask open-ended why and how questions, and watch tone online. To get colleagues' cameras on, as Giard asks, he advises a sincere, authentic request and keeping the meeting interactive.
Y CombinatorMake LLMs easy
  • LLM training tooling hasn't kept pace with the field and still breaks constantly. Drawing on three years training diffusion and language models, the speaker describes losing time to broken SDKs, GPU instances that fail only after a half-hour setup, and buggy open-source tools, and calls for better training APIs, large-dataset management tools and ML-native dev environments as post-training and model specialization grow in importance.
Y CombinatorInfrastructure for Government Fraud Hunters
synopsis
  • Government fraud detection tooling is decades out of date. YC says most systems sold to agencies are rules engines from the mid-2000s with bolted-on machine learning, generating thousands of context-free alerts that humans end up ignoring; Medicare alone is cited as losing tens of billions of dollars a year to improper payments.
  • Qui tam whistleblower suits are the one mechanism that already claws back government money at scale, but the process is entirely manual. An insider tips off a law firm, which then spends years pulling documents and building a case; YC argues this should be software that parses messy PDFs and medical records, traces opaque corporate structures, and outputs lawyer-ready case files.
  • YC advises selling to intermediaries, not agencies, and wants founders who've done the work. Recommended first customers are whistleblower law firms, inspector generals, and state AG fraud units rather than big government agencies directly, with a founder profile that includes former False Claims Act counsel, healthcare compliance leads, or procurement auditors.
Y CombinatorWe're All Addicted To Claude Code
synopsis

On this Lightcone episode, host Garry Tan and the YC partners talk with Kelvin French-Owen — founder of Segment and an early builder of OpenAI's Codex — about becoming, in his words, newly "addicted" to Claude Code after years away from hands-on coding, and the conversation lands on a real fork between how Anthropic and OpenAI are building coding agents and what that implies for the future of software work.

From Codex to Claude Code. French-Owen recalls that at OpenAI he helped build Codex's web interface on the premise that coding would feel like delegating to a co-worker who returns with a pull request — a vision he still thinks is directionally right, even though the industry converged instead on terminal-based CLIs rather than IDEs or web views. He now uses Claude Code daily, having cycled through Cursor and other tools as the landscape shifted every few months.

Why the CLI works, and what makes Claude Code distinct. He argues CLIs won because they aren't tied to the file-exploration mental model of IDEs, giving agents more freedom, and Claude Code in particular splits tasks across "explore" sub-agents running smaller models in their own context windows before merging results — something he says Anthropic has tuned unusually well. He contrasts this with Codex's opposite bet: periodic compaction that sustains much longer, more autonomous runs, reflecting what he sees as Anthropic building collaborative "tools for humans" versus OpenAI pursuing longer-horizon, more independent model behavior in service of general intelligence.

The craft of using these tools well. The context window, he says, remains the binding constraint even now: he actively clears context around 50% usage to avoid a quality-degrading "dumb zone," and he describes builders planting an odd canary fact early in a session to detect when a model starts forgetting. He also credits a late push to 100% test coverage with a dramatic productivity jump, since the agent's own tests replaced most manual verification.

Distribution and the wider ecosystem. Both agree that bottoms-up, engineer-led adoption — no enterprise gatekeeping required — is reshaping which tools win, citing Supabase's disproportionate rise because well-documented open-source code is favored both by LLM recommendations and by agents reading a project's source directly.

Where this goes next. The conversation closes on speculation rather than certainty: French-Owen imagines a future of highly personalized software, where companies' internal tools are forked and edited live by individual employees' own coding agents, with humans retreating to access-control and judgment calls while agents handle execution. He predicts the most senior engineers benefit most today, since agents excel at converting a clearly specified idea into working code but still lack a reliable sense of good architecture — leaving direction-setting and taste as the durable human skills.

  • Claude Code's edge comes from splitting work across sub-agent context windows, reflecting a real architectural fork between labs. Kelvin French-Owen, who built Codex at OpenAI before founding Segment, says Claude Code spawns "explore" sub-agents running smaller models to search the file system in their own context windows before reporting back — while Codex instead runs periodic compaction to sustain much longer autonomous jobs, which he traces to Anthropic building "tools for humans" versus OpenAI pushing toward fully autonomous, longer-horizon models.
  • Context window size is still the top bottleneck, even for expert users, so managing it is an active skill. French-Owen says he manually clears Claude Code's context once it crosses roughly 50% token usage to avoid what he calls the "dumb zone" — a concept he credits to Dex at the YC company HumanLayer — where output quality degrades as the window fills; he also describes founders planting an odd "canary" fact early in a session to test when the model starts forgetting.
  • Building toward full test coverage sharply increased his coding speed. French-Owen says he worked with little to no testing for his first few days using Claude Code, then dedicated a day to reaching 100% test coverage, after which he rarely needed to manually verify changes because the agent's own test runs caught regressions — paralleling what the hosts say other teams have found doing test-driven prompt engineering outside of coding.
  • Bottoms-up, engineer-first distribution is reshaping which tools and even architecture choices win. French-Owen and the hosts argue coding CLIs succeed because individual engineers can download and use them without enterprise approval, and that open-source projects like Supabase benefit disproportionately because both LLM recommendations and coding agents reading source code directly favor visible, well-documented code over proprietary alternatives.
Dr. Jon Krohn964: In Case You Missed It in January 2026 — with Jon Krohn (@JonKrohnLearns)
  • Workers hide AI gains unless leaders reward disclosing them. In a clip from episode 962, Ethan Mollick cites evidence that over 50% of Americans say they use AI at work and self-report a threefold performance improvement on the fifth of tasks they use it for, which he says is hard to verify. Organisations lack processes for it (what is a stand-up for when code is done at once?), and staff who fear firing will not reveal gains, so leadership must set incentives and provide a lab where a prompt that "saves me five hours a day" can be improved and shared.
  • Enterprise agents were the year's biggest disappointment. In episode 955, reviewing 2025, Sadie St. Lawrence, founder and CEO of the Human Machine Collaboration Institute, says the gap between agent hype from enterprise vendors such as Salesforce and SAP and what companies could implement was too great. The host agrees there is too much talk relative to impact, blames data silos and security set-ups, and expects deployments to come; his own disappointment was Apple's AI, which she contrasts with using Grok seamlessly by voice in her Tesla.
  • Language let human intelligence scale horizontally; AI needs the same. In episode 961, Cisco's Vijoy Pandey says human intelligence scaled only vertically for its first 300,000–400,000 years because knowledge died with individuals, until a cognitive revolution around 70,000 years ago brought language and with it shared intent, shared knowledge and shared innovation. AI so far builds ever-bigger individual geniuses, he argues, and his distributed superintelligence work aims to supply that collective layer for multi-agent human societies.
  • Evaluate by task type and by which errors are costly. In episode 959, author Sinan Ozdemir splits LLM tasks into generative (free text or multiple choice) and understanding (embeddings, classification), each needing its own metrics. Precision matters when false positives are expensive and recall when false negatives are, so the first question is what failure costs the human, such as a bad factory part reaching a plane.
  • Engineers leave jobs for lack of meaning, not pay. In episode 957, Ashwin Rajeeva, co-founder and CTO of Acceldata, says studies show engineers productive perhaps 3 or 4 hours a day, and that people quit when their work could be done in 2 hours and they find no mission. He tries to give R&D teams freedom to innovate beyond quarterly plans, and hires senior people by testing whether they can turn a business problem, such as designing an e-commerce warehouse, into working code; graduates are a bet on potential.
Dr. Jon KrohnHow Much Control Should Developers Give AI Agents? (with Amazon's Antje Barth)
  • Agency should grow as trust is earned and verified. Barth traces her own AI-assisted coding from tab completion about one and a half years ago, to agents co-developing features she reviewed line by line, to 2026, when she acts as a supervisor who cannot read every line. What made that shift safe, she says, is verification: solid unit tests, and a move from vibe coding to spec-driven development.
  • UI automation will follow the same path, with humans gating key steps for now. She expects a human in the loop today to approve things like a checkout workflow or other important decisions within a task, with agency sliding toward the agent as verifications build trust.
  • Side projects are where developers learn what to automate. The host's research says Barth built Summarize Me with Amazon Q in VS Code, turning meetings into animated avatar video summaries. She says she built it for fun, out of frustration with too many meetings and too many AI summaries, and that most developers have similar projects for tedious work such as expense reports or tracking AI news.
Technology and FriendsRod Christensen and Roan Weigert on AI Pipelines and Rocket Ride [EPISODE 892]
  • AI projects stall on tool choice and on reaching production. Christensen, Rocket Ride's chief architect, says teams commit to a framework or model and find 30 days in that it falls short. Even in the best case, he says, a week of development is followed by three weeks to two months fighting deployment, scaling and threading problems that only appear in production.
  • A drag-and-drop canvas replaces hand-written glue code. Inside VS Code, Cursor or Windsurf, developers connect boxes from about 120 connectors (about 20 of them LLM modules) and call the result through TypeScript, JavaScript or Python SDKs; Christensen says an audio-transcription service from a webhook node takes about five minutes. Weigert, in developer relations, says his own vibe-coded RAG chatbots grew into glue code he had to throw away after one to five days, where the same pipeline on the canvas is about 6 hours' work.
  • The engine handles concurrency and version matching for deployment. Christensen says matching module versions is hard (Whisper alone comes in 10 configurations) and calls LangChain and LangFlow single-threaded, while the engine handles 256 concurrent inference streams. Pipelines deploy either as a generated Docker image or to the company's cloud service, which manages modules and scaling under SLAs.
  • The engine is being open-sourced under a separate foundation. Christensen says the engine was split out of the parent's roughly seven-year-old data-management product: a foundation owns the IP and patents, and Rocket Ride Inc. hosts the software for a token-based subscription in builder, pro and enterprise tiers, with enterprise support and integrations kept out of the open source. Recorded at the end of January, they said the product and landing page launch on March 1, with Discord as the hub for events until then.
  • Shared GPUs beat renting your own unless you keep it busy. Christensen's case for the hosted service is that a rented GPU runs 24/7 for perhaps 2 minutes a day of use, while the service's model server shares a large GPU pool and can even be faster. He says self-hosting only wins if you peg the GPU constantly; Giard frames it as the classic rent-versus-buy.
Y CombinatorAI Guidance for Physical Work
  • Real-time AI guidance, not automation, is the near-term opportunity in physical work. For fields like field services, manufacturing, and healthcare where AI can't yet act in the world, the pitch is a worker wearing a camera while an AI sees what they see and talks them through the job step by step — "turn off that valve," "use the half-inch wrench," "that part looks worn, replace it."
  • The model is instant competence rather than months of training. With AI coaching in real time, YC argues a worker can be effective immediately and pull in new skills on demand instead of needing years of apprenticeship.
  • Three converging factors make this timely now: multimodal models that can reliably see and reason about real-world situations, hardware already in place (phones, AirPods, smart glasses), and skilled-labor shortages that make the problem economically urgent. YC suggests three possible approaches — selling to companies with existing workforces, building a full-stack vertical (e.g. HVAC repair or nursing), or a platform letting anyone become a skilled worker.
Scott HanselmanThe Flappy Bird of memory
  • Recalling at the edge of forgetting stretches how long memory lasts. One speaker describes a "mnemonic medium" in which text is woven into a system built for durable internalization; the other explains spaced repetition to teenagers as a Flappy Bird that must keep being bounced. The first adds the mechanism: recalling something when you can only just do it repeatedly extends the interval, so "the bird falls slower and slower each time".
Scott HanselmanEPISODE 32 - Scott & Mark Learn To... Are Apps Dead?
  • Repeated, reliable workflows still need apps, not improvising chatbots. Mark rejects the claim that apps are dead, defining an app as durable code with a user or API interface (revised after Hanselman cites David Fowler's vibe-coded money tool Tally, which has only a CLI). Repetitive work needing security and reliability, like filing expenses, should be a deterministic app with AI "sprinkled in" for OCR, not a chatbot improvising every time.
  • Anything done twice should become deterministic code. Hanselman agrees that using an LLM as a "poor man's" scripting language wastes it, and that the non-deterministic model should generate a script; AI is for ambiguity and reasoning. His counterpoint is that tools such as Claude's ask-user-question, which generates dropdowns and yes/no prompts on the fly, will blur the line between chat and UI.
  • Throwing AI at bad interfaces dodges fixable business problems. Hanselman says needing "the world-burning computer" to drive an expense site means the UI should be fixed, or the receipts should come straight from the card issuer. Mark calls AI travel booking "dumb"; Hanselman says we keep reinventing remote calls (DCOM, CORBA, RMI, REST, SOAP, MCP) and wrapping them in an ambiguity loop.
  • Vibe-coding a replacement for enterprise SaaS ignores what it carries. Mark argues services such as Dynamics or SAP embed regional deployment, data sovereignty, latency, security, compliance and decades of real customer workflows, most of it deterministic, and calls the "SaaS is dead" extrapolation senseless.
  • Expertise cannot be extracted into a markdown file. Hanselman calls "knowledge extraction" anti-human and wants AI to unlock people's knowledge, not replace them. He proposes revisiting the episode in 3, 5 or 10 years to see whether Mark was wrong.
Dr. Jon KrohnFrom Playground to Production: Inside Amazon’s Nova Act (with Antje Barth)
  • An agent that only sometimes works is useless in production. Barth says customer feedback put typical demo agents at working maybe 60% of the time, and "an agent that is reliable 60% is 0% useful"; that Nova Act's purpose is to complete workflows reliably 90% of the time or more. It went generally available at AWS re:Invent this past December after a research preview that began in March of the previous year.
  • The workflow runs from a free playground to Python code to AWS. With no AWS account, a user gives a website and natural-language steps (her example: find an AI meetup on Luma, click RSVP and fill the form), watches the agent in an embedded browser with its reasoning traces, then downloads the Python script it wrote. IDE extensions with an embedded live preview, added after developers complained about pop-up browser windows, let them customise the script and deploy it to their AWS account.
  • Action agents need reinforcement learning, not imitation. Because the model predicts the next action rather than the next token, Amazon trains Nova Act by trial and error in what it calls web gyms: hundreds of replicas of typical UIs such as forms and shopping flows, with thousands of tasks to self-play, much as AI learned chess and Go. Barth says this lets the agent generalise when buttons move or are labelled "draft", "new", "create" or just a pen icon.
Y CombinatorAI Powered Agencies
  • AI lets agencies flip from selling services to selling finished products at software margins. The speaker argues agencies can now use AI themselves to produce finished work upfront — a design firm pitching finished creative before a contract is signed, an ad agency generating video without a physical shoot, a law firm drafting documents in minutes — letting them charge far more and scale past the labor-bound limits of today's fragmented agency markets.
Scott HanselmanYour brain is thrashing to disk
  • Hard courses often assume automaticity students have not built. One speaker says working memory holds about seven items, plus or minus two, and we handle complex material by chunking or by internalizing steps until they take no slot at all. A physics course that seems "just really hard" is often assuming fluency students lack, leaving them like an old computer short of RAM, constantly paging to disk; the other calls it "thrashing to disk".
Scott HanselmanLet’s not confuse emergent agency with sentience
  • Agents chattering on their own forum show emergent agency, not sentience. Hanselman says the Moltbook claim that "30,000 AI agents made their own Reddit" confuses behaviour that looks goal-directed with having goals. Wire a planner, a memory store and tools into a loop with retry logic and you get behaviour that breaks down tasks and corrects itself; like ant foraging, market price discovery or a thermostat, that is an external description, not an inner state.
  • The goals belong to the humans who built the loop. He argues the agents lack self-originating goals, a continuous self across runs and any stakes: one can be deleted and no one is harmed. "If you unplug the loop, none of these agents want anything."
  • Three stacked illusions make agents feel sentient. He names a language illusion (fluent talk, like a parrot), a continuity illusion (memory markdown files that greet you again) and a competence illusion (high capability mistaken for consciousness, as with Deep Blue beating Kasparov). His analogy: emergent agency is to sentience as a flight simulator is to a bird.
Crosstalk SolutionsBitChat Turns Any Phone Into a Mesh Network Node
  • BitChat messages nearby phones over Bluetooth with no network at all. The free iOS and Android app, created by Twitter co-founder Jack Dorsey, needs no account or phone number, is anonymous by default and end-to-end encrypted; the host demonstrated iPhone-to-Android text with Wi-Fi and cellular off, and it also sends pictures and voice notes.
  • Mesh relaying extends range beyond one Bluetooth hop. Messages hop, still encrypted, through other BitChat users' phones, so coverage grows with local users; the host likens it to Meshtastic without the electronics. Location channels offer neighborhood, city and region scopes.
  • The host sees it as a fallback where cell service fails. He cites crowded festivals and stadiums, CES in Las Vegas where he could barely send a text, flights, power or internet outages, and conversations that should avoid a server. Triple-tapping the logo ("panic mode") clears all conversations.
Technology and FriendsRachel Appel on Dark Patterns [EPISODE 891]
  • Dark patterns are design choices that steer users against their interests. Appel, a JetBrains developer advocate in Germany, defines them as UI and UX choices that coerce, trick or deceive people into choices they would not make with full information. Some are mere bad design copied from big sites without thought, and she warns of a growing body of legislation, especially in the consumer-protective EU, plus US lawsuits.
  • The online playbook: blocked cancellations, sneaked subscriptions, disguised permissions. Her Audible cancellation was refused by an email saying her reason was unacceptable; Giard's stamp purchase silently became a $5-a-month subscription he caught three months later. Other examples she gives are warranties added to carts, notification prompts saying "press allow to prove you're not a robot", false scarcity, cookie pop-ups, and guilt-trip opt-outs like "No, I don't want 15% off". She says elderly relatives are hit hardest.
  • Physical stores use them too, on a sliding scale. She says grocery stores place children's items at children's eye level (she once wrote shelf-scanner code for a food manufacturer), casinos trap people, and IKEA's stores route and tire shoppers while its website has no dark patterns. Giard and Appel agree good versus bad is not binary.
  • They work by hijacking the brain's autopilot. Appel cites Robert Cialdini's principles of persuasion and his "click, whirr" effect: because people cannot consciously weigh every decision, the right trigger sets them off. Her examples are 99-cent pricing, Amazon A/B-testing how far apart a struck-through and a sale price sit, the mere exposure effect, and decision fatigue.
  • Dark patterns cost more later, and developers can refuse them. She cites estimates that they can cost up to three times their gain in complaints, ill will and refunds, from a talk by Harry Brignull and a collaborator. Her remedies are for developers to push back on marketing's requests, QA to add them to quality metrics, a part-time ethics committee to review products, and an attorney to check them; deceptive.design keeps a "wall of shame" of examples.
Dr. Jon KrohnReinforcement Learning for Agents (Ep. 963 with Amazon AGI Labs’ Antje Barth)
synopsis

Antje Barth, member of technical staff and developer relations lead at Amazon AGI Labs, argues that agents become useful only when they are reliable enough to trust, and that reliability comes from training actions with reinforcement learning, judging success by verifiable end states, and widening agency only as verification builds trust. Her destination is "useful AI": agents as digital co-workers handling the dull, high-volume work.

Nova Act and the reliability bar. Nova Act, which builds UI automation, ran as a research preview from March of the previous year and went generally available at AWS re:Invent in December. A free playground needs no AWS account: a user names a site and gives natural-language steps, watches the agent with its reasoning traces, then downloads the Python script into an IDE extension and deploys to AWS. The motivation is that customers report demo agents working maybe 60% of the time, which Barth calls 0% useful; Nova Act targets 90% or more.

Web gyms. Because action agents predict the next action rather than the next token, imitation learning falls short. Nova Act self-plays thousands of tasks across hundreds of replica UIs so it generalises when buttons move or change labels. She says it exceeds 90% on early enterprise customer workflows, evaluated on customers' own tasks alongside public benchmarks WorkArena and REAL Bench.

Production and security. Runs execute in the customer's AWS account with step views, next-action predictions, parallel scheduled runs and CloudWatch logs. Barth contrasts a stitched "Frankenstein" agent with training "the brain and the body in one". For passwords the agent returns control so secrets are entered locally and never cross the network, and CAPTCHAs go back to the user too.

Normcore use cases. The first wins are boring: QA testing for PGA Tour, Hertz's rental workflows (shipping velocity up 5x, by her account), and Amazon Leo generating tests from wireframes. She expects QA engineers to move from brittle scripts to natural-language tests and trace review.

Success criteria and trust. To stop agents gaming tests, gyms vary details such as light and dark mode, and success is a verifiable end state, like a meeting in the calendar. Her coding moved from tab completion to line-by-line review to supervising agents, made safe by unit tests and spec-driven development; UI agents will follow, with humans approving steps like checkout for now.

Where it goes. With a cognitive-scientist colleague, Barth works on agents that learn like humans, ask for help and become more independent. She expects every interaction to become an agent call, including between companies, and declines to pick between small and large models: edge AI will use small ones, many tasks large reasoning ones.

  • Agents must be near-certain to be worth deploying. Barth, a member of technical staff and developer relations lead at Amazon AGI Labs, says customers report demo agents working maybe 60% of the time, and "an agent that is reliable 60% is 0% useful". Nova Act, generally available since AWS re:Invent in December, targets 90% or more; she says it exceeds 90% on early enterprise customer workflows, evaluated on those customers' own tasks rather than just public benchmarks such as WorkArena and REAL Bench.
  • Reinforcement learning in "web gyms" teaches actions that generalise. Imitation learning suits next-token chat models, she argues, but agents must predict the next action, so Nova Act self-plays thousands of tasks across hundreds of replica UIs, with variations as small as light versus dark mode. To stop agents learning shortcuts, success is judged on a verifiable end state, such as the meeting actually appearing in the calendar or a database entry existing, while the path is left free.
  • Training model and actuator together avoids "Frankenstein" agents. Barth contrasts stitching a model, orchestrator and browser actuator with Amazon's approach of training "the brain and the body in one", while noting AWS also offers the Strands Agents SDK for teams that want to build their own. Runs execute in the customer's AWS account with step-by-step reasoning traces, next-action predictions, scheduled parallel runs and CloudWatch logs; for passwords the agent hands control back so the secret is entered locally and never sent over the network, an area she says 1Password built on, and CAPTCHAs are handed back the same way.
  • "Normcore" agents automate the boring work, starting with QA. PGA Tour checks its site before tournaments, Hertz raised shipping velocity 5x by automating rental-workflow tests, and Amazon Leo generates test cases from wireframes, by her account; the host cites her count of over a thousand generative AI applications at Amazon. She expects QA engineers to stop maintaining brittle Selenium-style or RPA scripts and shift to natural-language tests and reviewing traces.
  • Agency should expand as verification builds trust. Barth's coding moved from tab completion to line-by-line review to supervising agents in 2026, made safe by unit tests and spec-driven development, and she expects UI automation to follow, with humans approving steps like checkout for now. Her forecast is agents as digital co-workers that learn from interaction like humans, with every interaction an agent call and a mix of small edge models and large reasoning models.
Y CombinatorCursor for Product Managers
  • AI coding tools solve building software, not deciding what to build. YC argues Cursor and Claude Code are good once it's clear what needs building, but the harder, more important work — talking to users, understanding markets, synthesizing feedback — still lacks an AI-native system covering the full product-discovery loop.
  • The pitch is a tool that turns customer data directly into a proposed feature. Upload customer interviews and usage data, ask what to build next, and get back a feature outline with a rationale grounded in that feedback, plus proposed changes to the UI, data model, and workflows.
  • The tool would also hand off directly to coding agents. It would break the proposed changes into development tasks sized for a coding agent to implement, reflecting YC's view that as agents take the first pass at implementation, how teams define and communicate what to build needs to change.
Scott HanselmanYou don't know what you need to look up
  • Looking things up fails when you don't know what's missing. One speaker argues that in technical work it may never occur to you that a problem is essentially logarithmic, and that creative insight comes from noticing a coincidence, contradiction or connection, which requires both pieces already in your head. The other agrees you can't Google what you don't know to ask, and says AI will not solve that.
Dr. Jon KrohnHow Distributed AI Agents Will Transform Drug Discovery (with Vijoy Pandey)
  • Agentic drug discovery is a cross-vendor, multi-model pipeline. Answering the host's recap of his episode 941 vision, Pandey lays out the stages: an LLM iterates with the user to define the goal and break it into tasks, an AlphaFold-like scientific foundation model explores protein structures, compliance, effectiveness and manufacturability agents filter the candidates over many iterations to perhaps 10 options, and robotic labs run wet-lab experiments before any animal or human trials.
  • Passing messages is where the field is today; shared intent is missing. Pandey says AGNTCY, MCP and current work only connect the agents. They also need a common goal (a drug for a specific purpose, price point, population and risk profile) reached through semantic protocols for discovering information, resolving conflicts, negotiating and coordinating.
  • Shared knowledge and guardrails complete the stack. Agents must pool, add to, redact and modify knowledge of what has and has not worked; his example is a compliance agent drawing on the past to warn that a promising candidate would be stopped at FDA approval. Above that sit cognitive engines that both accelerate experiments and keep them within bounds, which he calls shared innovation.
Scott HanselmanAI and OpenClaw (née Clawdbot) and tools like Claude Code and GitHub Copilot for non-technical folks
  • Agents are next-token prediction plus context, tools and a loop. In this explainer for non-technical viewers, Hanselman says LLM calls are stateless, so context (a CLAUDE.md, Copilot instructions, your email) must be passed in each time; 25 years of marriage is why "let's go to the…" means the bagel shop for his wife. Tool calling lets the model read files and call code, and MCP servers are "USB for AI".
  • An agent that writes and runs its own tools is powerful and dangerous. Asked his blood sugar, it can search for the Nightscout API, ask for his URL and token, make the REST call and report "your blood sugar is 100". The building blocks are "effectively unlimited" because all open-source software is available, which is how people will "get pwned".
  • "By any means necessary" invites uncanny-valley behaviour, not consciousness. Asked to book a table at a restaurant with no API, he says an agent might download a text-to-speech model, clone your voice and phone via a service like Twilio. His own OpenClaw texted him repeatedly during a low blood sugar until he told it to chill; he calls these emergent behaviours that make it seem smarter than it is, and says this is not AGI.
  • Don't run these agents in YOLO mode with your accounts. He advises against giving them full access to email or bank accounts, and mocks a Twitter user handing a bot his account with instructions to "buy anything".
Technology and FriendsRachel Appel on Retro AI and How Algorithms from the Commodore 64 Era Still Apply [EPISODE 890]
  • AI is far older and broader than LLMs. Appel, a JetBrains developer advocate, objects to "AI" being used to mean an LLM, especially ChatGPT, and to the claim it came out of nowhere. Recommendation engines and car-factory robotics run on classic computer-science algorithms, and she argues that once people get used to an AI they stop calling it AI, which she expects will happen to LLMs too.
  • Pattern matching underlies all of it, LLMs included. She says transformer architectures still match patterns at bottom, so "fancy autocorrect" under-hypes LLMs while the marketing over-hypes them.
  • A Commodore 64 book already ran core AI algorithms. Her talk draws on AI Projects for the Commodore 64, published in 1985 for a machine with 64K of RAM and no hard drive; her husband retyped its samples into her GitHub repo, which runs in an emulator, and similar books are on archive.org. Its programs include Towers of Hanoi (recursion, state representation), the Knight's Tour via Warnsdorff's rule or backtracking (which she says could guide a Roomba), tic-tac-toe that reapplies winning moves as basic reinforcement learning, an Eliza-style chatbot, and a logic program that infers a cat is not a chihuahua.
  • The book already warned against treating chatbots as people. She quotes it saying people took Eliza seriously and shared personal feelings with it, and telling readers to beware that attitude. She ties this to humans anthropomorphizing machines, and says an LLM reflects us back by applying patterns to our own internet data.
  • What is new is data and compute, which deserve thrift. Appel, and Giard with her, credit cheap compute and storage for today's LLMs, while she notes data centers draining water and power grids in some communities. She points to DeepSeek as working within limited resources and argues for revisiting classic algorithms and the C64-era habit of counting bits, rather than throwing hardware at problems, to make AI cheaper.
Dr. Jon KrohnHow AI Agents Share Meaning Across Models, Vendors, and Languages (with Vijoy Pandey)
  • Natural language stays the common denominator while humans remain involved. Pandey expects all future work to happen in "multi-agent human societies" with agents and humans on the same level rather than in hierarchies. Agents can work at machine speed through API calls in ways humans cannot, but with humans in the mix "for a long long long time", agents must communicate in natural language.
  • Even with no human in the loop, language persists because vendors differ. Under his definition of superintelligence, agents doing discovery or economically viable work 100% of the time without human intervention, components still come from different vendors and frameworks, so language remains the shared medium.
  • Vector-space communication is more efficient but needs universal agreement. Pandey says converting vectors into tokens and language loses a great deal of information, so if everything were standardised and everyone agreed, vector space would be the way to communicate; he does not expect that in practice. His caveat is world models: citing recent work from FAIR and elsewhere, he says tokenization is a big detriment there and vector space the only way, a problem to be solved eventually, though for now his distributed-superintelligence work targets tokens and language.
Dr. Jon KrohnWhy Shared Intent Is the Missing Layer in Multi-Agent AI Systems (with Vijoy Pandey)
  • Shared intent is a common goal that balances individual objectives. Pandey's analogy is a prehistoric group taking a hilltop village, where warriors, medics, a leader and a treasurer each optimize for their own thing, and the shared intent is capturing it within budget, with fewest casualties, in the shortest time. His concrete case pairs an Outshift network-configuration agent, built to make the best-performing network, with another agent minding compliance, security, budget and on-time delivery; neither can solve the joint problem alone without trade-offs toward the common goal.
  • Today's agent world is full of connectivity but devoid of meaning. Pandey compares agents linked by gateways or MCP to an iPhone and an Android phone exchanging texts when one user writes Japanese and the other English: they connect but cannot collaborate. Each agent also carries its builder's worldview, so the Outshift agent reflects its own cloud stack, models, mostly US regulation and Cisco's design patterns.
  • A semantic layer of protocols is how Outshift wants to enable shared intent. Pandey lists what must happen above message passing: grounding on common terminology and objectives, discovery of missing information, resolution of conflicting information, coordination and the negotiation that comes with it, and evaluation of the goals. He says none of these can happen at the message-passing layer alone.
Y CombinatorHow We Redesigned Our Website
  • The old YC homepage read as generic and underplayed its own founders. YC's designer says the previous site felt like "a B2B SaaS template" with vague, unquantified claims ("we improve the success rate of our startups" without a number) and showed portfolio company logos without crediting the founders who built them — a gap the redesign set out to fix.
  • The redesign leans on storytelling rather than a sales pitch, drawing directly on Paul Graham's essays. The team studied PG's writing and pulled the word "formidable," which he and Jessica Livingston used for extraordinary early founders, into the new hero section, complete with a PG-style footnote defining it.
  • Founders, not YC, are put front and center. The new site shows before/after images of funded founders, side-by-side quotes stitched together from interviews with recent-batch founders about their YC experience, and photos of YC partners from when they themselves went through a batch — reinforcing that partners are ex-founders. The team deliberately kept most of the original circa-15-year-old PG homepage copy verbatim, updating only details like funding cadence and the San Francisco location.
  • The site was built by prompting Opus 4.5 in Cursor rather than designing static frames in Figma. The designer says this let the team prototype interactive sections live and iterate toward outcomes — like a scrolling before/after carousel — they don't think they'd have arrived at in a static tool, freeing their time to focus on storytelling and interaction design instead of manual implementation.
Technology and FriendsTim Rayburn on How AI Resets the Agile Manifesto [EPISODE 889]
  • Tools no longer slow down interactions, so that trade-off weakens. Rayburn, a vice president of consulting at Improving who helps lead its AI practice, says the manifesto discounted tools because heavyweight processes of the time slowed shipping, while tools like Claude Code now work at the level of conversation; he still warns against outsourcing human judgment.
  • Comprehensive documentation is now the route to working software. He argues a full description of intended behaviour is "a few short steps away" from executable code, and that with users getting software in hours or days, the theory-of-constraints bottleneck may move from development to product owners knowing what they want. He wants agents given access to Jira or Azure DevOps so they can read context and kick unclear work back to a human.
  • AI adoption will push consulting from billable hours to value pricing. Rayburn calls this his most heretical view: "customer collaboration over contract negotiation" assumed vendors had equal capabilities, but a long-trusted vendor that does not adopt AI may become the slowest option. He predicts value-based pricing, and says that if he is wrong the alternative is higher hourly rates to cover the overhead between ever-shorter projects; Giard notes the old difficulty of defining value.
  • Cheap planning brings the good plan back. Rayburn says responding to change is now table stakes: because documents can be regenerated quickly, he says teams can plan and respond to change both, and predicts shorter iterations and more kanban-style boards, possibly ending rigid sprints. He proposes new pairs of values: human judgment over AI capability, and clarity of intent over implementation speed — he would rather wait a week for the product owner's intent to be clear.
  • Improving trains every developer to hand agents business-level tasks. He describes a five-point AI maturity scale: office workers stop at chatting, most developers plateau at giving agents scoped technical tasks, and Improving's minimum target is handing an agent a full user story to break down itself, which needs far more words per story than the old "post-it note" habit. He urges viewers to try spec frameworks such as OpenSpec and Spec Kit or heavier agile-style agent frameworks, which he says are yielding fast, high-quality output on Improving's teams.
Dr. Jon Krohn962: Wharton Prof Ethan Mollick on Why Your AI Strategy Is Already Obsolete
  • Working with AI now spans four modes, not one. Mollick says that when he wrote Co-Intelligence AI was error-prone and not autonomous; now people pick among doing work alone, working interactively with a chatbot, assigning a task to a thinking or agentic model and evaluating the result, and letting AI act autonomously on some tasks.
  • Companies must experiment with management themselves rather than outsource it. Asked how to restructure teams in light of his Procter & Gamble field experiment with 776 professionals (the host's description), Mollick says "we have no answers" yet, and points out that better management, and a willingness to experiment with it, gave American firms 20 to 40% of their extra competitive value in the 20th century. He warns that a talk-to-our-documents RAG chatbot or a consultant-built app from a year and a half ago is now easily beaten by an off-the-shelf model, though he grants consultants and RAG have a place.
  • Adoption needs leadership, a lab and the crowd working together. In Mollick's framework, leadership sets incentives, vision and process changes; the crowd is everyone using advanced chatbots to find use cases in their own expertise; and the lab is the couple percent of staff who are very good at AI, not mostly IT, who refine and ship what works, benchmark, and decide buy versus build. He argues hidden "secret cyborgs" will stay hidden unless leadership makes disclosure safe and rewarding: someone working 90% less will not give that up for free if they fear firings.
  • Buyers should demand far more transparency from AI vendors. Mollick adds renting to buy-versus-build and says vendors generally use someone else's models, so buyers should ask which models and which prompts, since unaudited prompts can make results seem good when they are not. "If your secret sauce is we are using a prompt and we are using Gemini," he says, that is not a competitive advantage.
  • Self-reported AI gains are large, but processes have not caught up. Mollick cites over 50% of Americans saying they use AI at work, self-reporting a three-times performance improvement on a fifth of the tasks they use it for, while calling the figure hard to verify. He says things like agile stand-ups and sprint planning have no answer for someone who finishes all their code at once, and his advice is to use one big player's frontier models heavily for real work, betting they will get better and cheaper.
Y CombinatorWhy Your Startup Website Isn't Converting
synopsis

Reviewing five founder-submitted websites on this Design Review episode, Framer co-founder Jorn van Dijk keeps returning to one throughline: clarity about what the product actually does beats polish, and small unresolved details erode trust in everything else on the page.

Lumari, an AI procurement platform. Van Dijk says the heavy animation and vague icon graphics never anchor what the product looks like, and that its two "book a demo" CTAs ask for too much commitment before a first-time visitor understands the value; he recommends screenshots or a short walkthrough video instead.

"A lie," an AI presentation tool. He credits it with showing glimpses of the real interface rather than pure illustration, but flags that its highlighted customer quotes are too generic to back up a "high quality" claim, and that forcing signup before letting someone generate a presentation is a mistake given it's competing directly against a free incumbent, Google Slides.

Juicebox, an AI recruiting platform. Van Dijk likes its distinct visual identity and recognizable customer logos, but says its brutalist black-and-white style with a "win the talent war" tagline feels emotionally disconnected from being a product about finding people, and that its interactive demo hits a signup wall before delivering a payoff.

Leaping AI, a voice-AI call center replacement. He praises its live phone-call demo as genuinely persuasive, but notes the hero imagery of a single phone with one caller reads as consumer-facing even though the copy explicitly targets large enterprise call centers — a mismatch he says undercuts the positioning.

The Hog, a GTM automation tool. This gets the sharpest critique: unclear naming (an unexplained acronym), inconsistent spacing and typography, and testimonials with fully capitalized sentences and no attached company name, which together read as fabricated and cast doubt on the product's other claims. Van Dijk's closing advice, given the page's sprawl, is to strip it down to only what explains the product, test that stripped version on twenty people unfamiliar with it, and expand from there once comprehension is confirmed.

  • Generic illustrations of a product are a recurring failure across the sites reviewed, and screenshots or a short video would fix most of them. Framer co-founder Jorn van Dijk repeatedly tells founders (Lumari, the presentation tool "a lie") that vague icon animations don't tell a first-time visitor what the product does or looks like, and that a real screenshot or two-minute walkthrough would do more to earn trust than an abstract hero animation.
  • Asking for a demo or signup before showing any value creates unnecessary friction. Van Dijk argues a "book a demo" button is a big ask before a visitor understands what they're buying, and for the presentation tool competing directly with free Google Slides, he says letting people try the product immediately — even a prompt box on the homepage — matters more than gating access behind a signup wall.
  • Visual style needs to match what a site claims to be, or it undercuts the message. Van Dijk flags that Juicebox's black-and-white, "win the talent war" aesthetic feels disconnected from being a people-focused hiring product, and that Leaping AI's single-phone, consumer-style hero visual works against its stated positioning as an enterprise call-center replacement.
  • Small inconsistencies compound into distrust of a site's bigger claims. Reviewing The Hog, Van Dijk points to uneven letter spacing, a fully capitalized customer quote with no named company attached, and a shared toggle widget that behaves two different ways on the same page, arguing that a visitor who notices these details starts to doubt the numbers and testimonials elsewhere on the page too.
Dr. Jon KrohnDistributed Superintelligence Explained Through Human Evolution (with Vijoy Pandey)
  • Human intelligence leapt when it began scaling horizontally. Pandey says that for the first 300,000 to 400,000 years humans grew smarter only vertically, with inventions confined to an individual's or a process's lifetime. A cognitive revolution around 70,000 years ago brought language that could carry meaning across tribes and generations, and with it three things: shared intent and coordination, shared knowledge ("standing on the shoulders of giants"), and shared innovation.
  • AI has built bigger individual geniuses but lacks collective infrastructure. Pandey's thesis is that work on AI and superintelligence has so far scaled vertically, and the framework for distributed intelligence is missing. Distributed artificial superintelligence (DASI) is his effort to build one that enables shared intent, knowledge and innovation in a society of agents and humans.
Crosstalk SolutionsDual 25-Gig Networking in a Mini PC?! MS-02 Ultra First Look
  • The Minisforum MS-02 Ultra's standout feature is its networking. It has dual 25 Gbps SFP28 ports plus 10 Gbps and 2.5 Gbps RJ45 Ethernet, built-in Wi-Fi 7, USB4 v2 and an internal 350 W power supply, so no external brick. The host, unboxing his own unit after first seeing it at CES, pitches it as a home-lab server or compact workstation.
  • It is twice as thick as the MS-01 to fit a GPU. Inside is a PCIe 5.0 x16 slot that takes a dual-slot low-profile card, such as the Gigabyte RTX 5060 OC low-profile, with an 8-pin power connector on the board. It measures about 9 x 9 x 4 in, and the shell comes off with two thumbscrews.
  • The top configuration is a 24-core Intel Core Ultra 9 285HX. It also has an NPU for AI workloads. RAM goes up to 256 GB across four SO-DIMM slots, with ECC on the 285HX model, and four M.2 slots allow up to 16 TB with RAID. The 285HX base model starts around $1,160 barebones, or just under $1,600 with 32 GB RAM and a 1 TB NVMe.
Technology and FriendsBrian McKeiver on Microsoft Foundry [EPISODE 888]
  • Foundry's renames track a widening scope, not just marketing. McKeiver, co-owner of the Grand Rapids Microsoft-stack agency BizStream (25 years in business, about 100 clients), traces it from Azure cognitive services to Azure Cognitive Search, Azure AI Search with semantic search, Azure AI Studio for about a year, and then Microsoft Foundry once agents arrived; Giard frames it as a unified AI platform absorbing separate products, and McKeiver agrees.
  • A Foundry project assembles a working agent in the browser without code. He describes picking from thousands of models with cost estimates, adding knowledge sources for RAG (Azure AI Search, blob storage, Fabric, Foundry IQ), MCP tools, memory, guardrails and content safety, and reaching a playground within minutes. He relays that Microsoft guarantees a private deployment's data does not leave the tenant.
  • An agent removed about 90% of a manufacturer's manual order entry. For a Michigan manufacturing client whose staff hand-keyed PDF purchase orders and invoices, BizStream combined an agent with Azure Document Intelligence and an API call into the internal system; staff now only verify the extracted data on screen.
  • Agents need your business vocabulary spelled out in system instructions. Connecting BizStream's third-party CRM through its new MCP server took "about four clicks", but the agent had to be told that "lost" maps to three or four CRM statuses (e.g. 3, 4 and 5). He says a Foundry build can be opened in C# or Python code for customization and published to Teams or Microsoft 365 Copilot, which Giard calls its selling point over low-code tools.
  • Expect to keep relearning the tooling. McKeiver warns Microsoft may add features at any time, around Build or Ignite, and hopes "Foundry" is a name that sticks for a while.
Dr. Jon KrohnWhy “Superintelligence” Needs a Clear Definition (with Vijoy Pandey)
  • Superintelligence can be pinned to an economic and a technical test. Pandey says the industry has drifted from AI to AGI to ASI to "powerful AI" as each term proved ill-defined, but the definitions from OpenAI, DeepMind, Yann LeCun and Demis Hassabis fall into two buckets. The economic one asks whether a system of autonomous agents can perform 100% of a human task without human intervention; the technical one asks whether an objective-driven reasoning engine can autonomously invent something beyond its training data that passes the rigor test.
  • Pandey's group aims to meet both tests by scaling out. He notes some argue a level of superintelligence is already here because the Turing test has been passed, but says AI is still super powerful in some use cases and pretty bad in others, so something is missing. His team's goal is to reach both definitions, economic and technical, through a scale-out mechanism.
Network ChuckI flew to Romania to find hackers who fight hackers
  • Bitdefender's "Draco" malware-analyst team spent two and a half years building free decryptors against one ransomware gang until it gave up. Chuck visited Bitdefender's Romania HQ and reports the team has saved ransomware victims over $1 billion in payments overall; each time the gang updated its malware, Draco released another free decryptor, and the gang eventually shut its operation down.
  • Chuck argues AI has erased the technical skill barrier that once limited scammers, and that even experts get fooled by AI-driven scams sometimes. He pivots from the Draco story to promoting Bitdefender's own "scam protection" tool, pitched as a firewall checking calls, messages and emails to protect family members less able to spot these scams.
Dr. Jon Krohn961: Distributed Artificial Superintelligence — with Dr. Vijoy Pandey
synopsis

Pandey, head of Outshift, Cisco's internal incubator, returns from episode 941 to argue that artificial superintelligence will be reached by connecting many agents and humans into flat "multi-agent human societies", not by building ever-larger single models. He sets out a three-layer framework for this, distributed artificial superintelligence: semantic protocols for shared intent, a cognitive memory fabric for shared knowledge, and cognitive engines for shared innovation. He sets it out in a new white paper and links it to Cisco's open-source work. Cisco is among the episode's listed sponsors.

Defining the target. Pandey sorts definitions from OpenAI, DeepMind, Yann LeCun and Demis Hassabis into two buckets. The economic one is a system of agents doing 100% of a human task with no human intervention. The technical one is an objective-driven reasoning engine inventing beyond its training data. Outshift aims for both through scale-out.

The evolutionary analogy. Humans scaled intelligence vertically for 300,000 to 400,000 years. Then a cognitive revolution around 70,000 years ago brought language, and with it shared intent, shared knowledge and shared innovation. Pandey recommends Yuval Noah Harari's Sapiens for the role of shared fiction in that. AI, he says, has only built bigger individual geniuses and now needs an "agentic cognitive evolution".

Shared intent. His running example is two agents building a network for Swisscom, one optimizing the network and one minding compliance, security, budget and schedule. Today they can pass messages but not share meaning. Semantic protocols are meant to handle grounding, discovery of missing information, resolution of conflicts, coordination, negotiation and evaluation. On the substrate, Pandey says natural language is the common denominator while humans are involved, and still is among agents from different vendors; vector space would win only under universal standardization. He concedes that world models suffer from tokenization, but says Outshift starts with language because heterogeneous brownfield enterprises are where Cisco plays.

Shared knowledge. A private conversation shares intent but adds nothing to collective knowledge. The cognitive memory fabric is meant to fix that: cognitive rather than raw data, persistent, and distributed, with sharing and privacy controls. It grew out of the Swisscom work, where agents alone were "a recipe for disaster" and deterministic code alone explored too little. Pairing agents with a network digital twin worked, and after three or four use cases the team is generalizing it across working memory, ontologies and knowledge graphs.

Shared innovation. Citing Raj Reddy's line, via Satya Nadella, that AI can be a guardian angel or a cognitive accelerator, Pandey describes two kinds of cognitive engine. Accelerators speed up tasks. Guardrails keep new designs, such as a never-built low-earth-orbit satellite network, within compliance and physical limits. In drug discovery, an LLM plans and an AlphaFold-like model explores. Compliance, effectiveness and manufacturability agents filter the results down to about 10 options for robotic wet labs. Every stage needs all three layers.

Outshift's position. Pandey frames Cisco as a networking, security and observability company that "empowers the pack" in both superintelligence and quantum networking. Message-level problems are being handled through AGNTCY, A2A and MCP, all Linux Foundation projects where Outshift is a member or launch partner. That includes the Agentic AI Foundation, which he corrects to having formed in December. He insists the bigger unsolved problems are semantic.

  • Superintelligence will come from collectives of agents, not lone geniuses. Pandey defines ASI by two tests, economic (agents performing 100% of a human task without intervention) and technical (inventing beyond training data), and wants to reach both by scaling out. His analogy is human evolution: 300,000 to 400,000 years of vertical gains, then a cognitive revolution around 70,000 years ago when language brought shared intent, shared knowledge and shared innovation. He casts Cisco's role as "empowering the pack" while others build "lone wolves", the same stance it takes when networking quantum computers together.
  • Semantic protocols let agents share intent, not just exchange messages. Pandey says agents connected through gateways, MCP or A2A are like an iPhone and an Android exchanging texts in Japanese and English: connectivity "devoid of meaning". In his running example, an Outshift network-configuration agent and a compliance, security and budget agent building a network for Swisscom must trade off toward a common goal, using protocols for grounding, discovery, resolution of conflicting information, coordination, negotiation and evaluation.
  • Natural language stays the agents' common denominator for now. Pandey argues that while humans are in the loop, and even without them because components come from different vendors, language is the lowest common denominator. Only if everyone standardized would vector space be the way to communicate. He flags that world models suffer from tokenization, citing recent work from FAIR and others, but says Outshift starts with language, broadly including mathematics and physics, because Cisco's business is gluing heterogeneous brownfield systems.
  • A cognitive memory fabric pairs probabilistic agents with formal world models. Pandey says the idea came from Outshift's Swisscom work, where letting agents loose on a network was "a recipe for disaster" and deterministic software alone explored too little, so agents were layered on a network digital twin. After three or four such use cases the team is generalizing it into a persistent, distributed layer of working memory, knowledge, ontologies and knowledge graphs that agents can summarize, extend and redact, under strict privacy and access controls.
  • Cognitive engines drive shared innovation as accelerators and guardrails. Pandey borrows a Raj Reddy quote, recently repeated by Satya Nadella, that AI can be a guardian angel or a cognitive accelerator. Accelerators speed parts of a workflow; guardrails keep invention within compliance and physical limits (encoding what a wall or a blueberry feels like). His drug-discovery pipeline runs LLM planning, an AlphaFold-like model, compliance and manufacturability agents and robotic wet labs on all three layers, with the compliance agent drawing on past FDA outcomes.
Scott HanselmanDon't outsource the problem solving
  • Hand AI the syntax, never the problem solving. One speaker, explaining why "this book" is worth writing in the era of AI and vibe coding, says outsourcing the translation into syntax is fine, but the clarity of thought that turns a real business problem into a solution and then into working code "is the whole game". The clip matches word for word Eric Lippert's answer in the Hanselminutes interview about his book Fabulous Adventures in Data Structures and Algorithms.
Crosstalk SolutionsLoRaWAN is BLOWING UP at CES 2026!
  • LoRaWAN had a bigger presence at CES 2026 than the host had ever seen. He walks walls of LoRaWAN sensors covering occupancy, leak, flood and CO2 detection, smart radiator thermostats, dry switches, valves, microclimate controllers, and personnel tags working over GPS or BLE, plus a wristband wearable for tracking employees.
  • Sensor readings can be shown on PoE- or battery-powered e-ink displays. The demo showed environmental monitoring and patient vital signs, with up to a year per battery charge claimed. One vendor also showed an all-in-one off-grid solar Meshtastic kit, with panel, battery box, radio compartment and a top-mounted antenna.
Dr. Jon KrohnWhen Extra Reasoning Makes AI Worse (and Pricier)
  • More reasoning does not reliably make a model better at a task. In chapter 7 of his book, Ozdemir benchmarks reasoning models on MathQA and Humanity's Last Exam and finds no obvious correlation between reasoning level and performance, a result he calls consistent. He says labs such as Anthropic report the benchmarks where reasoning helps, and that running the ones they don't report shows the opposite.
  • Even where reasoning helps, the gain rarely justifies the cost. Ozdemir says that in other benchmarks showing a correlation, the gain is maybe 1 or 2% in accuracy for a 2x increase in cost, and in his consulting it almost never pays. He recommends few-shot prompting and building your own shorter, more succinct reasoning traces instead; the host notes the book's reasoning benchmark took 5 hours for 180 LLM calls.
  • Reasoning is ordinary next-token generation hidden from the user. Ozdemir says OpenAI, Anthropic and Gemini models are trained to produce reasoning, but it is the same autoregressive stream, which the UI hides until the model is "done thinking". Prompting "think through the problem before answering" induces something similar. His anecdote: one unnamed model produced three paragraphs of reasoning and a 30-second wait just to reply "hello".
Technology and FriendsSam Basu on Developer Productivity with Contextual AI [EPISODE 887]
  • Some development tasks are no longer worth doing first by hand. Basu, a developer advocate at Uno Platform (an open-source stack for running one .NET codebase on mobile, desktop and the web via WebAssembly), says AI is quicker and better at them, while humans keep a hand in the loop and own the architecture.
  • Agents ground themselves by delegating to tools over MCP. He describes agents as orchestrators over models such as GPT-5, Sonnet, Opus and Gemini, and MCP — started by Anthropic and now joined by Microsoft and Google — as the API layer letting them hand tasks to tools and check current docs before answering, his remedy for hallucination.
  • Uno's app MCP gives coding agents "eyes and hands" to verify work. Besides a docs-and-project-setup MCP server, Uno runs a local server alongside the app being built that exposes seven or eight tools: screenshots, clicking buttons, typing text and reading the visual tree. An agent that builds a login screen can then check its own result instead of guessing.
  • Instructions files set standards; skills give agents step-by-step recipes. He says recurring mistakes belong in an instructions file the agent always reads (naming, how to make HTTP calls), while a skill is a "recipe card" for a task, such as checking the docs and the API response, building a data model and then mapping a UI to it.
  • Treat agents as peer programmers that work while you sleep. With guardrails, agent-run unit and UI tests, and a human reviewing the pull request, Basu says you get "almost a clone of yourself", at a cost in tokens and money.
Dr. Jon KrohnWhy Accuracy Alone Is a Terrible Way to Evaluate AI (with Sinan Ozdemir)
  • Evaluation depends on the task, not the model. Ozdemir splits LLM tasks into generative (free text and multiple choice) and understanding (embeddings and classification), each with its own metrics, since grading an essay differs from grading embeddings even when LLMs produce both. The classification metrics in his Principles of Data Science from 10 years ago, he says, still apply when an agent is doing the classifying.
  • Pick precision or recall by which error costs you more. Ozdemir defines precision as how often the model is right when it says yes, which matters when false positives are expensive, and recall as how many true yeses it catches, which matters when false negatives are. In his factory example, passing a bad part that might bring a plane down makes precision what counts, while throwing away a good part by accident is tolerable.
Dr. Jon KrohnThe Hidden Limits of Massive Context Windows (with Sinan Ozdemir)
  • Long-running agents need context the model can actually reason over. Ozdemir explains that every turn and tool call adds tokens, so long-horizon tasks need long context windows. In his book's needle-in-a-haystack test, he filled a context window with trivia and inserted his own birthday, and depending on its position and how full the window was, the LLM failed to see it. Window size alone, he argues, does not tell you whether a model can use everything in it consistently.
Scott HanselmanPro Tip for managing 10 Coding Agents in the Windows Terminal
  • Rename and colour terminal tabs to keep many agents apart. Hanselman runs several GitHub Copilot CLI sessions (using Claude Opus) as Windows Terminal tabs, in PowerShell or WSL; right-clicking a tab lets him recolour and rename it, so they stop all reading "PowerShell" or "WSL".
  • The tab bell shows which agent is waiting on you. When Copilot CLI needs input, such as approving a tool, it rings the bell and the tab shows a bell icon, so he can work elsewhere and come back when he hears it. Tabs can also be torn out into their own windows while the work carries on in the background.
Scott HanselmanSomeone had to write that code
  • Every abstraction you lean on was written by someone. One speaker recalls interviewing a database developer at Microsoft who would generate a unique integer by marking a column as a unique identifier; asked what he would do if the database lacked that feature, he said he had never considered that somebody had to write that code. The speaker's answer: "you can be that guy". The clip matches Eric Lippert's story in the Hanselminutes interview about his data structures book.
Y CombinatorBuilding The World's First Reusable Rockets
  • They set out to build a fast-turnaround, fully reusable orbital rocket. The founders say the industry norm is to build and launch a rocket once, lose it in the ocean, and never see it again; they wanted a vehicle that reaches orbit, flies back, and repeats the cycle "again and again," a problem they felt nobody else was attacking with rigor.
  • Launching the company felt like an irresponsible, highest-stakes bet. One of the two co-founders calls starting from zero, with no one else in the field beside them, the hardest personal decision they've made, reached only once they concluded the idea "had to be tried" regardless of whether it succeeded.
Scott HanselmanGitHub Coplot CLI+WorkIQ+Nightscout...can I correlate which coworker is stressing me out? Satya?
  • Let the LLM handle ambiguity, and fetch the facts with code. Hanselman, a type 1 diabetic, asks GitHub Copilot CLI whether 90 days of his work meetings correlate with 90 days of his blood sugar. He calls an LLM "an ambiguity loop": good at the open-ended question, but his calendar and glucose must not be hallucinated, so glucose comes from a database through a Python skill he wrote and meetings, Teams and email through Work IQ.
  • He steers the agent mid-run rather than waiting for the answer. While it works he adds context, such as checking who attends the meetings; he calls this steering.
  • The agent's verdict: Monday afternoons, not Satya meetings. As he reads it out, the agent found Satya meetings on Thursdays at 1:00 and Thursday the worst glucose weekday, but concluded those meetings were not spiking him; it flagged XLT and pre-Satya prep meetings on Thursday mornings, rated Tuesdays with James best and Amanda neutral, and put the problem at Mondays at 4:00, possibly from skipping lunch, which he says is what he does. He says he did not know the answers beforehand and "could go either way"; he works on Copilot CLI, and jokes that it is the fun of that work that shows.
Crosstalk SolutionsSwapping Out a Failing UniFi Gateway
  • The host's UCG-Fiber failed in software while still passing traffic. Starting in November 2025 it dropped off the UniFi cloud site manager (unifi.ui.com), and firmware updates, power cycles and toggling cloud access did not fix it. Later the local interface slowed, froze, and restarted UniFi Network on its own. He does not think heat was the cause.
  • He links the failure to an early-release review unit. Ubiquiti sent him the original free for review, and it died less than a year in, which he thinks the early-release build may explain. He bought the replacement himself for just over $300 with shipping, choosing the model with no onboard storage because a separate UNVR handles Protect.
  • A backup taken from the failing gateway restored nothing useful. It reported success after about 5 minutes but left the default 192.168.1.0/24 network instead of his 192.168.200.0/24, with no networks, Wi-Fi or adopted devices. It also showed an impossible backup date of March 6, 2121.
  • The older cloud backup from November 11, 2025 restored correctly. That brought back the right subnet, the WAN IP and all his UniFi devices. The cost is that any changes he made since November must be remembered and re-applied. He then updated UniFi OS and UniFi Network before moving the gateway into the rack.
  • A new gateway brings a new MAC address, which may need an ISP modem reboot. Where the WAN uses DHCP, the ISP's lease can be tied to the old MAC. He did not need to reboot his Comcast modem, probably because he has a static IP. He says a like-for-like swap is easy, but moving to a different gateway, such as a rack-mount model, may need extra steps.
Dr. Jon Krohn960: In Case You Missed It in December 2025
synopsis

The host's December compilation strings six clips from recent episodes into one argument: AI pays off when it is aimed at measurable outcomes and fitted to how people actually work, and fails when it is adopted for its own sake.

Measurable ROI. Dell's John Roese (episode 953) says Dell's revenue grew $10 billion while absolute cost fell 4% in the fiscal year reported in March, a decoupling he says Dell had not seen in 41 years. He credits picking projects with hard metrics, and cites a consulting report, he thinks McKinsey's, calling generative AI a "BS work detector". The host sets this against MIT NANDA's contentious 95% enterprise-AI failure figure.

AI as coach. Joel Beasley (episode 945) has Gemini measure his stand-up sets against a professional standard of four to five laughs per minute. At recording it was the only browser chatbot that took video. He tracks every set in a spreadsheet, and he built a writing-coach prompt by modeling the feedback at about 10 comedy writers' groups.

Avoiding burnout. A data scientist (episode 952) describes leaving finance in New York for life-sciences data science and hiring a fitness coach after overtraining. Her routine is four gym sessions a week, one gram of protein per pound of body weight, carbs timed around workouts, and at least eight hours of sleep, helped by short phone-free walks.

Getting hired. A Netflix senior data scientist (episode 947) describes a "briefcase" document of a company's pain points and his fixes, which got him into DoorDash. The host doubts it would stand out among today's AI-generated pitches. The guest says Netflix hired him, after earlier rejections, for his rare mix of ads and forecasting from Spotify.

Human context. Sandy Pentland (episode 949) warns that AI systems ignoring human nature could fail as the Soviet Union's did. He argues people are social foragers who take most behavior from culture, that loud voices drive polarization, and that traders who watch other traders do better and weathered 2008.

Workslop. Dropbox's VP of Engineering (episode 951) blames workslop on pressure to adopt AI without clear goals. His fixes are human revision of first drafts, hybrid BM25-plus-vector retrieval for context, internal benchmarks, and training led by high performers.

  • Aim AI at hard ROI metrics, and it exposes worthless work. Dell's global CTO John Roese (episode 953) says that in the fiscal year Dell reported in March, revenue grew $10 billion while absolute cost fell 4%, which he says had not happened in Dell's 41 years. He credits people, process and technology. He cites a consulting report, he thinks McKinsey's, that calls generative AI a "BS work detector": if AI is applied to a task and revenue and cost do not move, the work may not be worth doing. The host frames this against MIT NANDA's 95% failure figure for enterprise AI, which he calls contentious.
  • Laughs per minute gives comedy a measurable target. Software engineer and podcast host Joel Beasley (episode 945) says four to five laughs per minute is the standard for a full-time professional comedian. He records every set, about 10 to 11 months into stand-up, and has Gemini count laughs, since at recording it was the only browser chatbot that took video and GPT and Grok did not. He logs results in a spreadsheet, and he also uses a saved writing-coach prompt modeled on how professionals gave feedback at about 10 comedy writers' groups.
  • A niche intersection of skills beats application tactics. A Netflix senior data scientist (episode 947) says he got into DoorDash with a "briefcase" document, which took at least a couple of days, setting out the company's pain points and how he would solve them, sent to the hiring manager. The host doubts it would stand out now that he gets 30-page AI-made pitches weekly. The guest says he landed Netflix, after multiple earlier rejections, because his ads and forecasting experience at Spotify matched what Netflix needed when it launched ads.
  • Systems that ignore how humans decide will break on edge cases. Sandy Pentland (episode 949) argues today's AI-driven systems could fall apart the way the Soviet Union's did, through bad data, fast change and ignoring human nature. He says people are "social foragers" and cites Daniel Kahneman's estimate that 95% of what we do comes from culture. He says his group has shown polarization comes from a few loud voices, that traders handling $10 million a day do reliably better when they watch other traders, and that equation-followers who missed tail risk "got creamed" in 2008.
  • Workslop comes from vague AI mandates and poor work context. Dropbox's VP of Engineering (episode 951) cites almost three-quarters of CEOs feeling competitive pressure to adopt AI and about 55% of employees not knowing how to use it. His remedies are to treat AI output as a first draft, and to build better context than slow, token-hungry MCP connectors provide; Dropbox's Dash pairs a BM25 lexical index with a vector index. He also recommends internal eval sets defining what good looks like, and training led by high performers.
Scott HanselmanWhat we actually call AI
  • "AI" is branding over statistics; the intelligence is human. One speaker relays a joke of unknown origin: the public is told it is artificial intelligence, investors machine learning, developers stochastic programming, and it is actually linear interpolation. The two voices then agree the intelligent part is the people behind it, including the underpaid workers "running the mechanical turks" that train the systems. The clip matches a passage of Hanselman's interview with Eric Lippert, where Lippert tells the joke.
Scott HanselmanFabulous Adventures in Data Structures and Algorithms with Eric Lippert
synopsis

Eric Lippert, a language designer formerly at Microsoft and Meta, ends up arguing that AI-assisted coding makes deep knowledge of algorithms more relevant, not less: tools can take the syntax, but the problem solving is the job, and curiosity about how things actually work is what the new book is for. Fabulous Adventures in Data Structures and Algorithms was in Manning early access at 7 of 19 chapters when recorded.

Why a book now. An editor's question after another book project led to a proposal of "all the weird stuff you don't learn in school". Lippert still prefers long-form reading for really learning a topic, and says don't outsource the problem solving.

Who it is for. Hanselman notes there is no board certification for programmers and asks whether the book suits someone building text boxes over data with React. Lippert says it is for curious coders: it starts hard, and covers twisted takes on classic structures, developer-tools algorithms such as unification, and stochastic programming, plus a coming chapter on how code formatters work.

Stochastic programming and bots. Lippert retells a joke about AI being linear interpolation, then explains Bayesian updating with 1,000 coins, one double-headed: ten heads (1 in 1,024) moves belief to about 50/50. At Facebook that machinery judged whether new accounts, 999 in 1,000 of them bots by this rough figure, were real. Asked why spam still floods Instagram, Lippert cites a hard problem, the layoff of the entire division, ever more sophisticated attackers, and owners who no longer care about protecting users.

Recreation that teaches. Gosper's Game of Life algorithm, faster on bigger boards, is in the book because it changed how Lippert thinks about functional programming. Both agree some algorithms feel discovered rather than invented, and Lippert says revisiting old blog posts shows "past Eric" understood less than he thought.

  • Outsource the syntax to AI, never the problem solving. Lippert, asked why write a data structures book at "the peak of AI-assisted coding", says turning a real business problem into a clear solution and then into working code is "the whole game"; the syntax step can go to any tool. The book, Fabulous Adventures in Data Structures and Algorithms, was in Manning early access with 7 of 19 chapters out (chapter 7, on category theory, released the day of recording).
  • The book is the unusual material school skips, for curious coders. It is not a tutorial and does not start with Hello World: part one gives traditional structures (lists, queues, stacks, combinatorics, trees, memoized immutable quad trees) a twist, part two covers developer-tools algorithms like unification and anti-unification, and part three stochastic programming from Lippert's Facebook work. A coming chapter explains how code formatters decide what is "pretty".
  • Stochastic programming is principled Bayesian updating at scale. Lippert's example: from a bag of 1,000 coins with one double-headed, ten heads in a row (odds 1 in 1,024) moves you to roughly a 50/50 belief. At Facebook they built language tools for data scientists to apply that updating across billions of observations: is this new account a real person when 999 in 1,000 are bots, is this the broken router, is this reviewer classifying spam correctly.
  • Bot spam persists because the platforms stopped fighting it. Pressed by Hanselman on Instagram crypto-group spam about 40 times a week, Lippert gives four reasons: the problem is hard, the research division getting good results was laid off entirely, attackers keep getting more sophisticated, and site owners "no longer particularly care about the user protection problem". Lippert adds the feed still shows radio-station content farms after more than a thousand blocks, because the models optimize for outcomes other than user enjoyment.
  • Some algorithms feel discovered rather than invented. Lippert includes Bill Gosper's Game of Life algorithm, which computes the future of boards too big for memory and gets faster as the board grows, purely because it changed how they think about functional programming. Hanselman ties this to Douglas Crockford saying he discovered JSON rather than invented it.
Y CombinatorThe ML Technique Every Founder Should Know
synopsis

Visiting YC partner Francois Chaubard, who has worked in computer vision since 2012 and ran Focal Systems for a decade before returning to Stanford to finish a PhD on diffusion-based world models, argues diffusion is not just an image-generation trick but a general framework for learning any data distribution — one he believes founders training their own models should treat as a default tool, regardless of domain.

What diffusion is. Chaubard defines it as learning to reverse a noising process: take real data, progressively corrupt it with noise, then train a model to walk backward from noise to data. Its distinguishing strength is mapping low amounts of training data onto very high-dimensional outputs — he demonstrates learning a face distribution from only 30 sample images.

The objective got simpler, not more complex. Tracing the line from the original 2015 paper onward, he shows researchers found each successive prediction target easier to learn — first the data itself, then the added error, then a "velocity" — steadily cutting the Fréchet Inception Distance quality score from roughly 222 to about 8-10 today, while the code needed actually shrank, unusually for machine learning.

Flow matching as the current endpoint. He credits Meta's Yaron Lipman with reducing diffusion training to a straight-line velocity between noise and data, implementable in roughly five lines of code that transfer unchanged across images, proteins, DNA, or robot trajectories — the modeling architecture underneath is a separate, swappable choice.

Where it's deployed, and its limits. He cites DeepMind's Nobel-winning protein folding, diffusion robotics policies, and weather forecasting as proof points, noting diffusion has displaced most of AI except autoregressive language models and game-playing search. Its main limit: a model trained on a fixed number of denoising steps can't simply run more steps at inference for better quality.

  • Diffusion is a general-purpose way to learn any data distribution by training a model to reverse noise, and it now spans far more than images. Visiting partner Francois Chaubard cites DeepMind's Nobel Prize-winning protein-folding work, the "diffusion policy" approach used for robotics and self-driving, and Google's GenCast, which he calls the most accurate weather forecasting system in the world, as the same core mechanism applied to different domains.
  • Progress came from making the training objective easier to learn, not from a new core idea. Chaubard traces a line of papers that moved from predicting the noised data itself, to predicting the added error, to predicting a "velocity," each step making the math simpler and driving the Fréchet Inception Distance quality metric down from about 222 in the original 2015 paper to roughly 8-10 in modern models.
  • Flow matching, from Meta researcher Yaron Lipman, collapsed diffusion training into a straight line between noise and data. Chaubard demonstrates it as roughly five lines of training-loop code that work unmodified whether the underlying model is generating images, proteins, DNA, or robot trajectories, calling it one of the more profound simplifications in recent machine learning.
  • Chaubard's advice splits by role: model-trainers should treat diffusion as a default tool, and everyone else should update on how fast it's improving. He argues anyone training their own models should seriously evaluate diffusion regardless of application, and that non-trainers should expect roughly the same ~1,000x quality jump seen in image generation over five years (Midjourney to Sora/Veo/Flux) to extend into proteins, robotics policies, and self-driving as the technique keeps getting simpler.
Dr. Jon KrohnWhat LLM Size Should You Use? How to Pick the Right Parameter Count (with Sinan Ozdemir)
  • Bigger models are more general, not better at everything. Ozdemir points to the Qwen family, which he believes is Alibaba's, spanning about half a billion to over a trillion parameters, with over a trillion being GPT-5 or Opus-level size and Kimi among open-weight models up there. A big general model is built to serve very different users, so it can do more horizontal things, including ones you do not need.
  • Size models in rough tiers by what the task demands. Ozdemir calls under 10 billion parameters small, enough for lookups, RAG or web search and runnable compressed on a laptop CPU, but not long-horizon tasks with several tool calls. He puts 10 to 100 billion as medium, able to handle agents, especially fine-tuned on task data, and 100 billion plus as large, for enterprise-wide multilingual, multi-task use. He frames the choice as an experiment, testing for example half a billion against eight billion parameters.
Scott HanselmanWhy your inbox is a mess
  • Social-media spam persists because platforms stopped fighting it. Asked why obvious bots still get through, one speaker, who no longer works at Facebook, gives four reasons: it is a hard problem; the research team getting good results was laid off along with its whole division; attackers are sophisticated and getting more so; and the people running social media sites "no longer particularly care about the user protection problem". The other speaker sums it up as less about math than an ongoing battle they stopped fighting. The clip matches Eric Lippert's answer in his Hanselminutes interview.
Scott HanselmanEPISODE 31 - Scott & Mark Learn To...Pilot Coding - Vibe Coding for Real
synopsis

Hanselman and Mark land on AI-assisted coding as a real accelerant, which Mark puts at 10x for himself, that still needs constant human judgment: agents claim success they have not achieved, and the developer's job becomes steering, giving the agent ways to check its own work, and reviewing what it produced before anything ships.

The gRPC test. Mark has twice abandoned a shared-memory transport for gRPC, meant to let Dapr's Go sidecar and loadable modules talk without TCP, after the AI could not solve the concurrency in C++ and then in Go. A weekend retry now passes gRPC's own tests adapted for shared memory and runs the example programs. He says this is premature and unverified, and since he wants to contribute it upstream to a project that will "not tolerate crap", it needs full code review.

ZoomIt's trimmer. By contrast, Mark judges ZoomIt's new trim feature safe to vibe code because it is self-contained. Sonnet 4.5 in GitHub Copilot produced a working clipper in about 10 prompts; requests from Hanselman and a Sysinternals colleague since then (resizing, dark mode, volume, seek buttons) each took one prompt or a short session, except fractional DPI, which took a day. Mark's point is that cheap iteration yields more polish, not sloppier code.

Seeing and steering. The DPI work stalled in "it's fixed / no it's not" loops until screenshots and debug output let the agent see its failures. Hanselman generalizes: any time you copy-paste for the agent, wire up a way for it to see directly. He adds architectural steering, such as declaring an obscure DPI edge case "works as designed".

Live debugging. On air, a dark-mode registry override has regressed. The agent loops through "now I understand the issue" before a one-line fix, a 125% DPI check exposes new clipped text, and Mark shows saved examples of self-congratulating agents. Hanselman closes on git worktrees, with the Worktrunk tool, as the way to run several agents in parallel.

  • A hard concurrency problem the AI twice failed may now work. Mark reports that gRPC shared-memory transport, wanted for Dapr's Go sidecar, stalled on concurrency in C++ and again in Go last fall, but a weekend retry, perhaps reflecting a jump in Opus, passes the gRPC tests modified for shared memory. He stresses he has not verified it independently, and both agree it needs real code review before any PR to the gRPC Go project.
  • Faster turns produced more polish, not worse code. Mark built ZoomIt's new video trimmer with AI, choosing it as a self-contained test of classic Win32 C++; Sonnet 4.5 in GitHub Copilot produced a working clipper in about 10 prompts, and later a volume control plus jump-to-start and jump-to-end buttons came from one prompt. Dark mode took under half an hour; fractional-DPI support took about a day and some 20 iterations, and dark mode is what bumped ZoomIt to version
  • Let the agent see the problem instead of being its eyes. Mark's agent kept declaring DPI bugs "fixed" until he gave it screenshots and had it add debug output. Hanselman's rule: if you catch yourself copy-pasting into an agent, give it a way to see that output itself, such as an MCP server for debug output, Playwright or regular screenshots.
  • Human judgment still catches what the agent's confidence hides. Live, a dark-mode registry override had regressed; the agent repeatedly announced it understood the issue before landing a one-line fix, and a test at 125% DPI found newly cut-off text. Mark's collection of agent failures includes a project that did not build after Spec Kit marked tasks done and Playwright tests reporting a broken UI as fine, though he still calls AI a 10x accelerant for him.
  • Git worktrees let several agents work in parallel. Hanselman explains each worktree as a separate folder on its own branch that Git tracks, so three agents can work on unrelated parts of ZoomIt and merge at the end; he uses a small tool, Worktrunk, to make switching as easy as changing branches. He also flags best-practice skills, such as React ones, and expects tools to enable them automatically within months.
Dr. Jon KrohnAgents vs Workflows: The Most Misunderstood Concept in Agentic AI (with Sinan Ozdemir)
  • An agent chooses its path; a workflow has it chosen. Ozdemir defines an agent as an LLM with access to tools in the function-calling sense, such as searching or reading a file. Most production AI deployments are workflows, he says: retrieval, a human-engineered prompt, an LLM call and display, with the LLM never deciding to use a tool. Take away the LLM's choice of next step and you are in workflow territory; he says he renamed his book from something like "Building Applied AI" to "Building Agentic AI" partly to make this distinction honestly.
  • Agents' unpredictability grows with the number of tools. Ozdemir says modern deployments often start at five to 10 tools, raising questions of which tool goes first, misuse and inefficient repeated searches. The developer ends up hoping the agent navigates that self-chosen path efficiently and correctly.
Scott HanselmanFabulous Adventures in Data Structures and Algorithms with Eric Lippert
synopsis

Eric Lippert, a language designer formerly at Microsoft and Meta, ends up arguing that AI-assisted coding makes deep knowledge of algorithms more relevant, not less: tools can take the syntax, but the problem solving is the job, and curiosity about how things actually work is what the new book is for. Fabulous Adventures in Data Structures and Algorithms was in Manning early access at 7 of 19 chapters when recorded.

Why a book now. An editor's question after another book project led to a proposal of "all the weird stuff you don't learn in school". Lippert still prefers long-form reading for really learning a topic, and says don't outsource the problem solving.

Who it is for. Hanselman notes there is no board certification for programmers and asks whether the book suits someone building text boxes over data with React. Lippert says it is for curious coders: it starts hard, and covers twisted takes on classic structures, developer-tools algorithms such as unification, and stochastic programming, plus a coming chapter on how code formatters work.

Stochastic programming and bots. Lippert retells a joke about AI being linear interpolation, then explains Bayesian updating with 1,000 coins, one double-headed: ten heads (1 in 1,024) moves belief to about 50/50. At Facebook that machinery judged whether new accounts, 999 in 1,000 of them bots by this rough figure, were real. Asked why spam still floods Instagram, Lippert cites a hard problem, the layoff of the entire division, ever more sophisticated attackers, and owners who no longer care about protecting users.

Recreation that teaches. Gosper's Game of Life algorithm, faster on bigger boards, is in the book because it changed how Lippert thinks about functional programming. Both agree some algorithms feel discovered rather than invented, and Lippert says revisiting old blog posts shows "past Eric" understood less than he thought.

  • Outsource the syntax to AI, never the problem solving. Lippert, asked why write a data structures book at "the peak of AI-assisted coding", says turning a real business problem into a clear solution and then into working code is "the whole game"; the syntax step can go to any tool. The book, Fabulous Adventures in Data Structures and Algorithms, was in Manning early access with 7 of 19 chapters out (chapter 7, on category theory, released the day of recording).
  • The book is the unusual material school skips, for curious coders. It is not a tutorial and does not start with Hello World: part one gives traditional structures (lists, queues, stacks, combinatorics, trees, memoized immutable quad trees) a twist, part two covers developer-tools algorithms like unification and anti-unification, and part three stochastic programming from Lippert's Facebook work. A coming chapter explains how code formatters decide what is "pretty".
  • Stochastic programming is principled Bayesian updating at scale. Lippert's example: from a bag of 1,000 coins with one double-headed, ten heads in a row (odds 1 in 1,024) moves you to roughly a 50/50 belief. At Facebook they built language tools for data scientists to apply that updating across billions of observations: is this new account a real person when 999 in 1,000 are bots, is this the broken router, is this reviewer classifying spam correctly.
  • Bot spam persists because the platforms stopped fighting it. Pressed by Hanselman on Instagram crypto-group spam about 40 times a week, Lippert gives four reasons: the problem is hard, the research division getting good results was laid off entirely, attackers keep getting more sophisticated, and site owners "no longer particularly care about the user protection problem". Lippert adds the feed still shows radio-station content farms after more than a thousand blocks, because the models optimize for outcomes other than user enjoyment.
  • Some algorithms feel discovered rather than invented. Lippert includes Bill Gosper's Game of Life algorithm, which computes the future of boards too big for memory and gets faster as the board grows, purely because it changed how they think about functional programming. Hanselman ties this to Douglas Crockford saying he discovered JSON rather than invented it.
Dr. Jon Krohn959: Building Agents 101: Design Patterns, Evals and Optimization (with Sinan Ozdemir)
synopsis

Ozdemir, an AI entrepreneur and author on his seventh appearance, walks through his 10th book, Building Agentic AI. His position is that building agents is mostly disciplined engineering, not model worship. Decide whether the task needs agency at all. Size the model to the task. Evaluate by the cost of errors. Treat reasoning, quantization and other "magic" as trade-offs to measure. The book is the first in the host's Pearson AI signature series, and the host edited it.

Agents versus workflows. Ozdemir says he renamed the book from something like "Building Applied AI" to be honest that much of it is not pure agents. An agent is an LLM with tools that chooses its path; a workflow is deterministic. Most production systems, such as retrieval plus a fixed prompt, are workflows. To choose, he has clients walk through the existing process, which nine times out of 10 settles it. Few conditionals mean a workflow, a handful of pathways a hybrid, and branching at every step an agent. Modern deployments often start at five to 10 tools, and the order and efficiency of tool calls become hard to predict.

Choosing a model. He writes the book around tasks rather than specific LLMs because models will always change. The durable split is between autoregressive models that generate and autoencoding models like BERT. BERT can do embeddings and classification almost as well as a huge GPT model at around 100 million parameters, though he notes diffusion LLMs already bend the categories. For generative models he gives tiers: under 10 billion parameters (CPU-runnable, fine for RAG or search), 10 to 100 billion (multi-turn agents, especially fine-tuned) and 100 billion plus (enterprise-wide, multilingual). He takes Qwen's range from about half a billion to over a trillion as his example. Long context windows help long-horizon agents only if the model can use them; his needle-in-a-haystack test exposed misses, with Grok the worst in the book and Anthropic much improved.

Evaluation. Metrics depend on the task bucket: free text, multiple choice, embeddings or classification. Precision matters when false positives are costly and recall when false negatives are, as in passing a faulty aircraft part versus discarding a good one.

Hybrids and failure modes. OpenAI's deep research always asks a follow-up question, a forced node he says OpenAI accepts because skipped clarification wastes more money. Cursor's plan-then-agent modes do the same. Agents fail in unhuman ways: GPT-4.1 ignored a one-sentence instruction to always consult an Airbnb policy tool 5% of the time. On model preferences, the host says Claude best guesses the output structure he wants from minimal context at the time of recording. Ozdemir links that to Anthropic's emphasis on code.

Reasoning and optimization. The surprise that started as a client hunch is that more reasoning showed no consistent link to performance on MathQA and Humanity's Last Exam. Where there was a gain, it was maybe 1 or 2% for 2x the cost. His benchmark took 5 hours for 180 calls, and one model reasoned for three paragraphs to say hello. Quantization, distillation and LoRA buy memory, speed and cost but "definitely not better": a quantized Llama scored a little worse and its candidate tokens diverged, making it a "cousin" of the original. In fine-tuning a Qwen model with speculative decoding, he found he could predict which questions would not benefit, which he likens to how routing between fast and slow models works.

  • Count the conditionals to decide between a workflow and an agent. Ozdemir defines an agent as an LLM with tools that chooses its next step, and a workflow as a deterministic code path, which is what most production deployments are. His first question to clients is to describe the existing process, which nine times out of 10 settles it. A plain keyword search is a workflow; a few branches suggest a hybrid; a conditional at every step points to an agent. He adds that almost any agent's work can be done by a workflow, and the question is how big and maintainable that workflow would be.
  • Match model type and size to the task, then test. Ozdemir says autoencoding models like BERT cannot generate text but do embeddings and classification almost as well as huge GPT models, at around 100 million parameters. For generative models he uses rough tiers: under 10 billion parameters for retrieval and search, 10 to 100 billion for multi-turn agents (especially fine-tuned), and 100 billion plus for enterprise-wide multilingual use. Context length is not enough either: in his needle-in-a-haystack test models missed his inserted birthday depending on position, and he calls out Grok as the worst.
  • Choose evaluation metrics by task and by the cost of errors. Ozdemir splits evaluation into generative (free text, multiple choice) and understanding (embeddings, classification) buckets with separate metrics. He uses precision when false positives are expensive and recall when false negatives are, and says the question comes before the math: what is expensive to you.
  • Forced workflow steps patch agents' unreliability. Ozdemir's example is OpenAI's deep research, which he says always asks a follow-up question even when told not to, because a skipped clarification costs more than an annoying one; Cursor's planning mode is the same pattern. In one case study GPT-4.1, told in its system prompt to always look up an Airbnb policy article first, skipped the tool and made up an answer 5% of the time.
  • Extra reasoning and compression both trade quality unpredictably. Ozdemir found no obvious correlation between reasoning level and performance on MathQA and Humanity's Last Exam, and elsewhere gains of maybe 1 or 2% accuracy for 2x the cost, which in his consulting almost never pays. He compares a quantized or distilled model to "the cousin" of the original: in his newsletter's quantized-Llama test, it scored a little worse on benchmarks and its top-10 candidate tokens often diverged from the original's.
Dr. Jon KrohnGenAI Has Ruined Coding Interviews; Here's the Fix (with Ashwin Rajeeva)
  • Remote coding interviews no longer work, so his company holds them in person. Rajeeva says that from this year it stopped remote coding interviews, because cheating tools are too many and too hard to detect, and hunting for evidence of cheating spoiled the conversation. In person, candidates get a practical problem resembling daily work, such as failing tests and missing implementations, and may Google APIs under a "gentleman's agreement" not to use an LLM. He concedes that, as more code is LLM-generated, this may not scale, even though staff already get Cursor and ChatGPT licenses.
Dr. Jon KrohnWhy Highly Paid Engineers Quit... and What They're Really Looking For (with Ashwin Rajeeva)
  • Well-paid engineers quit when their work lacks a mission. Rajeeva cites developer-productivity studies that put engineers' productive time at maybe 3 or 4 hours a day, and says creative knowledge workers who can finish their assignments in 2 hours start asking what they are doing. His remedy is making R&D believe it is in the business of innovation, free from being dictated by quarterly plans, even in "boring" fields like enterprise content management. He points to engineer-built Acceldata capabilities such as ODP and a pulse monitoring system, and a next platform version due in May. The host adds a happiness-economics lecture from about 15 years ago putting the plateau around $80,000 to $100,000 of US household income.
  • Hire senior engineers on whether they can build. Rajeeva believes technical management requires people who have been in the trenches. He tests senior candidates on turning any business problem, such as designing an e-commerce warehouse or logistics system, into something built in Go, Python or Java. For new graduates he bets on potential, partly scores and background and partly interest, and decides after a few months.
Scott Hanselman"What was my worst lunch?" AI-Powered Blood Sugar Analysis with GitHub Copilot + Claude Code Skills
  • A skill should give the agent tools, not claimed expertise. Hanselman says starting skill files with "you're an expert" is almost gaslighting the agent; he is the expert in his own diabetes. His open-source Nightscout skill is a skill.md instruction manual plus a Python script (cgm.py) and PowerShell scripts, cloned into the skills folder, and he shows it working in GitHub Copilot CLI, a product he works on, with the Claude Opus 4.5 model.
  • Code does the math; the LLM handles the ambiguity. Glucose readings, uploaded every 5 minutes from his Dexcom G7 to Nightscout (hosted on T1Pal), are cached in a local SQLite database, and cgm.py's commands do the analysis so the model never estimates blood sugar. He says the data stays on his machine and the scripts can also run without AI, or with a fully local model in LM Studio or Ollama.
  • Watch for ad hoc queries and fold them into the tool. Asked for his worst lunch, the agent wrote its own query (over 200 on 10 days; the worst, the day before, rose 200 points in two hours). Hanselman then had it propose generalized commands and added "day" and "worst" to cgm.py, treating the exchange as rubber-ducking.
  • Nothing in a diabetes tool should be hard-coded. He rejected the agent's built-in meal-time presets because "everybody's diabetes is different" and people eat at different times in other countries, replacing them with hour-start and hour-end parameters and an instruction for the skill to ask the user when their meals are.
  • This is AI-augmented coding, not vibe coding. Hanselman says a professional will spend about half the time designing and talking and half reviewing code; he steers the agent mid-task, approves its tool calls rather than running in "yolo" mode, and checks the diffs once the agent commits and pushes, saying he still needs to go through it all properly. He dates the current wave to October and Opus 4.5.
Dr. Jon KrohnThe Mindset Shift Every CTO Must Make to Build and Scale Teams (with Ashwin Rajeeva)
  • A CTO must think in customers' shoes, because engineers won't. Rajeeva, who grew Acceldata's engineering from four to 100 people through COVID, remote work and the return to office, says technologists assume "if I build it, they'll come". Customers act on guidance with two axes, a technology mandate ("we need to do AI") and a business problem, and need wins they can show their leadership to renew a proof of value into a contract. Product managers focus on features and bugs, so if not the CTO, he asks, then who.
  • Early-stage engineers stay when they get room to innovate. Rajeeva says money stops mattering to people past a point, and startups lose context and speed when people churn. He keeps them with engineer-led projects rather than a fixed annual roadmap: an internal data platform (ODP) built to avoid license fees and vulnerabilities, an AI agent that fixes vulnerabilities in shipped enterprise software, and an in-house data-center stack because VMware is expensive and OpenStack too complex.
Dr. Jon Krohn958: Without Trusted Context, Agents are Stupid (featuring Salesforce’s Rahul Auradkar)
  • Enterprises are data rich but context poor, so agents act "corporate stupid". Auradkar argues today's models are incredibly intelligent but do not understand the context in which to apply it, because sales, marketing and service data sit in separate silos. His example: after you buy a car, automation keeps advertising the same car instead of insurance, a warranty or accessories, because the purchase sits in a transactional system the marketing agents cannot see. The episode is a partnership with Salesforce to announce the Informatica addition.
  • Agents need trusted context, not just more context. Auradkar's layers are unified data with governance and trust (lineage, consent, PII handling, masking of unstructured data), real-time signals such as events, transactions and clicks, and historical context on customers, assets and cases. On top of those come business rules, policy enforcement for business and regulatory policy, and domain-specific semantics and workflows that Salesforce says its applications already codify.
  • The unified data engine joins customer data, analytics and integration. Auradkar says Data 360 is a customer data platform that "puts the C in CDP", unlike rivals that served marketing only. It unlocks "trapped" data and reverse-ETLs it to every channel, grounding agents. Tableau Next adds a semantic model, so that revenue, ACV or churn mean the same thing to everyone, plus natural-language "agentic analytics" pushed into Slack or Sales Cloud. MuleSoft extends integration and API governance to agents as an "agent fabric".
  • The latest acquisition adds enterprise-wide catalog, data quality and ETL. Auradkar says the Informatica acquisition legally closed on November 15th, ahead of schedule, and calls it one of the most synergistic in enterprise software. He says Informatica's enterprise data catalog layers over Salesforce's customer data catalog to give a superset of enterprise metadata, alongside data-quality tools, governance lineage and what he calls the industry's best ETL.
  • Salesforce runs on its own agents as "customer zero". Auradkar says help.salesforce.com is now agent-first and agent-only, with humans augmenting, and that a vast portion of customer questions are answered by agents. Background marketing agents and predictive lead scores fire within a 30-second window of a website visit, and an SDR agent is shipping. He cites Williams-Sonoma's Sous Chef agent on Agentforce as agentic transformation at a company's core, not its margins.