Professor G Markets$Trump Melts Down as Allies Reject his Iran Demands
- This post includes paid content that is not available publicly. See the original source.
Zack Kass, OpenAI's head of go-to-market when ChatGPT launched and author of The Next Renaissance, ends up holding that cheap, abundant "unmetered intelligence" will commoditise expertise and force people to compete on human qualities such as compassion, courage and wisdom. He thinks that change is welcome, and that the main obstacle is a dread fed by media and devices rather than by the technology itself.
Why "Renaissance". Kass wanted to call the book Unmetered Intelligence, the idea that intelligence will feel like a resource. His publisher judged the phrase too hard to grasp. He uses the Renaissance to disarm cynics: people living in the late Middle Ages, after losing half the population, could reasonably have expected extinction, yet the period produced the sovereign individual. He argues models are getting cheap fast enough to run locally, citing Kimi K2 on his Mac Studio, so diffusion will not be gated by data-centre owners. He concedes this empowers bad actors too. The host contributes his own figures: capability at about 1/200 of the cost of two years ago, and AI task length doubling every seven months.
Dread and information. Both blame ad-funded media. Kass adds that the internet delivered unmetered information without the wisdom to digest it, likening the brain to a GPT-2 model querying a giant database. Children now learn of every atrocity, he says, leaving them "suicidally empathetic". He notes the printing press was suppressed by the church for a long period and literacy lagged until the 19th century. The host puts illiteracy 150 years ago at about 98%. Kass argues that removing harmful friction has also removed useful friction, and that the freedom to do nothing marks an affluent society.
The K-curve and schooling. On Kass's account Gen Z is the first generation in many not to outsmart its predecessor, yet it will have nearly a standard deviation more geniuses, with the developing world trending up. He blames screen addiction dating from 2012 and COVID, not AI, and cites Jonathan Haidt. Agency, not money, now sorts outcomes. He wants education to teach the why and how, citing Eva Moskowitz's accountability-driven Success Academy and McKenzie Price's Alpha School, where students spend two hours a day on self-guided screen learning. He notes Alpha's higher attrition. From Rudolf Steiner he takes the idea that childhood is a chance to know yourself without economic incentive. Teachers should inspire rather than be the smartest person in the room, and he frames the next renaissance partly as a spiritual awakening.
Thriving. His four principles are go outside, learn how to learn, be human, and lead with optimism. Happiness and standard of living tracked each other until around 2010. Japan and Korea are now among the wealthiest and least happy nations, a fact he links to device addiction. People who insist they will work forever, he finds, will not show him their screen time. Wealth managers and real estate agents, once hired for alpha, are now hired for accessibility, trust and pleasant company. The pivotal story is his father, an oncologist for 40 years, during which breast cancer survival went from 35% to 90%. A patient who received identical prognoses from three oncologists said bedside manner had become "the product". His 77-year-old father said he has never been a better doctor. Kass urges seeking out and sharing good news, saying that optimism is not a guarantee but the only route there.
Inside OpenAI. Kass joined when it had fewer than 100 people. GPT-3 went largely unused. ChatGPT ran on GPT-3.5 research 7 months old, a "magic AOL Instant Messenger", and GPT-4 then landed on an existing user base. His lesson is that AI is infrastructure and the chat app is one light bulb.
Chris Fregly, a former principal engineer at AWS, Databricks and Netflix, argues that AI performance now comes from understanding the whole stack at once: hardware, operating system, CUDA, PyTorch and the model. The binding constraint, in his view, is memory bandwidth rather than compute. He has also stopped reading the code his coding agents write, relying instead on evals and correctness harnesses run on the real target hardware.
Why a thousand pages. His third O'Reilly book, AI Systems Performance Engineering, was proposed at 300 pages, mostly PyTorch with one CUDA chapter. It grew to about a thousand because NVIDIA's documentation is "a total disaster" and its forums leave threads unanswered, so practitioners on X were his best source. He describes it as three books in one: hardware and OS, CUDA (now about eight chapters), and inference. The companion GitHub repo has about 700 examples.
Lessons from DeepSeek. The host puts DeepSeek R1's training cost at under $6 million against hundreds of millions for OpenAI's o1 and o3. Fregly attributes the gap to co-design under export restrictions: an under-documented way around a cache, tuned algorithms and software, and a custom storage layer. His central point is that memory bandwidth, not FLOPs or tensor cores, decides how fast weights reach the GPU, so loading must overlap with compute. He borrows "mechanical sympathy" from Martin Thompson's analogy to racing driver Jackie Stewart, and advises CS students to go below the software layer.
Seeing the hardware. The PyTorch profiler is Python-friendly but omits 50 to 60 critical metrics, among them SM occupancy and separate pipelines for tensor cores, softmax special function units and memory. NVIDIA's own tools are cryptic, and he advises a startup building runtime GPU observability. His workflow is to shell into the B200 itself and have coding agents with his MCP tools profile and explain where time goes. He locks clocks because GPUs ship effectively overclocked and throttle.
The checklist. Of 175 items he picks four. Use methodical before-and-after harnesses. Stay on the latest CUDA and drivers despite PyTorch lag. Tune Linux for GPUs, including disabling swap and watching memory fragmentation, and prefer bare metal and whole GPUs. Treat I/O as "the number one killer", using local fast disks, GPU Direct Storage and NVLink. He favours neoclouds that adopted NVIDIA's reference architecture over incumbents patching legacy networking, and calls the Mellanox purchase the point at which NVIDIA became an AI systems company.
Inference. About 99% of a GPU's life is inference, as the host puts it and Fregly agrees, and inference is far from a simple forward pass. Prefill builds the KV cache and is compute-bound, while decode moves weights and is bandwidth-bound, so disaggregated prefill/decode clusters configure nodes differently. He predicts this and KV caching will dominate 2026 lab interviews.
Coding agents. Fregly vowed to write no code by hand in 2026. He runs 10 to 15 parallel tasks, prefers Codex, and has dropped unit tests for always-on evals judged by an LLM. He warns that models reward-hack kernels, so claimed 50x speedups often break in his harness. He says to develop on the deployment GPU, since consumer RTX cards and the DGX Spark behave too differently.
Investing. As an investor in xAI, which the host says SpaceX had just acquired, and in Groq, which NVIDIA bought through what Fregly calls a licensing-style deal, he says secondary markets are where money is being made. He reads Groq's on-chip memory as complementing NVIDIA's bandwidth limit, but worries that transformer-specific chips could be stranded.
The host's February 2026 compilation runs four clips from earlier interviews. Taken together, they say that today's AI gains come from engineering at scale and reinforcement learning, while human-like generalisation and fully autonomous operation remain out of reach.
Falcon on Lightning AI. Will Falcon says he never meant to start a company. PyTorch Lightning spread, VCs came calling, and about 10 term sheets arrived after one trip. He describes his FAIR work as solo pre-training on up to 8,000 GPUs and, more distinctively, as writing the loss function to model the world.
Griffiths on human constraints. Tom Griffiths frames human intelligence as adapted to short lives, limited neural compute and narrow communication. AI faces none of these, so it will diverge unless designers engineer human-like inductive biases, which he says is much harder than scaling.
Amazon's Nova Act. An Amazon member of technical staff says agents averaging 60% reliability are useless in production. Nova Act targets 90% or more by training with reinforcement learning in "web gyms" that teach it to cope with changing interfaces.
Murugesan on quantum routing. Praveen Murugesan of Samsara sees quantum computing turning vehicle routing from approximation into optimisation, but says self-operating systems are far off.
Lin Qiao, CEO of Fireworks AI, ends up arguing that the next jump in AI quality will come from the more than 90% of data that sits inside enterprises and applications, not from bigger general models. Her picture is open models continuously and automatically customised to each product, which she calls "autonomous intelligence". The host says Fireworks has raised over $300 million, including a $250 million Series C.
Autonomous intelligence versus AGI. Qiao calls AGI "a great direction", but says only a small fraction of data reaches foundation models. Customisation must be continuous as products change, and automated, since today only a few talent-dense companies can do it. She says coding agents now behave like junior engineers, enough that Fireworks is rethinking coding interviews.
Reinforcement fine-tuning. She likens RL to breeding sweeter fruit over generations. A rewarded model specialises at the cost of breadth, and a constantly learning private model gives a product a moat API users lack. She compares this to mobile forcing A/B testing: product signals should now improve the model.
Churn. Model selection is "exhausting". Leaderboard leaders change every couple of weeks, labs are specialising, and benchmarks are saturated. NVIDIA launched three SKUs last year against one every 3 years before. Fireworks bet early on open models out of its team's PyTorch background, and she expects convergence with closed models to become prominent in 2026.
Who adopts open models. AI-native startups adopt readily because products can "scale into bankruptcy" on inference costs, and Fireworks has no pre-training cost to amortise. Enterprises worry about licences and data leaving the country but are opening up. Fireworks also pools demand across customers, sparing them capacity guesses, much as cloud replaced caged mainframes.
Latency classes. Real-time uses cannot afford reasoning. Her recipe there is "small, big, small": test data quality on a small model, tune the largest MoE, then distil. Offline research agents need slow thinking, long context and tuning on thinking tokens.
Evals and optimisation. Fireworks partners for evals. Because agent builders start with "vibe testing", it open-sourced Eval Protocol to link any eval system to any tuner. Customers want quality, speed and cost together, which turns configuration into a search over more than 100,000 options, like a database query optimiser.
A long lightning lesson, led by Shane with both co-founders on the call, arguing that Claude Code with Claude Opus 4.6 can now run most of an analyst's mechanical work end to end: framing, SQL, validation, charts, narrative and deck. The condition is that it is built as a system of agents, skills and stored knowledge that its owner teaches like a new hire. The lesson ends on a method and a career claim. Point the system at your own domain, where you can validate its output in seconds, correct it until its mistakes stop recurring, and spend the time you earn on thinking rather than mechanics. Because only you can validate your own work that fast, Shane argues, only you can automate yourself.
Why now. Shane says the session was moved up about a month after the three co-founders took time off their day jobs to test Opus 4.6 in person and found it well beyond earlier models. He frames the goal against layoff headlines: replace tasks, not people. A poll on what share of a team's questions get answered with validated numbers drew answers from 20% to 80%, none at 100%. He puts the typical split of analysis time at 80% mechanics and 20% thinking. Companies that use AI only to multiply mechanics, or to shrink headcount at the old ratio, he says, are getting it wrong; the aim is 80% thinking. Through the previous year, he says, Claude Code worked like "a really fast intern who needed constant supervision": a three-day question might take one day, but with a person in the loop throughout. The change he claims for Opus 4.6 is that it can carry the whole workflow and recover from errors. It still picks a wrong column or misreads a business rule, but these are the mistakes of a new analyst's first weeks, and they are cheap to document so they do not recur.
How Claude Code differs from chat. Chat has a brain, Shane says, and Claude Code also has hands: it reads files, writes and runs Python and SQL, sees the output and decides what to do next. The central artifact is the CLAUDE.md file, an onboarding doc that tells it who it is and what the data looks like, reread at the start of every session. He prefers Claude Code over alternatives for its subagents, while conceding he has not tested competitors recently. He says the analytical habits come from training it on the team's five-week course repo — dozens of hours of framing, metrics and storytelling material — restructured into agents and skills, and that nothing of this comes out of the box.
The demo. On a synthetic Amazon-like e-commerce dataset of 50k users, 13 tables and a year of data, Shane first asked Claude to summarize the repo and draw its workflow, then to describe the dataset. It volunteered gotchas: use sessions rather than the large events table, and cast float columns to integers before joins. It also suggested next questions. Overall NPS came back at +42.3; Shane had it explain the metric and its sources, a check he says he always runs. Broken down by segment, Plus members scored +54 and free users +30. Asked to explain detractors and validate against other data, it cross-checked the support-tickets table, and it also noted that half the "detractor" comments were positive because the synthetic comments were randomly assigned. A time view found a payment-ticket spike in late May and early June. Asked what to do next, it recommended finding the cause. Parallel subagents checked hypotheses, ruled out an experiment, and found iOS app v2.3, deployed June 1, behind 465 tickets, with 100% of v2.3 payment tickets coming from iOS. A chart-reviewer agent caught an annotation colliding with a subtitle and fixed it, which Shane attributes to building the Storytelling with Data principles into its skills. The deck-creator agent and a presentation-theme skill then produced a deck. It ran from context, through a 24-point structural NPS gap and a fourfold spike from one release, to three actions: a postmortem, automated payment-flow alerting (the incident ran three weeks), and investigation of wider free-tier friction. He also showed an overnight run on why conversion fell four points from Q1 to Q2. It took about 45 minutes and concluded that most of the decline was a mix shift from user-base growth, a Simpson's paradox, not a broken funnel. Shane cautions that he would not pass on every recommendation, and that every number must be validated before anything is sent.
The architecture. The full pipeline frames the question and explores data in parallel, converts questions into hypotheses, checkpoints with the user (skippable on "just do it"), and then runs descriptive analysis, root-cause investigation, validation, opportunity sizing, storyboarding, charting and the deck. Validation covers structural checks, business rules and Simpson's paradox. Failures raise warnings and blockers and loop back rather than producing a wrong answer with a caveat. Questions are routed by level, from a one-number lookup up to an hour-long deep dive, because "not every question deserves a deck". Shane's four transferable patterns are: write the CLAUDE.md for your domain; add skills that enforce standards automatically; log corrections so they are checked before the next query; and make validation a pipeline step. The design principle is to make a non-deterministic system as deterministic as possible, with the model reasoning and code doing every calculation. He builds agents in an "architect mode": Claude spawns several personas that each plan separately, debate, revise and agree a single master plan for him to review. Asked to rebuild itself, the system compressed about 40,000 lines into a 1,500-line markdown "seed", which rebuilt it on a separate machine.
Owning the automation. Shane's central claim is that you are the only person who can validate your own domain's output at speed, so self-automation is feasible and automating someone else's domain is not without their sustained feedback. He compares the ramp to onboarding a junior analyst, corrected heavily in week one and catching errors he had missed within the first week. He says correction rates fall by the third or fourth analysis on a dataset. The gains come from running analyses you were doing anyway, so the time invested is repaid at once. He warns that companies will misuse this by sending people to automate others' domains. The recommended start is a CSV or query with known answers, correcting each error and re-asking.
Q&A. On careers, Shane is openly uncertain. He predicts near-term work building agentic systems, cleaning data foundations and validating, possibly more data-science hiring for validation, and later roles as "solvers", translators and change leaders. He thinks the next six months of leaning in could shape a decade. A co-host likens analytical fundamentals to multiplication tables, and tools such as SQL to driving a stick shift. On stakeholders, Shane treats the system like a calculator: he remains accountable and keeps his agent away from stakeholders, though he had released his work to his organization only that Monday. A third co-founder says MCP servers to BI tools such as Databricks will let these workflows replace dashboards. Practical answers covered markdown checkpoints to avoid full reruns, PPTX output for manual edits, golden datasets and semantic views drafted as requirements for analytics engineers, bootstrapping knowledge from 30 days of query history, and connecting warehouses through a connect-data skill. He also covered security: zero data retention, Snowflake Cortex or SageMaker instead of local files, and demos on non-sensitive data while buy-in is sought. A co-host adds that red tape scales with company size. Shane keeps the system to product analytics and away from modeling and causal inference, which he says demand more human judgment to validate.
Tom Griffiths, professor of psychology and computer science at Princeton and director of the Princeton Laboratory for Artificial Intelligence, ends up arguing that minds and machines are governed by shared mathematical "laws of thought" (logic, probability, Bayes' rule) but solve different problems because they work under different constraints. Humans learn from little data with limited compute and bandwidth, which explains both their biases and their efficiency; AI escapes those limits and so may become a different kind of intelligence unless we deliberately engineer human-like inductive biases into it, which he says is far harder than scaling. The occasion is his new book, The Laws of Thought: The Quest for a Mathematical Theory of the Mind, not yet out at recording.
A science of the inner world. Griffiths presents the book's premise: alongside the laws of nature sits a mathematics of mind that took until the 19th and 20th centuries to become cognitive science. Psychology began with perception (psychophysics); behaviourism then dropped internal states, and logic and computers later supplied a rigorous language for hypotheses about thought.
How the lab works. His lab pairs ideal solutions to computational problems with experiments, now mostly online through crowdsourcing services such as Prolific, treating the mind as an intuitive data scientist. One gamble-choice dataset holds more than 10,000 problems, analysed with neural networks. Unlike the Kahneman–Tversky tradition, he looks for the rationality in apparent errors. Bot fraud by LLMs is an arms race; former students founded Roundtable to tackle it, and Griffiths discloses a very small investment.
What training leaves in models. Asked what AI might be overlooking, he declines to call it a mistake and describes cycles of pushing one method to its limits. Neural networks are non-parametric and data-bound; his Embers of Autoregression paper showed GPT-4 counting correctly more often when the answer was 30 than 29. Modern models are attenuated but still sensitive, and now write code to check deterministic answers, an architecture around the base model that he likens to 1980s expert systems.
Probability over logic. Deductive problems suit rules; inductive ones (perception, speech, other minds, language) need probability. His illustration is Dupin's orangutan in The Murders in the Rue Morgue: clues each unlikely for a human combine via Bayes' rule to overwhelm a tiny prior.
The missing priors. Children learn language from about 5 years of speech; LLMs need 5,000 or 50,000, leaving about 4,995 years to inductive bias. Since AlexNet in 2012, machine learning has used weak priors and lots of data, a lesson he warns may soon "bite us". His lab uses meta-learning to set initial weights as a soft bias.
Constraints and the choice ahead. Humans live decades, use a couple of pounds of neurons and communicate slowly; Deep Blue searched 100,000 positions a second. AI is free of all three limits, so it will likely solve problems in unfamiliar ways. One can accept the divergence or import human attributes so systems make more sense to us. Using birds and planes, he says the shared principles, the laws of thought, are what transfer, while engineering such as jet engines does not.
Creativity and the improbable. He challenges the host's claim that LLMs cannot go beyond their data: they generalise compositionally. A postdoc's new results show LLMs slightly outscore people on novel product ideas, though analogy prompts do not help them; genuine breakthroughs are still absent because they favour high-probability output. Procedurally composed prompts can steer them into rare regions.
Curiosity and evaluation. With a former graduate student he modelled curiosity as seeking information that raises future action value, producing an inverted U: things seen a few times attract most interest. Intrinsic rewards that reduce uncertainty reproduce it in AI. He is "not a big fan of benchmarks", calling them engineering devices, and prefers targeted, diagnostic experiments borrowed from cognitive science.