Episode Summary

A month ago, Dave and Dan weren't giving this advice. Now they're telling every client — from solo founders to the Fortune 500 — the same thing: adopt autonomous coding immediately. The technology crossed the quality threshold, and this is now a CEO-level decision, not an engineering preference.

Key Topics

• Why the advice changed this month — autonomous agents now ship real, high-quality code, not AI slop
• Shipwright (free, open-source, runs in your own infrastructure) vs. Devin (commercial, $25B valuation, raising $1B)
• Why adoption is a CEO's call — developers won't volunteer to stop writing code
• Developers get paid to plan and review, not to write code — and that's the part that doesn't change
• Flatten your org: top-heavy, management-heavy structures break under autonomous velocity
• The economics — roughly $10–20 per PR/feature in tokens, optimized down toward $10

Notable Quotes

• "If your VP of engineering is not pounding on the door saying 'we need to adopt this,' you should think about getting a different VP of engineering."
• "A lot of developers think they're getting paid to write code. That is over with."

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

Episode Summary

Dave and Dan make the case that developers are no longer getting paid to write code — and explain why that's actually better news than it sounds. Drawing from real client work across Fortune 500s and one-person startups, they walk through what the new engineering job actually looks like: planning, reviewing, and exercising technical judgment while autonomous agents do the typing.

Key Topics

• Why paying developers to write code is now a waste of money — and what to do instead
• The new developer job: plan, deploy, review, and manage autonomous agents
• How junior engineers can level up faster in the AI era
• Why the transition from coder to engineer is harder than it sounds (and why Dave wishes AI hadn't happened)
• What engineers should actually be spending their time on: CI, deployments, incidents, and bigger systemic problems
• How Shipwright fits into the autonomous coding workflow — and why engineers fear it

Notable Quotes

• "There is absolutely no reason at this moment to pay developers to write code. That is an absolute waste of money."
• "No one is paying you to type anymore. No one's paying you to look at a terminal. That is over with right now."
• "Your job was never really to write code. Code was a byproduct of judgment."

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

Episode Summary

Dave and Dan break down how Shipwright, their open-source autonomous coding agent, stacks up against Devin AI — a $26B-valued competitor. They cover the key differences: open source vs. black box, runs in your infrastructure vs. Devin's cloud, built on Claude Code for full extensibility, and the one thing Devin doesn't do that Shipwright does — deploy.

Key Topics

• Why they accidentally built a Devin alternative while building for their own clients
• Open source (MIT) vs. closed black box — what you can and can't customize
• Your infrastructure vs. Devin's cloud — the security and flexibility gap
• Claude Code as the foundation: plugins, skills, and the extensibility advantage
• Deployment: Shipwright merges and deploys, Devin stops at the PR
• Cost model: Shipwright's only cost is tokens; Devin adds licensing at every seat

Notable Quotes

• "Shipwright literally built Shipwright. The last 1,000 pull requests in Shipwright were all written by Shipwright."
• "Devin is a black box. You have no idea what it's doing. The only knobs you can turn are the ones they give you."

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

Episode Summary

Dave and Dan tell the origin story of App Vitals — from LiveKit AI-voice tutorials to an AI-transformation consultancy to shipping their own open-source autonomous coding agent. They unpack the 37signals philosophy that shapes how they build, how a mobile-dev side project quietly became Shipwright, and why test readiness is the real on-ramp to autonomous programming.

Key Topics

• The 37signals model — build products for yourselves first, let consulting pay the bills
• How Shipwright started as a Claude Code plugin and grew into a managed autonomous coding agent
• Shipwright vs. Devin — open source, runs in your own infrastructure, fully customizable vs. a closed SaaS black box
• Coding asynchronously in Slack: planning and reviewing while the agent handles execution, PRs, review, and deploy
• The ski-trip story — building and deploying a website by voice from a chairlift, no laptop
• Test readiness as Phase Zero: fixing flaky, slow, low-coverage tests before you can trust an agent to ship

Notable Quotes

• "There's no reason to be in a terminal. There's no reason to write code anymore."
• "While I was skiing, it built a different version of solitaire and deployed it to Vercel — and I never saw my laptop the whole day."
• "We ship hundreds of PRs a week for us and our clients with no human interaction."

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

Episode Summary

Major announcement: Dave and Dan are open-sourcing Shipwright, the autonomous coding agent they've been building since November. It takes you from PRD to production deployment with no human intervention ~99% of the time — and it built itself. Across ~500 pull requests, they say they barely read a line of code. The core provocation for leaders: if a free tool can 10X your engineering throughput and you choose not to adopt it, that's a decision you'll have to justify.

Key Topics

• Open-sourcing Shipwright (MIT) — PRD → plan → code → tests → PR → CI → review → merge → deploy, mostly hands-off
• "Shipwright built Shipwright" — ~500 PRs, the founders read essentially none of the code
• The 14-step dev-task checklist (TDD, green CI, docs) vs. raw Claude Code's half-baked PRs
• Human-in-the-loop only where it must be — Terraform applies, secret/key updates, GitHub access
• Run it in your own cloud (EC2/EKS/AKS/Kubernetes) — you control security, secrets, and tokens
• The economics: 10X throughput for free, but it also 10X's token spend and pressures headcount
• Portable by design — a thin Claude shim means it can move to OpenCode/Pi and open-source LLMs later

Notable Quotes

• "If you have an engineering team and you're choosing not to adopt this, you are choosing not to 10X your throughput on purpose."
• "Shipwright created Shipwright. It has 500 pull requests... I didn't look at a single line of code."

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

Episode Summary

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

Episode Summary

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

Episode Summary

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