Topic
Durable Execution
8 episodes
-
Andrew Ng 4 agentic steps "from Loops to Graphs from scartch"
Andrew Ng's four-step framework maps agentic design from simple loops (Reflection, Tool Use) through chains (Planning) to graphs (Multi-Agent Collaboration). The central claim: architecture beats model selection—GPT-3.5 in a reflective workflow hits 95.1% on HumanEval vs. GPT-4 zero-shot at 67%. Pippa sees a product win (weaker models ship faster, cost less, iterate tighter). Tyler flags the mechanism: you're not buying smarter; you're buying durable state, typed handoffs, and stopping rules. Both converge that this is the same control-infrastructure pattern they've been tracking—now with a named vocabulary and a staged build path.
-
Overview: Durable Execution
We’re finally slowing down and unpacking durable execution from the ground up, because it keeps showing up in our conversations and it actually deserves the full treatment. We’re using the book-with-bookmarks idea to make the mechanics of checkpoints, retries, and recovery click without hand-waving.
-
Overview: Append Only Logging
We’re finally making append-only logging click, because it keeps sneaking into the stuff we cover and we keep assuming everybody sees the mechanism already. We walk from the basic idea to why it gives AI systems a durable, auditable trail, and where that trade-off starts to bite.
-
Overview: State Serialization
We finally slow down and explain state serialization from the ground up: what it is, why it matters, and how it lets an AI pause, resume, and hand off work without losing the thread. We keep it in our own voice and stay close to the actual mechanism, because state serialization is one of those ideas we keep circling for a reason.
-
Kwc2SSaP0y
Buzz argues that the workspace for software teams should treat people, agents, messages, workflows, and code as parts of one shared system. Cooper likes the product shape, while Miles argues the hard part is whether signed events and self-hosting produce usable coordination rather than another fragmented collaboration stack.
-
Agentic orchestration: Enterprise AI organizations have a deployment problem, not a platform problem — and most are calling chatbots agents
Cooper and Miles dig into VentureBeat’s claim that enterprise AI has a deployment problem, not a platform problem. They land on the gap between what companies say they want from agents and what they’ve actually shipped, with Miles probing the survey’s limits and Cooper focusing on what matters operationally once finance, security, and reliability show up.
-
Why every AI agent decision needs a receipt
Two hosts dig into the case for giving every AI agent action a receipt: not because logs are fashionable, but because verification is the only way to know what happened, what failed, and what to trust. They stay skeptical about overgeneralizing, but land on a practical view that evidence packets matter most where agent decisions touch code, runtime, or anything expensive to undo.
-
What we’ve learned building cloud agents · Cursor
Laura and Harper unpack Cursor's cloud agent engineering lessons — why the dev environment IS the product, how durable execution via Temporal unlocked real reliability, and why the harness is shifting from deterministic control to giving agents tools to self-heal.