O TYM ODCINKU
This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps.
In this Ship It Conversations episode, I talk with Ted Julian about the gap between AI-generated code getting written and teams trusting it enough to ship it, why code review is the first thing to break, and who should own AI-generated code once it's running in production.
Ted is the founder and CEO of Flux (askflux.ai), an engineering intelligence platform, not Flux CD the GitOps tool. He has spent more than twenty years building security and infrastructure companies, including Resilient Systems, Arbor Networks and @stake.
We start with Flux's AI Code Generation Reality Check: 44.7% of the organizations surveyed already run AI-generated code in production, and 35% write it but don't ship it. What holds them back is trust: complexity that could spiral into an outage, a new library with a vulnerability, regulated data nobody has really scrutinized.
Ted calls code review act two of an AI transformation, and he says it's a people problem as much as a tooling problem. His once-in-a-career hack: measure features versus maintenance versus bug fixes now, backfill it, and show the before and after. At one customer, feature work went from 9% to 43%, and it became a chart in their board meeting.
We also get into why engineering has to be the yes squad, with guardrails, the bill that comes due when someone has to understand code nobody really wrote, who feeds the cat, what loops mean for visibility, and why tech disruption is the best career opportunity you'll get.
Highlights
• Written but not shipped: 44.7% in production, 35% holding back
• Code review breaks first, and it's a people problem
• Measure features vs. maintenance vs. bug fixes, then backfill
• From 9% to 43% feature work, as a board chart
• The yes squad, with guardrails
• The bill for code nobody really wrote
• Who feeds the cat: one owner for AI-generated code
• Loops, dark factories and a control plane
• Why disruption is your best career move
Links
Ted on LinkedIn · Flux · AI Code Generation Reality Check · Cobalt case study · More episodes · On Call Brief · LMGT Awards
TRANSKRYPCJA 🔗
00:00:00.000 --> 00:00:03.120
If more than one person is responsible for feeding
00:00:03.120 --> 00:00:06.900
the cat, the cat starves. My guest today used
00:00:06.900 --> 00:00:10.640
that line for a question a lot of teams are dodging
00:00:10.640 --> 00:00:14.960
right now. Who owns AI-generated code once it's
00:00:14.960 --> 00:00:18.660
running in production? His company surveyed engineering
00:00:18.660 --> 00:00:22.460
teams. Almost half already run AI-generated
00:00:22.460 -->…