Dave and Dan pull back the curtain on the autonomous coding agent they built — an agent that lives in the cloud, takes instructions in Slack, and runs a full plan-to-deploy pipeline 24/7. In the last seven days alone, their agents opened 85 pull requests. They walk through exactly how the system works and why "build the system" beats "write the code."

Key Topics

• Talk to your agent in Slack — an agent that lives in the cloud, writes code, and runs around the clock.
• 85 PRs in a week — the metric that frames the whole episode, and what it says about building systems over writing code.
• Brainstorm → PRD → Plan → Tasks — the interactive front of the pipeline, where the human stays in the loop.
• The four crons — dev task, review, patch, and deploy fire every 30 minutes and only burn tokens when there's real work pending.
• Right-sized tasks — why a 1,000-line PR fails and how the plan session breaks work into manageable, one-commit-sized tickets.
• Mandatory canary deploys — merge to main, canary, promote to prod, with automatic rollback and Slack alerts when telemetry looks wrong.
• Everything is metered — PostHog metrics on every step, used to wake up to "what did the agents do overnight?" and to keep improving the system.

Notable Quotes

• "We said it a million times — you don't need to code anymore if you build a system. So we built a system."
• "You're gonna flip your laptop open on Monday morning and there's 24 PRs — all done, all passing green, all ready to be reviewed and deployed."
• "If you build the right system, not only do you not need to code — you don't even need to watch your deploys."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

If AI handles the coding, then being an engineer means planning and reviewing — the work of staff and principal engineers. But that breaks the career ladder: how does anyone become senior when the junior rungs disappear? Dave and Dan dig into where senior engineers come from now, why juniors still add value on top of Claude, builders versus maintainers, and how interviewing changes when anyone can vibe-code.

Key Topics

• The vanishing junior rung — if seniority is "planning and reviewing," how do you climb without junior work to learn from?
• Adding value on top of Claude — good juniors ship more complete PRs than Claude alone, and compress a 5–10 year career into a couple of years.
• Builders vs. maintainers — the "commandos and palace guards" framing, reimagined: builders extend the system, maintainers keep the harness healthy.
• Claude is no longer a junior — with the right harness it plans, tests, lints, simplifies, and reviews like a solid mid-level or senior engineer.
• Robots ship, humans plan — the autonomous agents do the shipping 24/7; the builder's thrill now comes from queuing tasks, not typing code.
• Interviewing in the agentic era — show what you built with Claude, then show the system you built to build it. Anyone can vibe-code; the differentiator is the system.

Notable Quotes

• "Right now, as of May 2026, if you're writing code, you shouldn't be. You're doing something wrong."
• "Anyone can vibe code anything nowadays — but the differentiator is, did you build a system to build it?"
• "You and I aren't shipping anything. Our autonomous coding robots that live in the cloud and work 24 hours a day, they're the ones actually shipping."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan get candid about the most uncomfortable question in software right now: is my career still safe? Dan recounts a literal "therapy session with Claude" that exposed his 20-year sense of job security as a false one — and the two work through what to actually do about it. The throughline: AI isn't ending engineering, it's reshaping it, and the people who refuse to engage are quietly opting themselves out.

Key Topics

• The career-identity crisis — "Am I gonna be a waiter a year from now?" and why even all-in AI users feel it
• False security — how a 20-year "solid foundation" got disrupted, and the story your brain still tells you
• From DevOps engineer to "Claude Code something" — losing and rebuilding a professional identity
• Self-selecting out — why opting out of AI tooling is opting out of a career
• Layoffs vs. AI — separating balance-sheet cuts from the real AI signal, and why AI-forward companies are hiring
• The advice for every developer in May 2026: embrace change, go all in, and go build the side projects you never could

Notable Quotes

• "If you're choosing to not use Claude Code, you are self-selecting yourself out of a career at this point."
• "Stability in my career feels like it might be crumbling underneath my feet — and Claude told me that was a false sense of security all along."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Org-wide AI transformation keeps failing — not because the tech doesn't work, but because trying to move 200 engineers at once turns into a slog. Dave and Dan break down what they see in the field: tool sprawl, the very real fear engineers feel about being the ones disrupted, and the trap of tripling your Claude bill without shipping any faster. Their fix: skip the org-wide rollout, embed a small tiger team on your most important product, and build a system the rest of the company can adopt later.

Key Topics

• Why moving the whole org is too slow — and why a small embedded team builds momentum faster
• Tool sprawl: pick one (Claude Code) instead of juggling Copilot, Codex, Cursor, and a now-canceled Gemini CLI
• The fear factor — engineers wired for change now find themselves the target of disruption
• The bill-tripled-but-no-faster trap as a clear signal AI adoption has failed
• Flattening the org: top-heavy management and bureaucratic gates slow speed AI should unlock
• "If you're still writing code, you're a dinosaur" — the shift from writing code to planning, reviewing, and mentoring the system

Notable Quotes

• "Listen, CEOs and CTOs, if your developers are still writing code, you're behind the curve. They should not be writing code."
• "We doubled our bill, but we're not shipping faster — that's a symptom that your org-wide AI adoption has failed."
• "Don't try to move the whole org. Get in with a small team and see things move fast."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Anthropic is taking the gloves off. The VC-subsidized era of essentially-free AI agents is ending: OAuth tokens lose Open Cloud coverage, Claude Code Max plans are getting throttled for autonomous workloads, and Dave & Dan are staring at a $200/mo → $1,000+/mo jump for their ShipRight background agents. The episode is a candid talk about what changed, why it was inevitable (the Uber-pricing parallel), and the operator choices ahead: optimize aggressively, gate non-deterministic crons, mix cheaper models for execution, or just eat the cost as a line item.

Key Topics

• What changed: OAuth/Open Cloud coverage cut, autonomous-coding workloads pushed toward per-token API pricing
• The numbers: $200/mo plan vs ~$1,000–$5,000/mo if the same work ran on API tokens (at least 10×)
• Why this was inevitable — the Uber bridge-toll parallel: VC subsidies don't last forever
• Operator optimization moves: gate crons behind deterministic checks, split planning vs execution across models, tighten permissions on always-on laptops
• Phone-as-prompter workflow: Caffeinate-running laptop + mobile Claude as the in-the-loop interface, OAuth-covered
• Why we're staying with Claude: ecosystem (skills, plugins, MCP) still beats Codex even if pricing changes
• What this means strategically: AI economics are about to look like real economics — plan accordingly

Notable Quotes

• "We're seeing this happen with Anthropic right now. They're taking the gloves off. They're pulling out the subsidies."
• "$200 a month, if you're paying API tokens, would be like $5,000."
• "This is gonna force some of us to be a little bit more conservative about how we use AI."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan dig into service readiness — the industry calls it "harness engineering" — and why testing just moved to the #1 spot of their 13 repo-readiness pillars. Before you let agents ship code in the background, the question isn't 90% coverage; it's whether anyone actually trusts the tests. They walk through the onboarding plugin that gets a repo test-ready and how test decisions get baked into the agent's planning phase instead of left to human best-effort.

Key Topics

• Why "no one has confidence in the tests" is universal — slow, flaky, and thin coverage everywhere
• Testing as pillar #1 of 13 for agentic-engineering readiness ("phase zero")
• The test-onboarding plugin: research versions → design the greenfield ideal → reconcile what to keep vs. throw out → a reviewed task list
• All four layers in scope: unit, integration, end-to-end, smoke — plus migrations, seeds, and integrations
• Baking "which tests does this need?" into the agent's planning phase rather than relying on a human to remember
• Coverage dogma vs. reality: test what matters, but keep 90% in CI as the practical proxy
• The daily cron that catches coverage gaps and staleness; local-first test execution for agents

Notable Quotes

• "Every organization we've pretty much ever worked for — no one has confidence in the test. The tests are slow, the tests are flaky, and they don't cover enough stuff."
• "How do you know that you can trust your agent to ship code that's gonna work?"
• "We said 90% coverage — great philosophy. Three months later we realized maybe the 10% is the one that matters."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan announce a reshaping of their AI adoption work: org-wide SDLC transformation over three months wasn't moving the needle, so they're switching to embedding in a single team — even a single repo — and unleashing agents on a big, important project. The episode doubles as free advice to engineering leaders: stop doing AI at 20%, pick one project, and crush it.

Key Topics

• Why the org-wide "evaluate your whole SDLC" model under-delivered in three months
• The new model: embed in one team, one project, one repo — and ship a big migration/rewrite fast
• Coding is becoming the dinosaur skill; planning, reviewing, and sanity-checking keep humans in the loop
• Why staff/principal engineers map most naturally onto the agent-orchestration role
• The leader's playbook: cut the roadmap, take a handful of your best people, focus for one quarter
• Build the system while you ship — then force the rest of the org to adopt it
• Why five-person companies disrupt giants, and why that's even more true with AI

Notable Quotes

• "If you're just writing code and then waiting for somebody else to review your stuff, and then you deploy it — that's going away. That's solved by AI agents already."
• "Take a handful of your best people, only focus on this, and by the end of three months you're gonna be like, 'Holy cow.'"
• "You're building a system. That system will work for any other project you have."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan look three months down the road: autonomous coding went from "watch every line" to "Claude is basically an employee" in six weeks. They share their Anthropic wishlist, the hygiene automations that get teams onto the autonomy ladder, and the one piece of advice every executive keeps ignoring.

Key Topics

• From watching Claude write code to planning and reviewing only — what changed in three months
• The Anthropic wishlist: long-term memory in Claude Code Mobile, more voice integration
• Hygiene automation as the on-ramp: auto-updating docs, READMEs, and code coverage on a weekly cadence
• The big-AI money moves — valuations, data-center deals, and the Cursor option
• Why "we have trouble keeping up" — and why staying ahead of clients is easier than it feels
• The core exec argument: dedicate your best people full-bore for three months instead of a 20% slow burn

Notable Quotes

• "Take a handful of your best people, dedicate them for three months to only work on this, and you're gonna be so much better off than the slow burn."
• "Claude is basically an employee for us now."
• "It doesn't just happen by typing in questions to ChatGPT. You've gotta actually build a system and invest in the system if you wanna move fast."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan riff on how they used Claude Code to build the entire AppVitals business — marketing site, internal SaaS replacements, time tracking, invoicing, even this podcast — and ask why non-technical entrepreneurs are out-adopting professional engineers on agentic tooling.

Key Topics

• The three tiers of AppVitals — AI adoption work, project work, and an autonomous coding product for non-technical users
• Deleting the SaaS stack — replacing four paid platforms with their own Claude Code-built tools
• Inside Vitals OS — accounts, calendar, time tracking, billing, invoicing, and partner pay-outs all automated
• Why this podcast only exists because publishing is one Claude Code command (with help from Sully)
• The engineer-vs-entrepreneur gap in AI adoption — and what it says about curiosity as the unlock
• AI as amplifier — it magnifies strengths and weaknesses, so the gaps you ignore today become the gaps that bite you tomorrow

Notable Quotes

• "We deleted all of our SaaS platforms that we were paying for. And we rebuilt them with Claude Code because we can now."
• "This is the age when the curious people are going to crush it. Because if you're not curious, then you're not using these tools."
• "If recording this podcast and publishing it required work on my part, we wouldn't be doing it."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

The Velocity Lab's first-ever guest interview. Dave and Dan sit down with Brian Jones (Tahoe Digital), a non-technical founder who has built multiple AI-native businesses without writing a single line of code. He walks through his evolution from ChatGPT and Microsoft Notepad to Replit, Cursor, and now Claude Code — and shares why curiosity and persistence are now the only credentials that matter.

Key Topics

• Why a non-technical entrepreneur is shipping faster than most engineering teams
• The toolchain evolution: ChatGPT plus Notepad to Replit to Cursor to Claude Code, and what broke at each stage
• Building a system: orchestrating Claude across 94 tasks to fix local-business search presence
• The 10x multiplier — running a one-person agency that would have required ten people two years ago
• Why senior engineers hedge on AI while vibe-coders charge ahead: expertise as a tax on speed
• Learning loops in practice: how 6,000 pieces of user feedback shaped a game tutorial business
• "We don't need junior developers anymore" — and what humans still need to do
• The last 5%: where autonomous coding agents stall and operators take over

Notable Quotes

• "Stop looking at the things that it's fucking up — and start looking at the things that it's doing right."
• "I can fly now. Imagine if right now you just learned you could fly. What would you be doing all day long?"
• "This is the age when the curious will succeed."
• "I have never worked harder in my life. I'm waking up at three in the morning because I'm so excited." — Brian Jones
• "Take the red pill."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Engineering leaders have been sitting on the same migrations for years — monolith to microservices, ORM rewrites, framework upgrades — because the cost of doing them was always 50% of the engineering org for a year. Claude makes those migrations feasible. But not as a single 12,000-line PR. Dan and Dave break down the method that turns a five-year migration into a three-month migration with a skill, a cron job, and a learning loop.

Key Topics

• The anti-pattern: 12,000- to 100,000-line migration PRs. Tempting with Claude, but the absolute wrong way
• The method: pick a small piece, do the first migration with Claude in the loop, then have Claude write a skill from what you learned
• Run the skill on a cron — Claude opens one small migration PR a day while you ship product code
• Why the engineering fundamentals haven't changed: testing infrastructure, shadow reads/writes, upfront planning are still required
• Adding a learning loop so every cron run gets smarter — each PR is less rocky than the last
• Who this is for: engineering leaders, product leaders, and CEOs staring at tech debt they've been avoiding for years

Notable Quotes

• "30,000, 50,000, a hundred thousand line PRs are not the answer."
• "Your three-year migration is now a six-month or a three-month migration. And the most important thing is — you're not spending any time on it."
• "All the core engineering principles that you've already learned are still super, super valuable."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Generic AI PR review agents from Copilot, Gemini, and Claude are a baseline, not a finish line. Dan and Dave break down the five things senior engineers actually look for in a PR — and why a custom review skill catches issues that the stock agents miss.

Key Topics

• The "V zero" problem — why generic GitHub PR review agents only get you so far
• Five things senior engineers want surfaced first: what+why, views/APIs changed, business logic, breaking changes, and concerns from the standard review
• Stale PR titles and bodies — Claude rarely updates them across iterations unless you force it
• Breaking changes at the API and database layer: not minor outages, 100% outages
• How agentic coding goes sideways — random indexes, drive-by event systems, features Claude assumes you'll need
• Why posting inline review comments is the underrated capability most generic agents skip

Notable Quotes

• "Having a generic PR review agent is not as valuable as one that's custom for your company."
• "It's not like a minor outage, it's a hundred percent outage if you mess that up."
• "Claude has a lot of agency. It'll just go add features that it assumes you'll need in the future."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

AI transformation isn't a tooling problem. It's an organizational one. Dave and Dan dig into why bringing in AI without cutting bureaucracy, top-down processes, and the people who create them just gets you the same speed with new tools — and what to actually change so builders can build.

Key Topics

• Why technical adoption alone won't make your engineering org faster
• How processes, architecture committees, and "trust theater" silently kill velocity
• Builders vs maintainers — when to prune, and why "palace guards" are a real role to retire
• The honest test: ask your top performers what it would take to 2x — then act on the answer
• Speeding up the upstream too: product, design, security, sales — same playbook
• Why ownership and sideways accountability beat top-down hierarchies for moving fast

Notable Quotes

• "As an engineering manager, your main job is to get the hell out of their way and let the builders build."
• "You have palace guards who look good and protect everything. They don't really do much. And you have commanders who go out there and kick ass."
• "Move fast and build things — you can actually build quickly if you have the right system in place."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan walk through the questions a board or executive will ask about AI — from inventory and tooling to ROI, accountability, and competitive risk — and what answers actually hold up. Pro tip: if you can't answer them, your competitors probably can.

Key Topics

• Do we have an inventory of where AI is operating in the company? — most orgs can't answer this
• The scattershot tooling trap — why one tool, used together, beats four licenses spread across the team
• Who's responsible when something goes wrong? — calculated risk + a no-fault, no-blame postmortem policy
• Measuring ROI — forget "10x feels"; the only number worth tracking is PRs deployed to production
• Are we keeping up with competitors? — a 20% efficiency gap is massive, and it compounds in months
• How do we know AI is doing what we think? — agents, gates, canaries, and tuning context surfacing
• Are we losing institutional knowledge? — the answer is to auto-update docs and runbooks every night

Notable Quotes

• "I don't think board members care about culture very much. Bottom line — are you guys shipping?"
• "Pick one tool, make your whole company use the same tool. A bunch of individuals using AI is more productive, but a team using AI together gets you 10x."
• "If you're not investing and seeing your team adopt AI and ship faster, your competitors are. Maybe not now, but they will in three months."
• "Everything that Claude needs to know is the same thing that humans need to know."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan break down the upfront infrastructure work required before a single repo is ready for autonomous programming. They walk through the full prep checklist — monorepo structure, lazy-loaded docs, 90% test coverage with end-to-end tests, a dev environment that actually matches prod, canary deploys, and observability — and explain why each one is non-negotiable when you're shipping code without a human in the loop.

Key Topics

• Why monorepos win — a root-level CLAUDE.md that knows how all your services interact, plus per-service docs underneath
• Progressive disclosure for context — keep CLAUDE.md under 200 lines and lazy-load topical docs (data model, GitHub Actions, Terraform, API endpoints)
• A daily docs cron — agents that update your docs every morning so context never goes stale
• Agent validation = tests + lints — 90% coverage as a hard gate, unit + end-to-end, all green before merge
• Shipwright crons in practice — development, review, docs, golden principles, cruft cleanup; one of them found and fixed an unauthorized Stripe webhook overnight
• Dev parity, canary deploys, and observability — the safety stack that makes shipping without a human safe (yes, just pay for Datadog)

Notable Quotes

• "You can't just turn it on and expect magic to happen. There's a bunch of upfront work — we call it infrastructure — around your repository."
• "You're shipping code without a human involved. So you gotta put in as many safety things as possible. You gotta burn those extra calories to make sure dev is the same as prod."
• "I am an open source guy, but if it was up to me — just bite the bullet. Pay for Datadog and use APM."
• "By the way, these are things that would benefit any organization even if you aren't autonomous. Every org should be doing this anyway."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan share what they're seeing in the field this week: non-software engineers — in marketing, sales, customer service, and data — are getting massively accelerated by Claude Desktop and MCP servers. The episode centers on a real story of a single subject matter expert who built a Snowflake data tool, shared it across his entire company, and eliminated the need for one-off dashboard requests forever. The core argument: stop experimenting with every AI tool and pick one. For the whole company.

Key Topics

• Claude Desktop for non-engineers — How marketing, sales, and ops teams are using Claude Desktop + MCP servers to do work that previously required engineering sprints
• The admin app problem — Why internal tools are always hacked together, and how giving Claude access to the data warehouse sidesteps that entirely
• Snowflake + Claude + Vector DB — How one team built a self-documenting data layer: Claude explores the warehouse, writes documentation, and surfaces the right tables via natural language
• Pick one tool — The case for committing your whole org to a single AI platform so shared tools, skills, and workflows actually compound across teams
• Building skills, not just prompts — Why the unlock isn't the first conversation with Claude, it's turning that conversation into a reusable skill that works every time
• What Anthropic hasn't built yet — Two missing pieces: scheduled tasks (a morning brief without cron hacks) and a direct bridge between Claude Code and Claude Desktop projects

Notable Quotes

• "Be an adult. If you're in leadership, say: we are going with this tool. Dan and I recommend Claude Code."
• "It's not Claude, it's not GPT. These things are getting better and better. It's the system you're building on top of it."
• "A single human being who was an expert on this was able to create a tool for himself — and now he shared it with his team. Developers can use it. Marketing can use it. Anyone in the company can use it."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan announce Vitals OS — App Vitals' autonomous coding pipeline built on Claude Code and their Shipwright plugin. In the past two weeks it shipped 393 pull requests, with Dave and Dan writing fewer than 10 of them. They walk through how the pipeline works, where it still needs humans, and how they plan to bring it to client codebases.

Key Topics

• The 393 PR milestone — what autonomous coding at scale actually looks like in practice
• The Shipwright plugin — a full DevOps-style pipeline covering research, planning, coding, and validation
• The 95% threshold — where the agent runs fully autonomous and where humans step in
• Slack as the interface — directing agents via voice notes while walking the dog
• The last 5% — deployment, monitoring, and architecture review as the human value-add
• Vitals OS for clients — launching the product for founders and non-technical builders

Notable Quotes

• "Dan and I have done less than 10 pull requests out of the 400. It's pretty powerful stuff."
• "It doesn't stop until all the PR tests have passed successfully."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

A client asked Dave and Dan a deceptively simple question: "What should we call the job title for the person who leads our AI engineering transformation?" The answer surprised them — it's not a new role. It's a Principal Engineer. In this episode, they break down exactly what that means, why the best candidate hasn't written a line of code in the last six months, and how to interview for it.

Key Topics

• Why there's no new job title — agentic engineering isn't a sliver of your org, it's the whole thing. The role is Principal or Distinguished Engineer, full stop.
• The counterintuitive hiring criterion — you want someone who's written code for 10–20 years but hasn't written a line in the last six months. They've already built the trust with AI systems to let go.
• DHH and Linus flipped — both publicly opposed AI-generated code; now it's in Rails and the Linux kernel. The holdouts have adapted. So should you.
• Why rewrites almost always fail — Dave and Dan's take on migrations: the first 80% is easy, the last 20% kills the project, and you end up with something just as messy as what you started with.
• The interview process has changed — don't ask them to write code. Ask them to show you the system they built to build code. "If you built it by coding, you're not a good candidate."
• Management is in the way — autonomy and agency are what make senior engineers succeed. Micromanagement is the fastest way to lose the person you just hired.

Notable Quotes

• "If you built it by coding, you're not a good candidate."
• "Your job nowadays is to not just build that system, but to constantly improve that system. You're building, maintaining, and improving a system that's building stuff for you — that is your job."
• "It's game over guys. You need to adapt if you haven't already."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan share a jaw-dropping collaboration breakthrough: Claude Code's voice mode accidentally picked up Dan's suggestions over a Google Meet call, turning a routine planning session into a real-time AI pair-planning session with two people and one AI. They also react to the OpenAI source code leak, discuss the real cost of their MAX subscription, and share how Claude Code fits into every part of their day — including 2 AM phone sessions from bed.

Key Topics

• The Google Meet Epiphany — Claude Code voice mode picking up a second person's voice over video call unlocks true real-time collaborative AI planning
• Simpler than you think — Years of complex collaboration feature ideas, solved by speech-to-text + two people on a call
• The last 5% with clients — How this breakthrough eliminates friction between technical and non-technical collaborators
• OpenAI source code leak — Dave and Dan's hot take: it's more about the system you build on top of the LLM layer than the model itself
• The real cost of Claude MAX — $200/month subscription estimated at $5k/month in equivalent API usage
• Claude Code everywhere — Voice mode on walks, remote sessions at 2 AM, agents coding while you sleep

Notable Quotes

• "You don't need a hundred different features. It's just get on a Google Meet, start pairing together."
• "Oh my God, dude, if we don't build some awesome product, it's our fault, not Claude."
• "If they were to actually charge what it actually costs, I might have to be an electrician."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Dave and Dan share how they shipped 254 pull requests in 7 days using AI agents Sully and Bodhi — with only about 10 hours of human effort combined. They unpack the key unlock (getting out of the terminal and into Slack), how they accidentally broke their own planning rules and recovered, and how adding metrics and learning loops turned a chaotic experiment into a real production system.

Key Topics

• 254 PRs in 7 days: how autonomous agents maintained 40 PRs/day even on weekends
• Getting out of the terminal — why Slack became the unlock for async AI collaboration
• How two agents with the same model developed different personalities through memory
• Skipping the planning phase, chaos, microservices, and Wednesday night recovery
• Metrics as ground truth: moving from learning loops to hard numbers with PostHog
• What enterprise engineering orgs need to do right now (break your workflows)

Notable Quotes

• "You should be breaking your workflows right now. You should be experimenting. You should not hold on to any legacy workflows."
• "We have two pull requests in the last 20 minutes, and Dan and I are sitting here talking. We did not do anything. It is just our bots out there working."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS