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