Use AI to make product decisions - Better with Kent | Lyssna här

Most people use agents to write code. Watch Kent use one to decide what to build: gather evidence, argue primitives, peel cleanup into side quests, keep the judgment - and only then type go.

(00:00) - Cold open: I think we are aligned, so let's go
(00:05) - Better with Kent intro
(00:24) - The durable skill: making a product decision with your agent
(00:31) - Start at the top: hand the agent the Agents Week post
(01:11) - Your agent needs a computer, not a container
(02:49) - Agent TLDR: opportunities and a workspace assistant primitive
(03:47) - How Kody repo sessions work today
(05:32) - Will King: use agents to gather, keep the judgment
(06:17) - Built-in primitive or community package?
(06:27) - Primitives are hard to remove once you add them
(07:37) - Entitlements, cost, and whether the business survives it
(09:16) - Ask for real usage data, not speculation
(10:38) - Push back when the data is wrong
(11:05) - Side quests: spawn other agents so the thread stays on the decision
(12:30) - A gap can mean expanding a primitive, not adding one
(13:34) - Durable objects vs R2: expertise that saved 13x
(15:17) - Catching the agent being sloppy
(15:47) - Artifacts is the better backing primitive
(17:39) - Least surprise is a product principle too
(18:08) - Research: large files in Cloudflare Artifacts (30 MB, 413s, no LFS)
(19:39) - Price-conscious prompts make price-conscious agents
(20:22) - The call: one repo primitive with a package marker
(21:10) - Progressive disclosure, then go
(21:52) - Why almost no skills for this conversation
(22:20) - Homework: ask for one research deliverable
(23:12) - Close: get better together

Better with Kent - durable skills for people who ship software.

A Cursor cloud agent is sitting mid-conversation and the next thing Kent types is one word: go. Before that, there is a whole product conversation worth watching - because none of it was "write the feature."

Cloudflare Agents Week drops @cloudflare/computer, and the real question is not "can we build it" but "what should Kody's primitives be?" Kent walks the actual thread: asking the agent to gather evidence instead of implementing, pushing back when the data is wrong, measuring the large-file ceiling in Cloudflare Artifacts (about 30 MB, 413s, no LFS), catching a durable-object storage choice that would have cost 13x more than R2, and spawning side-quest agents so surfaced tech debt never hijacks the decision thread.

The call that comes out of it: no new data-repo primitive - expand the repo primitive with a package marker, gate large files with a friendly redirect instead of an opaque rewrite, and respect the principle of least surprise as a product principle, not just a programming one.

Homework: before your next "build it," ask your agent for one research deliverable that could change your mind. If it surfaces cleanup, spawn a side quest. Then say go.

Links

Rss