Professor G Markets$Platner’s Out. Here’s How Dems Avoid Disaster — with Brian Tyler Cohen
- This post includes paid content that is not available publicly. See the original source.
This introductory "Claude Code 101" lesson argues that speed is no longer what makes an analyst valuable; being trusted is. It builds a minimal harness of one skill, one agent and one hook in Claude Code Desktop, and ends on a hook that refuses, unprompted, to ship a weekly report built on broken data.
Three building blocks. The presenter frames the session around a recurring Monday metrics update. Chatbots make you re-explain the format and paste data every week. Claude Code without structure is "a very confident intern". A skill is the playbook, written once in plain English. An agent is a teammate with its own persona and context, to whom work is delegated. A hook is a rule that fires deterministically at a trigger. The host adds that skills sometimes fail to fire in large systems, which is why must-run tasks belong in hooks, though hooks give up the model's judgment. He uses them for eval traceability, logging every Snowflake query with its SQL, timestamp, ID and question context. The whole folder is the harness.
The demo. The data covers a fictional coffee-subscription app: daily ad spend by channel, and signups, activations and revenue. Running /weekly-review produced a report under the skill's rules (TL;DR, what moved, one risk, one action, under 250 words, one-decimal percentages). It traced a double-digit weekly decline to two days of near-zero paid social activity. Editing the skill to demand a green/yellow/red status light changed the rerun, which rated the week yellow. An exec-reviewer agent playing a VP of growth then returned three questions the report invited, such as whether signups were lost or just miscounted. Finally the presenter changed a value from 772 to 900 so that activations exceeded signups. A Python hook checking duplicates, activations against signups, and negative or malformed values blocked the report from being written. The presenter then briefly showed the lab's open-source "AI analyst" repo in the terminal as the fuller system.
Why it matters. The presenter's closing frame is that every analysis is a bet: impact is the number of bets times the hit rate times the size of the win. AI-built systems raise all three by giving more attempts, deeper slicing, and room for long-shot questions.
Questions. The presenter says they do not code; the host argues the needed skill is validating output, by hand or through evals. Queries over a Snowflake MCP run in Snowflake, and only results land in the folder. The choice between agent and skill blurs, since each can call the other, but agents suit personas such as reviewer, planner, writer or researcher. A generic VP agent knows only the context it is given. The presenter's rule of thumb is chat for questions, Cowork for getting a task done on existing material, and Claude Code for building systems. The host described having Claude work through about 1,200 recorded customer calls, form hypotheses and try to disprove them, with hooks keeping summaries sourced back to the originals.
/weekly-review followed a skill requiring a TL;DR, the one number that moved, one risk, one action, under 250 words, numbers only, and percentages to one decimal. The report traced a double-digit week-over-week drop to two days when paid social reported almost no activity. After the presenter edited the skill to open with a status light, the rerun rated it yellow. An "exec reviewer" agent playing a VP of growth then returned three likely questions, including whether the signups were "lost or just miscounted" and why organic peaked on those same days.Eddie Kim, Gusto's co-founder and head of technology, describes building Gusto Co-Founder — an AI agent that runs small-business processes end-to-end — and argues the real innovation wasn't the product idea but discovering, through his own use of a personal AI agent, that a chat or text interface beats even a well-designed app.
Kim's starting point was hands-on: he spent eight hours setting up a self-hosted, always-on AI agent on a Mac mini, air-gapping it out of caution, and initially found himself using it mainly as "a glorified search engine." The unlock came from texting it simple requests through a messaging app and watching it just handle them, an experience he says no amount of reading about agentic AI had prepared him for. A missed flight home from vacation gave him five uninterrupted hours in an airport lounge, which he used to prototype a version in Claude Code that let Gusto customers request custom web apps in plain language.
That prototype evolved once the team realized the real advantage wasn't building arbitrary apps, but combining a customer's request with the data Gusto already holds about their business — payroll history, industry, behavior — to automate a specific recurring workflow, like the weekly ritual of exporting spa-booking data into a spreadsheet before running payroll. Early versions borrowed a cron-job "heartbeat" pattern from Kim's personal agent, later adding deterministic scheduled triggers once he found the heartbeat alone couldn't guarantee exactly when time-sensitive tasks like payroll would run.
Kim credits the build process itself as much as the idea: five people, including himself, shipped the full product in ten weeks with no product docs, no sprint planning, and no Figma files — just one continuously running Zoom call and heavy Claude Code use, discarding a large share of code they wrote along the way. He argues this was faster than conventional planning because an implementation surfaces information a written spec cannot.
The product launched to 500 customers after a 20-person pilot, with automations ranging from payroll and time-off approvals to weather-triggered customer emails that have nothing to do with Gusto's core software, and Kim says the roadmap will be guided by watching what customers build next, including eventually opening the product to people without an existing company.
Benjamin Todd, co-founder of 80,000 Hours, returns to the show, last having appeared in episode 497 before ChatGPT. He ends up holding that the next five to 10 years may bring change on the scale of the Industrial Revolution or larger, and that this makes career choice more consequential, not less. Individual leverage is rising even as automation approaches. The problems most worth that leverage, in his ranking, include not only alignment but newer and far more neglected AI risks, above all humans using AI to lock in extreme concentrations of power.
The book and its heuristics. The new edition of 80,000 Hours is named for the typical length of a working life. Todd argues that improving the impact or fulfilment of that time by 1% would justify 800 hours, about 20 weeks, of planning. Its ABZ framework pairs a best-guess plan A with nearby plan Bs and a concrete plan Z for if everything fails; spelling out the fallback often shows a risk is more bearable than feared. Rather than precise expected-value spreadsheets, he favours rough quantification to avoid scope neglect, plus heuristics such as working on neglected problems. On passion, a survey of Canadian students found 90% named sport, art or music, against 3% of jobs. Fulfilment, he argues, comes from building valuable skills and using them meaningfully, and the strongest predictors of satisfaction are hour-to-hour conditions such as feedback, variety and autonomy.
AI safety then and now. His advice five years ago to go into AI safety proved well timed; many who took it became founding members of Anthropic. He still calls it neglected. Capabilities work has grown faster, with researcher numbers up perhaps 30 to 40% a year, so roughly 1,000 people do technical safety research against 100,000 to a million speeding up capabilities.
No solid ground. The host asks where practitioners can stand now that Claude handles the technical parts of his own job, and cites METR charts past 16 hours at the 50% success rate. Todd corrects that the 80% rate is about three hours. His answer is that value sits in the current bottleneck, which keeps moving; as AI grows more useful, the human remainder grows more valuable. A full digital remote worker could absorb even adoption work. That would leave legally required human roles, consumer preference for humans and physical work, though he thinks robotics could scale fast. By mass, converting car factories might yield about a billion robots a year, as car plants were turned to aircraft in World War II. A human-level digital worker would be superhuman almost immediately, running about 50 times faster, sharing learning across copies and coordinating without human overhead. Todd wants agents' chain of thought kept in natural language as long as possible so it can be monitored. Work might shrink to "relational" jobs where a human doing it is the point, as agriculture shrank to a few percent of jobs, though he expects many people to live on investment income and UBI instead.
Gradual disempowerment. Even with alignment solved and no dictatorship, Todd describes an economy that slowly turns hostile to humans. People are costly in energy and land compared with digital workers, and whichever nation builds fastest grows most. If chips and robots replace labour as the source of economic power, every state starts to look like an oil state, and the threat of a strike stops checking governments.
The pressing-problems list. 80,000 Hours ranks problems by scale, solvability and neglectedness. Loss of control of AI tops it. Todd says LLMs at least understand human values, unlike earlier score-maximising game agents, but whether alignment is easier than feared is undetermined until agents can plan over long horizons and exceed humans. He cites Meta research that reward hacking rises with problem difficulty. Second is extreme power concentration, with perhaps 20 specialists. Recursive self-improvement could compress three to 10 years of progress into under a year, possibly around 2028, and turn constant leads into widening ones. One company could hold 200 million digital workers, and AI could make universal surveillance feasible. Third is engineered pandemics: no super-virus is possible yet, he says, but one may be soon. Emerging priorities include the moral status of digital minds, which he thinks we should treat as possibly sentient, and S-risks, outcomes worse than extinction such as AIs threatening simulated suffering. Climate change ranks ninth on urgency, future cheapness and its inability to end civilisation.
Where practitioners fit. Alignment has moved from big-picture theory to empirical work bottlenecked on AI engineers for control, monitoring, red-teaming and interpretability, with the MATS and ARENA programmes and a three-month transition guide as on-ramps. Power concentration has technical questions about whose commands AI follows and how access is controlled. Governments want data scientists to track labour impacts, and pandemic preparedness needs builders for wastewater sequencing. As a lower bound, Todd says, earning and donating can save a life for $3,000 to $4,000. Todd's conclusion is that this leverage raises the stakes of the next few years, because only this short window can shape the transition.
Vlad Tenev, Robinhood's co-founder and CEO, argues that retail investors are now the disciplined money, backing frontier companies on their fundamentals rather than repeating the stimulus-fuelled froth of 2021. He ends on private markets: since trillion-dollar companies now list late, retail ownership has to reach pre-IPO and even seed-stage capital, through Robinhood Ventures and tokenization. Frost frames the company's arc: IPO in July 2021 at $32 billion, down 80% to $6 billion in 2022, now just over $90 billion with $380 billion of platform assets.
The 2021 froth. Tenev says he expected inflation when 10-year breakevens sat near 2% despite money printing, and that the rise toward 9–10% made rate hikes predictable. In Robinhood's data, stimulus money reached the market within days or weeks. Lockdowns, spare time and zero rates fed the January 2021 meme rally, and customers bought COVID-hit nostalgia names.
Smart money and today's market. In his view institutions rebalance on macro and sell good businesses, while retail judges companies. Today's customers hold SpaceX, Nvidia, Tesla and chipmakers. He says AI is unlike past bubbles because revenue exists; the open question is whether customers start demanding ROI. IPO windows, he notes, are reopening faster each cycle.
Why Robinhood worked. He names three things: zero commissions against $7–10 a trade, a mobile-first design, and an ownership message to a generation shaped by 2008 and Occupy Wall Street. He sets that message against Bulgaria, where inflation passed 2,000% in 1997.
Penetration. Tenev expects US participation to rise from 65% toward the 90s, helped by Trump accounts for newborns. In the UK, where one in six people hold equities, Robinhood is launching ISAs with a 2% match. He wants Robinhood to be one of the UK's largest employers, which he admits is aspirational. Frost adds that over 50% of Britons placed a bet in 2024.
Tokenization and privates. Robinhood Chain will carry 24/7 stock tokens in 120+ countries, backed one-to-one, he says. Robinhood Ventures Fund One holds Stripe, OpenAI, SpaceX and Revolut. Tenev insists on issuer buy-in.
AI and the human trader. Tenev expects humans to keep trading: if everyone ran the same agent, its edge would shrink. He expects Robinhood's newly launched agentic trading to take share from pro-sumer and eventually institutional trading. He rejects the idea that only firms at massive scale can compete in AI, citing DeepSeek's reported $6 million frontier model and cheaper post-training.
Ownership as the American dream. Having arrived from Bulgaria in 1992, he describes the American dream as moving from home ownership to broad asset ownership. His closing advice repeats the case for democratizing private markets, with appropriate guardrails.
This lightning lesson argues that AI belongs inside the spreadsheets stakeholders already live in, as long as the question and the numbers are checked first. It ends on a side-by-side in which Gemini in Google Sheets builds a partial tracker from a prompt, while Claude Code, armed with a prebuilt skill and Python helpers, builds a full tracker with chart and insights tab in minutes.
Why sheets. The presenter says that at past companies, despite polished dashboards, Google Sheets was how leaders actually consumed metrics, and that feeding those sheets is tiring work for data teams. The host adds that most people who do analysis work in Sheets or Excel, not Python or SQL, and that a sheet is easier to validate than an opaque script.
Question and checks. The method is a four-step loop: ask, check the data, visualize, summarize. Framing comes first, because a wrong question makes the output meaningless. Before any number is trusted it gets three tests: totals that sum, magnitude within a plausible range, and one known value verified. The presenter presents these as natural evals and describes a weekly metric anomaly engine they built that ran them before a metric's owner looked.
Gemini demo. On the lab's synthetic e-commerce data, Gemini charted the three-month revenue trend, added a formula-backed day-of-week column, and ranked months consistently with the chart. Asked for a tracker with week-over-week and month-over-month views, it planned and built only week-over-week, which the presenter attributes to the prompt.
Claude Code demo. Using Opus 4.8 with 1M context in auto mode, Claude Code produced an October 2024 tracker with segment breakdowns, week-over-week changes, conditional formatting, a chart, and an insights tab against September. It finished in about a minute, because an existing create tracker skill, an orchestrator script and a Sheets wrapper did the work; the original build took about 10 minutes of iteration. The presenter concedes the comparison favored Claude Code for that reason.
Questions and transparency. The host argues that a companion sheet lets stakeholders trace AI-produced numbers without reading SQL or logs. The presenter suggests logging every pipeline step to its own tab. On dynamic scenario forecasts, the presenter would build a parameter-driven Python file triggered by a skill, as they have for HTML dashboards, but has not yet done it in Sheets.
create tracker skill, a Python orchestrator and a Sheets API wrapper were already in the repo. The first build took about 10 minutes of iteration, and their Google Sheet creator agent was not called this time. They concede the comparison with Gemini "cheated", since Gemini had only a prompt.This compilation of five June clips circles one question: what stays valuable as AI absorbs technical work. The answers run from people problems and interface design, through hard-won product judgment and the physical plant behind AI, to self-awareness. It ends with the host's view that AGI needs no consciousness, but that its real-world breadth is still years away.
Where the moat goes. In episode 999 the host describes his own lost technical moat. Chip Huyen answers that people problems remain. A founder who pitched agent orchestration to fix poor product-engineering communication was, in her view, misdiagnosing a human problem. She also sees open questions in human-AI interfaces and in making the world AI-ready, from better APIs and permissions to city street-light APIs for delivery robots.
Building on moving models. Astrocade's founding AI lead, interviewed in episode 997, joined in April 2023. He says the company adopted Claude Code across the board around June 2025. Its edge is not special ingredients but how agent, prompts and tools are combined and evaluated, which is hard when one game request has a million valid answers. Its costliest lesson was that scaffolding built before vibe coding worked became a limit once models improved.
The physical layer. Lightning AI's Frank Basso, in episode 1003, describes data halls at 105 to 110 decibels. Active noise cancelling would itself produce that level, so staff wear passive in-ear and over-ear protection and talk by radio or hand signals. Liquid-cooled halls are no quieter, and are threaded with overhead water mains and hoses.
Self-awareness. The episode 1005 guest defines self-awareness as overlap between how you see yourself and how others see you, and cites research putting it at 15% of people. Journaling, meditation, exercise and less reflexive phone use built his.
AGI and the brain. Interviewed by Kirill Eremenko in episode 1001, the host adopts Google DeepMind's tiered definition of AGI. Screen-based tasks have reached some tier, he says, while physical-world breadth has years to go. He sees no need for consciousness, and argues brain-inspired designs need not be the best route given silicon's different speed and scaling.