--- schema: 1 type: video title: >- Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref. description: >- A newsletter writer walked Matt Dailey through an agentic pipeline good enough to amplify their own voice instead of flattening it, then mentioned they were now effectively writing a book every week. Dailey asked whether the audience was reading a book every week. They were not. Those pages go unread, and that gap is what he calls velocity sickness: the stress of a sudden output increase that delivers output without impact. On engineering teams it arrives as too many pull requests to merge, work sprinting in too many directions at once, and the ritual of declaring agent bankruptcy, walking back to twelve terminals the next morning, recognizing none of it, throwing all of it out and paying for the same work twice. The failure that actually worries him is critical decisions getting made by agents, because an engineer who lets that happen has stopped owning the code, and a team doing it at scale no longer owns the product. His fix is to separate the decision layer from the implementation layer and give the decision layer its own primitive: a document rather than a chat. Chats are isolated, ephemeral and built for implementation, so the decisions made inside one evaporate while only the code survives. A durable shared doc holds the state and the agent supplies the action, which keeps agents effectively stateless, lets several start from identical context, and turns rebuilding your own understanding into rereading a file. The tell that it is working, he says, is people writing plans they never implement, which is what prioritizing looks like once idea velocity replaces code velocity. Three things to try immediately: notice which gear you are in, treat the plan as a portal into the system rather than a prompt, and hand a plan to a teammate before you hand it to an agent. Speaker info: - https://www.linkedin.com/in/matthewjdailey - https://ref.tools/ --- Watch along with the corrected transcript, summary, timestamps and resources on this talk's official AIE page: https://ai.engineer/talks/Kz4QJmNrVXU-velocity-sickness-what-happens-when-your-whole-team-gets-10x-faster Join our upcoming AI Engineer conferences (see https://ai.engineer landing page): - AIEi Shanghai, November 5–6 — the first for meeting top Chinese labs and engineers - AIE CODE in SF, November 10–12 — the top AI Coding conference returns - AIEi Sydney, December 7–8 — the first AIEi run alongside NeurIPS 2026 in Sydney --- canonical: >- https://liquidgold.cc/channel/aidotengineer/explore/video/velocity-sickness-what-happens-when-your-whole-team-5c5cb9527a5f markdown: >- https://liquidgold.cc/channel/aidotengineer/video/velocity-sickness-what-happens-when-your-whole-team-5c5cb9527a5f.md llms: null parent: 'https://liquidgold.cc/channel/aidotengineer.md' channel: aidotengineer updated: '2026-10-24T05:46:37.462Z' language: null children: [] videoId: Kz4QJmNrVXU durationSeconds: 1237 publishedAt: '2026-08-09T16:30:28.000Z' searchChunks: - ordinal: 0 text: null startSeconds: 23 endSeconds: 112 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=23' heldReason: rights - ordinal: 1 text: null startSeconds: 123 endSeconds: 254 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=123' heldReason: rights - ordinal: 2 text: null startSeconds: 123 endSeconds: 254 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=123' heldReason: rights - ordinal: 3 text: null startSeconds: 123 endSeconds: 254 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=123' heldReason: rights - ordinal: 4 text: null startSeconds: 123 endSeconds: 254 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=123' heldReason: rights - ordinal: 5 text: null startSeconds: 266 endSeconds: 356 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=266' heldReason: rights - ordinal: 6 text: null startSeconds: 366 endSeconds: 465 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=366' heldReason: rights - ordinal: 7 text: null startSeconds: 476 endSeconds: 561 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=476' heldReason: rights - ordinal: 8 text: null startSeconds: 572 endSeconds: 672 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=572' heldReason: rights - ordinal: 9 text: null startSeconds: 572 endSeconds: 672 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=572' heldReason: rights - ordinal: 10 text: null startSeconds: 682 endSeconds: 785 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=682' heldReason: rights - ordinal: 11 text: null startSeconds: 796 endSeconds: 918 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=796' heldReason: rights - ordinal: 12 text: null startSeconds: 796 endSeconds: 918 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=796' heldReason: rights - ordinal: 13 text: null startSeconds: 929 endSeconds: 1014 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=929' heldReason: rights - ordinal: 14 text: null startSeconds: 1025 endSeconds: 1115 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=1025' heldReason: rights - ordinal: 15 text: null startSeconds: 1126 endSeconds: 1237 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=1126' heldReason: rights - ordinal: 16 text: null startSeconds: 1126 endSeconds: 1237 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=1126' heldReason: rights - ordinal: 17 text: null startSeconds: 1126 endSeconds: 1237 watch: 'https://liquidgold.cc/watch/Kz4QJmNrVXU?t=1126' heldReason: rights --- # Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref. A newsletter writer walked Matt Dailey through an agentic pipeline good enough to amplify their own voice instead of flattening it, then mentioned they were now effectively writing a book every week. Dailey asked whether the audience was reading a book every week. They were not. Those pages go unread, and that gap is what he calls velocity sickness: the stress of a sudden output increase that delivers output without impact. On engineering teams it arrives as too many pull requests to merge, work sprinting in too many directions at once, and the ritual of declaring agent bankruptcy, walking back to twelve terminals the next morning, recognizing none of it, throwing all of it out and paying for the same work twice. The failure that actually worries him is critical decisions getting made by agents, because an engineer who lets that happen has stopped owning the code, and a team doing it at scale no longer owns the product. His fix is to separate the decision layer from the implementation layer and give the decision layer its own primitive: a document rather than a chat. Chats are isolated, ephemeral and built for implementation, so the decisions made inside one evaporate while only the code survives. A durable shared doc holds the state and the agent supplies the action, which keeps agents effectively stateless, lets several start from identical context, and turns rebuilding your own understanding into rereading a file. The tell that it is working, he says, is people writing plans they never implement, which is what prioritizing looks like once idea velocity replaces code velocity. Three things to try immediately: notice which gear you are in, treat the plan as a portal into the system rather than a prompt, and hand a plan to a teammate before you hand it to an agent. Speaker info: - https://www.linkedin.com/in/matthewjdailey - https://ref.tools/ --- Watch along with the corrected transcript, summary, timestamps and resources on this talk's official AIE page: https://ai.engineer/talks/Kz4QJmNrVXU-velocity-sickness-what-happens-when-your-whole-team-gets-10x-faster Join our upcoming AI Engineer conferences (see https://ai.engineer landing page): - AIEi Shanghai, November 5–6 — the first for meeting top Chinese labs and engineers - AIE CODE in SF, November 10–12 — the top AI Coding conference returns - AIEi Sydney, December 7–8 — the first AIEi run alongside NeurIPS 2026 in Sydney --- Canonical: https://liquidgold.cc/channel/aidotengineer/explore/video/velocity-sickness-what-happens-when-your-whole-team-5c5cb9527a5f · Channel: [AI Engineer](https://liquidgold.cc/channel/aidotengineer.md) > Search chunk text is held until public-source provenance is verified. ## Document chunks > Missing: no stored document chunks are available.