Share

AI News & Strategy Daily with Nate B. Jones
Daily AI strategy and news for the AI curious.
Latest episode

Claude Opus 5.5 Review: Easier to Steer, Fewer Tokens
24:32|For deeper playbooks and analysis: https://natesnewsletter.substack.com/What does an AI task actually cost when you count the whole job? Nate examines his Opus 5.5 LEGO build, the difference between API pricing and a subscription allowance, and why fewer retries can matter as much as the price per token.He also explores writing that preserves your intent, clearer stopping conditions for overnight work, and a practical way to rerun your own assignments when a new model arrives.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.
More episodes
View all episodes

An AI assistant added up my subscriptions: $5,350 a year. The prompt guide to get your own list in about 20 minutes.
31:16|For deeper playbooks and analysis: https://natesnewsletter.substack.com/What makes a consumer AI assistant useful enough for people to return to it? Nate examines Meta’s Muse, the everyday work it can take off people’s plates, and what its conflict with Amazon reveals about attention and commerce.Finding recurring costs and acting on subscriptions.Making complex AI work feel simple.Why the shopping journey matters to Amazon and retailers.How personal context can shape competition between assistants.Nate’s savings figures describe future spending avoided, not a cash refund. Other users’ insurance savings are self-reported. The subscription-revenue findings concern an inattention model.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.
How to Scale AI Developer Productivity Across a Team
32:56|For deeper playbooks and analysis: https://natesnewsletter.substack.com/What helps a team turn faster AI coding into useful work that actually ships? Nate examines the setup behind Lauren Tan’s self-reported pull-request volume and six principles teams can apply to their own agents.Share useful agent work across the team.Preserve history outside a temporary chat.Keep humans accountable and give agents reliable checks.Leave clear handoffs for the next session.Remove process that no longer helps.The goal is to improve the systems around the agents so more people can ship valuable work.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.
NVIDIA World Models Explained: What Developers Can Build
46:26|For deeper playbooks and analysis: https://natesnewsletter.substack.com/What does a world model actually do—and why might a robot learn to fold your laundry before it can make perfect scrambled eggs?Nate sits down with Ming-Yu Liu, VP of Cosmos Lab at NVIDIA, to explore how world models turn observations into predictions and physical actions. They discuss where the analogy to language models helps, where it breaks down, and why knowing whether an action worked can be harder than generating the action itself.How simulation lets builders test many kitchens and situations before returning to a real robot.Why robots in the field face different timing and compute constraints from services in a data center.What researchers can—and cannot—conclude about a model’s understanding of physics.How verifiable results change the pace of learning, from folding laundry to judging food.For builders and operators, this conversation connects the models to the practical questions: what can be tested, what must happen immediately, and where human judgment is still needed.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.
AI-Native Workplace: What Real AI Adoption Asks of You
42:28|For deeper playbooks and analysis: https://natesnewsletter.substack.com/What changes when AI can work across your computer instead of waiting for you to move information between apps?Nate sits down with Andrew and Akshay at OpenAI to explore how AI is changing their own work: where adoption takes hold, what makes useful context available, and what people do when the busy work starts to disappear.In this conversation:How access to the right context can change who uses AI at work.What it means to share a computer with an agent.Why voice input and written output solve different problems.How orchestration, experimentation, and human judgment fit together.What a tax-error discovery reveals about useful automation.For builders and operators, the discussion brings the focus back to everyday work: which tasks to hand over, which decisions still need attention, and how to recognize when a tool is actually helping.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.
You cannot tell which parts of your software should stop calling an LLM. My Jev guide has a prompt that scans your projects and names them.
33:01|For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when a model can read a complicated input but only choose among answers you supply?Nate explains why Jev's general-purpose classification could change where intelligence appears in software. He walks through support routing, tax documents, research prioritization, agent orchestration, and spreadsheets that respond to meaning.Why complicated inputs and simple outputs define a useful class of problems.How classifiers, generative models, and ordinary code fit together.What lower classification costs make possible for teams and individual builders.Where testing still matters, and how to try Jev with a coding agent.For builders and operators, the opportunity is to revisit decisions that were previously too expensive to automate—and test what happens when those decisions become cheap enough to use throughout a workflow.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.
AI Cost to Serve: Which Customers You Can Now Afford
30:56|What happens to your AI bill when agents improve and more people start using them? Nate draws on his conversations at Dreamforce to examine the cost of wider adoption, the work agents can make affordable, and the decisions that change cost per successful result.The discussion covers redesigning workflows, routing routine work to cheaper models, matching an agent’s surrounding software to its capabilities, and evaluating results before scaling up.More analysis and practical playbooks: https://natesnewsletter.substack.com/Editorial note: Draft podcast copy; current Acast house format has not been independently confirmed. No chapters included.