Sep 9, 2026 · 59 min · 11 segments
This episode is Part 2 of Who Owns The Code. The team explores how “vibe coding” with AI is reshaping who can build software inside organizations, and what happens when prototypes start drifting…
Agile was a big change on kind of how you do things from start to finish when you're developing software applications or quote unquote products.
And now you got idiots like me that can write code because I can't write code, but I can tell AI what I want and they can kind
So I did some research on this, and actually Robert Hansen put an interesting article about the idea of a lead developer leaving because they had become the lead code reviewer and hadn't written anything.
They built agents to kind of write their code, and so their developers became code reviewers instead of actual creators and builders and
thinkers.
Which is a good topic that does definitely, I think, I don't know, branch off of this one, but this one's more about yeah, how do you get your arms around a full company worth of people who think they can build the next solution? And sure enough, they kind of can, but they're really, I don't know, I'm really interested in this topic from other people, basically, because I've certainly got some experiences, but I'm also struggling with the language that we use.
I struggle with understanding the boundaries of when does somebody who's vibe coding, when does it, you know, become a prototype versus, you know, a full on application and based on some of these categorizations, what, what should happen? Like how much, wild west do we allow to kind of get to something and then once we have something where do we formalize it uh and and transition it into something that is monitored secure scalable maintained managed um and frankly supported by like redundancy like you become dependent on a single person if you you know a vibe code one thing um Anyway, sorry, I just kind of ran with it there, Kyle, but that's what I was hoping to get into a little bit.
So, okay, so I think the real challenge for all of this is somebody wants something useful, right? And in order to be useful at your company, they have to take your data and your information and do something with it, right? And all along from...
probably the first, I don't know, password hack or software security breach, IT has worked up a series of processes to prevent bad things from happening as much as possible,
right?
Like, hey, we don't put passwords into our Git repository because it could somehow get taken over by somebody so that's a bad thing five coders have very none restrictions like they're they don't care what why would they care they're they're asking Claude to do it and they're giving Claude all the information that it needs to do its job right
I feel like some of it is they don't know or they trust that the AI is already factoring in all of those other elements that we've spent 30 years trying to lock down and control and understand.
Right.
Agile was a big change on kind of how you do things from start to finish when you're developing software applications or quote unquote products.
And now you got idiots like me that can write code because I can't write code, but I can tell AI what I want and they can kind
So I did some research on this, and actually Robert Hansen put an interesting article about the idea of a lead developer leaving because they had become the lead code reviewer and hadn't written anything.
They built agents to kind of write their code, and so their developers became code reviewers instead of actual creators and builders and
thinkers.
Which is a good topic that does definitely, I think, I don't know, branch off of this one, but this one's more about yeah, how do you get your arms around a full company worth of people who think they can build the next solution? And sure enough, they kind of can, but they're really, I don't know, I'm really interested in this topic from other people, basically, because I've certainly got some experiences, but I'm also struggling with the language that we use.
I struggle with understanding the boundaries of when does somebody who's vibe coding, when does it, you know, become a prototype versus, you know, a full on application and based on some of these categorizations, what, what should happen? Like how much, wild west do we allow to kind of get to something and then once we have something where do we formalize it uh and and transition it into something that is monitored secure scalable maintained managed um and frankly supported by like redundancy like you become dependent on a single person if you you know a vibe code one thing um Anyway, sorry, I just kind of ran with it there, Kyle, but that's what I was hoping to get into a little bit.
So, okay, so I think the real challenge for all of this is somebody wants something useful, right? And in order to be useful at your company, they have to take your data and your information and do something with it, right? And all along from...
probably the first, I don't know, password hack or software security breach, IT has worked up a series of processes to prevent bad things from happening as much as possible,
right?
Like, hey, we don't put passwords into our Git repository because it could somehow get taken over by somebody so that's a bad thing five coders have very none restrictions like they're they don't care what why would they care they're they're asking Claude to do it and they're giving Claude all the information that it needs to do its job right
I feel like some of it is they don't know or they trust that the AI is already factoring in all of those other elements that we've spent 30 years trying to lock down and control and understand.
Right.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
