Rethinking Agent Harnesses, Live Software, and Token Economics
From State of Agentic Coding - Series
Armin Ronacher · Source dated 16 Oct 2026
New to this library, not necessarily new to the world.
From State of Agentic Coding - Series
Armin Ronacher · Source dated 16 Oct 2026
Time To Program explains server-side sessions, JWT validation and revocation, OAuth delegated authorization, and OpenID Connect login through web, mobile, and multi-service scenarios. A practical introduction to choosing and combining these mechanisms, not a complete protocol implementation guide.
Time To Program · Source dated 12 Oct 2026
Thorsten Ball demonstrates his Amp workflow: batch alternatives instead of waiting on agents, request end-to-end evidence before reviewing critical code, make development and production tools discoverable, and evaluate repository instructions in fresh environments. Includes rollout monitoring and a feature-flagged memory-warning case study. Amp-team experience and product demonstrations, not controlled productivity or safety findings.
Amp, Inc. · Source dated 13 Oct 2026
Salvatore Sanfilippo contrasts his positive early impressions of Gemini 4 Argon's document understanding and concise writing with skepticism about Muse Wonder's benchmark claims. Italian-language opinion commentary, not a controlled model comparison. The summary separates his assessments from Google's documented shared token budget and introductory pricing.
Salvatore Sanfilippo · Source dated 14 Oct 2026
Logan Kilpatrick and Google's product and research team discuss Argon's writing feedback, agents assisting model development, engineering use cases, long-decode reasoning, and balancing persistence with clarification. They recommend scrutinizing and iterating on outputs. A first-party launch conversation with internal anecdotes, not independent evidence of reliability or autonomous self-improvement.
Google for Developers · Source dated 14 Oct 2026
Salvatore Sanfilippo describes retaining creative involvement through detailed product decisions, asking agents to announce significant steps, and using observed display behavior to steer changes. He distinguishes reducing idle time with parallel projects from preserving flow, and cautions against making automation more stressful. Personal experience and advice, not measured productivity findings; summarized in English from Italian auto-generated captions.
Salvatore Sanfilippo · Source dated 13 Oct 2026
Tibo Sottiaux discusses OpenAI's direction for persistent assistants, changing multi-agent workflows, plugin discovery and revenue sharing, and agents that connect to multiple devices. His production-alert anecdote distinguishes useful awareness from authority to repair systems, while his monitoring discussion describes a safety approach rather than proven guarantees. A first-party product and engineering interview with forecasts about agent-driven internet traffic.
Lenny's Podcast · Source dated 4 Oct 2026
Bill Gates and Ezra Klein discuss AI-enabled cyber and biological threats, job displacement, government oversight, and whether AI will reduce or deepen inequality. Gates's risk assessments and policy proposals are attributed views, not established forecasts or demonstrated safety guarantees.
The Ezra Klein Show · Source dated 29 Sept 2026
Salvatore Sanfilippo explains his AI-assisted CAD workflow: investigate representation and algorithms, build a small prototype, steer interaction and performance, and give the agent screenshot-based checks. He argues for tools usable by both people and agents. Based on Italian auto-generated captions, summarized in English; development time and project outcomes are personal reports, while predictions about AI and design remain forecasts.
Salvatore Sanfilippo · Source dated 7 Oct 2026
Salvatore Sanfilippo explores a suggestion he attributes to DHH: generating code with LLMs may reduce attachment to a particular implementation and make teams more willing to replace it. He distinguishes ownership of a project's design from attachment to its code. A psychological hypothesis from a mostly solo developer, not measured team outcomes; based on Italian auto-generated captions, summarized in English.
Salvatore Sanfilippo · Source dated 8 Oct 2026
Mario Zechner and Armin Ronacher explain Pi Durable through persisted task intent, effect execution, saved results, and versioned application documents. They discuss why external actions still need safe retry semantics, where human architecture work remains useful, and why shared agent interfaces introduce browser-side trust problems. A first-party design discussion, not an independent reliability test.
0xSero · Source dated 7 Oct 2026
Gergely Orosz surveys parallel agents, migrations, smaller projects, review overload, and cloud harnesses while arguing that teams, planning, testing, and learning remain essential. Based on English auto-generated captions; company practices and platform data are his reporting, broad adoption claims are not a representative industry survey, and future workflow changes are forecasts.
The Pragmatic Engineer · Source dated 6 Oct 2026
Laurie Voss argues that agent-generated code shifts the bottleneck from writing to verification. He surveys automated reviewers and proposes codifying team context and merge criteria in review harnesses, while retaining human judgment for high-risk or poorly specified changes. Based on English auto-generated captions; study figures and vendor outcomes are reported by the speaker, not independently verified here.
AI Engineer · Source dated 30 Sept 2026
A panel debate on risk-based code review, architectural learning through cheaper experiments, engineering ownership, and distribution when software is easier to build. The speakers disagree about how much agents change established practice. Practitioner accounts and forecasts, not measured productivity results; summarized in English from French auto-generated captions.
Convex · Source dated 8 Oct 2026
Simon Willison surveys 2026 through coding agents, personal agents, local models, software factories, and reported training-time security incidents. He argues that stronger agents shift engineering effort toward goals, constraints, verification, and product judgment. His demonstrations and capability assessments are personal observations; incident accounts are attributed reports, not independently verified here.
WeAreDevelopers · Source dated 21 Sept 2026
Robert Martin tells Aviator's Ankur Jain why he abandoned an elaborate multi-agent pipeline while retaining unit tests, complexity-and-coverage checks, mutation testing, and human sign-off. He describes inspecting architecture through an agent-linked diagram tool instead of routinely reading code. Based on English auto-generated captions; workflow benefits are personal observations, and claims about replacing code review or shrinking teams are hypotheses rather than validated team outcomes.
Aviator · Source dated 24 Sept 2026
Kent Beck argues for alternating feature delivery with refactoring and learning to preserve future options. He discusses generated-code verification, one-shot versus iterative development, and measuring mission outcomes rather than code volume. Based on English auto-generated captions; project experiences and critiques are practitioner observations, not controlled productivity or reliability findings.
Rise8 · Source dated 29 Sept 2026
Matt Pocock proposes stronger behavioral tests, deep modules, a separate standards-review agent, and human review based on reversibility and blast radius. His Retro skill suggests automated checks and team-standard updates from review feedback. Practitioner advice, not measured productivity findings; based on an English transcript with an early gap and unverified caption kind, from an upload labelled bad audio.
AI Engineer · Source dated 25 Sept 2026
Zach Lloyd proposes software factories that coordinate agents across triage, specs, implementation, review, verification, and monitoring. Drawing on Warp's open-source workflow, he describes human checkpoints and observer agents that improve skills from feedback. Based on English auto-generated captions; the factory model and career predictions are recommendations and forecasts, not measured productivity or reliability findings.
AI Engineer · Source dated 27 Sept 2026
Benedict Evans argues that AI makes tools easier to build without resolving which problems to solve, how shared workflows should change, or who takes responsibility for them. He explains the movement between improvised spreadsheets and institutionalized software, then separates deployment choices from operational change and competitive strategy. An analytical essay using examples and historical analogies, not a measured study of enterprise AI outcomes.
Benedict Evans · Source dated 3 Sept 2026