Professor G Markets$Trump Brags About His Big Greenland Grift
- This post includes paid content that is not available publicly. See the original source.
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.
Tom, Scott and co-host Sol run another viewer-and-caller Q&A, moving from career advice through management mechanics, a brutal natural-gas trade, a dispute over quoting index moves, and closing on gold, silver and bank stocks. The thread tying it together is a bias toward taking risk deliberately rather than defaulting to convention, in business, compensation, or hedging alike.
Best business advice. Scott credits his entrepreneur father's resilience — the ability to fail and get back up — as the lesson that stuck; Tom argues the real edge is taking every risk opportunity without hesitation, citing Google, Meta and Apple's practice of acquiring hundreds of companies a year knowing most fail, because the rare hit (YouTube, WhatsApp) redefines the company.
Scaling multiple businesses. Caller Alan, running a trading Discord and a Pokémon-card distributor simultaneously, describes being stretched too thin as the sole operator of both. Tom argues scaling three businesses is no different from scaling one from $10 million to $300 million — a learnable skill, not a limit; Scott disagrees, suggesting something is likely already suffering and Alan should eventually hire operators for the non-trading businesses while keeping personal control only of trading.
"Peanut butter" raises. Responding to a viewer frustrated that 55% of Fortune 500 firms plan flat-percentage raises regardless of performance, both call across-the-board raises a sign of managerial laziness, contrasting it with their own practice of flat base raises paired with an individual bonus pool for outperformers. Their caveat: virtually every employee believes they exceeded expectations, so a manager's job is to weigh that claim skeptically rather than take it at face value.
A natural gas trade gone violent. A caller describes a short strangle in natural gas up over 70% against him in three days after a geopolitical news spike; both commiserate with their own natural-gas pain this week and call it, with copper, the most dangerous futures contract to trade. The "widowmaker" nickname, they explain, comes from the CME floor's March/April natural-gas calendar spread — a trade retail avoids because its margin requirements are far higher than what floor traders once used to run it on almost no capital.
Points versus percentages. A caller's pet peeve — that quoting index moves in points is meaningless without knowing the index's level — triggers a genuine, long-standing disagreement: Tom insists traders should only ever hear point moves ("handles"), calling percentages meaningless for trading decisions, while Scott and the caller prefer percentages for the same reason. They settle on reporting both going forward.
Collaring a portfolio of call spreads. A caller wants to hedge a book of deep-in-the-money long call spreads correlated to the NASDAQ; Tom's fix, since the position is already all spreads, is a "cashless, verticalized collar" — selling call spreads and buying put spreads both just outside the expected move, sized narrower than the core position so a sharp rally doesn't erase existing gains, with dividend risk on the long calls the only real ongoing concern.
Gold, silver and big banks. With gold near $4,900, both decline to chase it further, framing the risk-reward as roughly 3% of upside against 10% downside — "bad pot odds" — while silver sets a fresh all-time high mid-segment. On banks versus fintech, both call large banks "priced for perfection" and reliant on outdated, fee-extractive revenue vulnerable to disruption, preferring beaten-down names like Coinbase and Robinhood instead.
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.
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.
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.
Olly Hughes, co-founder and CEO of Count, argues on the Data Neighbor podcast's series on the analyst's new toolbox that data teams have been trapped as a support function by tools built for an old problem, and that their real job is to visualize the business clearly and act as its problem solvers. He ends on Count's agent working inside a shared canvas, where analyst, stakeholder and AI break a problem down together and every output stays editable. His closing claim is that data teams already have the superpowers they need, full visibility of the business and problem-solving skill, and that purpose, not tooling, is what keeps them from being replaced by AI.
Origin. Hughes trained as an engineer and started as a consultant inside factories, including a can-making plant in Germany, finding bottlenecks with pen, paper and a stopwatch, then did data work at Tesco and at startups. Working as a consultant he found Tableau and Power BI were tools "to see a number again and again", not to make a decision, and that clients did not feel the numbers were theirs. Power BI's launch, which he dates to around 2015, and having to learn DAX convinced him and his co-founder, also called Ollie, that dashboards were the wrong answer. Shane recalls telecom dashboards that leaders liked and frontline staff found a barrier; Hughes replies that only the executives lacked visibility.
The service trap. Hughes's hypothesis is that the BI tool is among the most expensive, lowest-ROI software a company buys, because it solves a two-decade-old problem of getting data into the business when companies now have too much. He says that in interviews with 400 data leaders they told him about 90% of their teams' work maintains the status quo, such as accurate sales tracking, and adds no incremental value; the best teams he has seen reach 50/50 or 40/60. He names four traps: drowning the business in information; acting as an answering machine, which AI could make a "Cambrian chart explosion"; retreating from stakeholders; and building things the business cannot see. His test is whether the exec team can name three examples of the data team driving value last quarter. A co-host adds that stakeholders' questions degrade when all they ever get back is charts.
Purpose as the fix. Hughes's remedy is operational clarity, making the business look simple with the least information, which leads stakeholders to ask better questions about bottlenecks rather than about what is going on. Beyond that, the team should be the organization's problem solvers, working in agile iterations with stakeholders instead of a waterfall of spec, model and report, and should track time to decision. Purpose, he says, is also what lets a team say no.
The canvas. Count's interface, in his description, is an infinite collaborative whiteboard like Miro or Figma, running on live data. He showed a metric tree breaking revenue into MRR, churn and upsell, and a metric map of about 60 onboarding-funnel metrics a customer built for an activation project, with SQL cells whose dependents are traced and which can be pushed to dbt or a semantic layer. He says customers also use it as a dbt IDE, and answers the complaint that canvases get messy with "thinking is messy".
The agent. Hughes says Count held back on AI to get the paradigm right first, since AI amplifies whatever it is given. In the demo two agents ran at once: a narrow request for New York sales over time, and an ambiguous question about Chicago, which the agent broke into facets before reporting that Chicago ranks seventh in sales but loses money through excessive discounting, mainly in office supplies. Outputs are editable, the agent picks up edits as context, and conversations are visible to collaborators. Shane adds his view that nondeterministic AI products make data science more important. Hughes stresses teams can work this way without Count.
The show opens on a red morning that reverses into a rally, with bonds selling off hard as rates climb against the grain of Fed-cut expectations and gold pulling away from a battered silver. Viewer questions carry the hour, and the hosts use them to argue that discipline — consistent size, staying engaged, defending naked puts by rolling rather than panicking — matters more than any single call, while dismissing prediction markets as a costlier, worse-structured alternative to listed options and sportsbooks.
Trade sizing and market structure. Answering a question on "trade small, trade often," the hosts put typical retail size at ten contracts and under, versus an industry average near 3.5–4 for options and about 1.25 for futures. They note Nasdaq is rolling out Monday/Wednesday, stock-settled expirations for a handful of names, framed as another step toward the market eventually offering daily, hourly, then ten-minute expirations.
The bond market ignoring the Fed. Bonds broke into the 113 handle even as the market expects the Fed and a future chair to cut rates quickly; the 10-year yield rose to roughly 4.3%, up from weeks earlier. One host has been selling February 114 puts (31 days out) into exploding premium, entering more at 110 as bonds fell further. The takeaway offered is that the bond market drives the Fed's hand rather than the reverse, and that no single macro explanation for bond moves is reliable.
Taxes: pay them and move on. Asked whether to trade for after-tax efficiency or maximize profit first, the hosts favor the latter, calling taxes "a high-class problem." The one concession is that SPX, as a Section 1256 contract taxed 60% long-term/40% ordinary, is mildly more efficient than SPY, and that investors sitting on years of unrealized stock gains face a genuinely different calculus around timing.
Short silver, long gold. One host has been short silver since it broke out, scalping the short side profitably every session since Sunday night while his core short position, held through the move from the 52 handle to 94.25, has taken heavy losses. He holds long gold as a partial hedge — the gold/silver ratio near 150 — but is short far more silver than he is long gold. The other host argues the risk-reward now favors staying short given how extended the move looks.
Prediction markets versus sportsbooks. The hosts argue prediction markets aren't a better experience than DraftKings, FanDuel, or Vegas books: fees can run 1–2%, producing effective spreads up to roughly 10% once width and fees combine, on markets that are otherwise the same odds. They won't meaningfully compete with listed markets until they move to an exchange model, and one flags a new Illinois per-bet tax passed through to bettors as a troubling precedent for taxing financial markets. On AI, they see no predictive edge for outcomes, only a possible use comparing which platform's fee-adjusted price is better.
Defending a naked put. Asked how to roll a threatened short put, the stated sequence is: first sell a call against it with roughly half the delta; only if rolling out in time, expect about a 30% reduction in risk and the ability to roll down a full strike, adding both duration and cushion.
Trading routine. A caller's question draws out that the hosts' real discipline isn't a fixed schedule but staying continuously engaged with markets, and consistently selling options around a 22–30 delta, roughly one standard deviation out, regardless of underlying symbol.
Naked puts as the historical top performer — with a caveat. Asked for the single best options strategy, the answer is naked puts and covered calls, cited as the best risk-adjusted performer since 2009 with almost no drawback. But this is immediately qualified: it's a strategy that has worked because there's been no sustained down move in roughly 18 years — last April's near-20% selloff reversed quickly — and if that changes, the strategy's edge likely doesn't hold. Both hosts say they personally prefer selling strangles.
A stretch on side businesses, CEO turnover speculation, and a rambling college food-co-op story produces no material takeaways; plugs for the forecasting-contest waitlist and the branded merchandise store are acknowledged as pure marketing. The show closes with a numeric market wrap: equities and gold rallying off the lows, silver off its highs, bonds and the dollar weaker.
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.
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.