Searching...
18 results for “developer productivity”
Topic11 mentions across episodes
developer productivity
Concept5 mentions across episodes
productivity
Concept2 mentions across episodes
developer productivity
...much more productivity do you get per person? You know, actually, maybe just to even say one other thing for some of these large companies.
1:04:29 / 1:05:32
from transcript1:04:29 – 1:05:32
...as a productivity metric isn't great. Right? It's pretty bad. But now it's kind of more relevant if we can tease out which code came from people and which code came from AI because now we can answer downstream questions. What is the code's survivabil
12:46 / 13:52
from transcript12:46 – 13:52
If I merge some line and then I change that line, if you change that line in a shorter period, it'll churn versus a longer period, it'll count as, like, refactoring, which is, like, a little So gen generally, in enterprise code bases, if you merge a
38:19 / 39:20
from transcript38:19 – 39:20
And we were like, oh god. No. But it can generate the code, and you just gotta paste it in. You just gotta do all this stuff. Right? And they were like, that sounds kinda hard. And we're like, but it's faster, and they they wouldn't do it. And then n
12:04 / 13:11
from transcript12:04 – 13:11
Like, as you think about live coding and all that, how does the percentage of potential usefulness change when I feel like we over engineering a lot of times, it's like the investment in syntax. It's less about the investment in, like, architects act
22:26 / 23:32
from transcript22:26 – 23:32
Where is the 25% of all code is deleted by AI? Right? Like, this is where we have to start thinking about it because the right code is never the volumous, like, lines of code metric. It's always something else. It's always like elegance, and that's w
48:44 / 49:46
from transcript48:44 – 49:46
...What people really care about is, like, developer sentiment.
39:02 / 40:05
from transcript39:02 – 40:05
...and the developers? They do. Some of them do. I don't think most people look at monitoring. I think look. It's it's it's too simplistic to suggest that, frankly, in my opinion, because Okay. Engineering is a hard job. Right? It's easy to say no commi
31:28 / 32:33
from transcript31:28 – 32:33
So can I delete, start over, and build this, more easily? And now everything else becomes, like, easy to build on top of. And so we routinely we have, like, a we have a delete code club. We have hack days, which happens two or three times a year wher
47:56 / 49:06
from transcript47:56 – 49:06
You touched on something that I wanted to get to later, but I may as well bring it up now. The question of just how engineering will change in the future. You throw out the stat that, like, 90% of code is gonna be written by AI in the future. Dario f
17:13 / 18:19
from transcript17:13 – 18:19
public with this once they have more data about it. Yeah. Anecdotally, they're sharing that, The performance. The performance difference is like 10 x by any way that you measure it. So lines of code, commits, business impact, whatever. And it's it's
3:00 / 4:08
from transcript3:00 – 4:08
and that I've seen is, again, this kind of rapid prototyping. I hate lines of code, but I'm going to use lines of code. We do see I know I worked with, some folks who had kind of a whole set of companies they were looking at. And they found that, AI
34:30 / 35:32
from transcript34:30 – 35:32
with Claude code to write a document that helps sort of decide a set of heuristics to decide when you should assign it to codex versus when you should give it to clog code. And so if it's tightly defined enough and simple enough, I just send it off t
28:28 / 29:47
from transcript28:28 – 29:47
makes code a particularly good place to do this is that code is verifiable in a way that, you know, most other work is not. So, you know, with code, you can verify that the build works. Right? So you can say, hey. I wanna build this. I wanna build th
30:42 / 31:45
from transcript30:42 – 31:45
saving $2,000,000 a year on our infrastructure bill, which is about somewhere between half to two thirds, goes directly to the bottom line, which means it's returned to Jason or I as owners and our employees, part of our, profit sharing plan. It's to
3:22:31 / 3:23:44
from transcript3:22:31 – 3:23:44
Have a podcast?
Run your podcast through Clypt
Get ranked clips, hooks, and ready-to-post copy from your own episodes. Free to try.