Developer Productivity

“I do think that very bullish estimates of speed up today are, you know, to some extent inflated by what we document in that original paper, that people's expectations of speed up tend to be too optimistic, it seems. They also tend to be inflated, I think, by n…”

“If you're getting there in ways that are high toil or high friction, then at some point a developer is going to burn out. Or if it's, you know, super high cognitive load, if it's hard to even think about what you're doing, because you're concentrating on like …”

“If you can solve a problem that they have, or it's like something that they're focused on, if you can slightly reframe it even, right? Like if they're calling everything developer productivity, go ahead and call it productivity. If they're calling it velocity …”

“If I was a CEO or like a CTO of a large enterprise company, I wouldn't think in terms of, oh, how can we make our engineers more productive? I would think in terms of how can we get the most information about what we should build as quickly as possible into ne…”

“Rough data, maybe somewhere between 18 to 25% productivity boost for a developer, which is fairly massive, right?”

“And I think AI on top of that is going to give us maybe another order of magnitude or two in terms of, you know, what a human can produce functionally.”

“And we're seeing the developer productivity go up, you know, can be anywhere from 10 to 40%, depending on the developer, depending on the use case, which is massive, even if it stays at 10%.”

“I think the best way to measure developer productivity is, like, in terms of the feedback loops. Like, it, like, in, like, How quickly when you iterate, like when you write code, like how quickly can you get feedback? And at the innermost loop, it's like runni…”

“You look at the developers are, I've been getting like probably 10 X more productive every decade for the last four, four decades or something that was kind of crazy. Like on an exponential scale, we're talking about 10 X or is there a 10,000 X like, you know,…”

“The most easiest one is time, but time is, it's funny what I'm going to say, but time is not quantifiable. As a success metrics, because you can write really bad code really fast.”

“This actually matters because we find that satisfaction well-being ends up being incredibly highly correlated with all of the other dimensions of productivity and doing things well. And as soon as satisfaction well-being, things like sustainability, if you're …”

“Now, to use space correctly, we want to use at least three dimensions at a time, because that helps us balance.”

“Software productivity just has to go up. There is no other way. Or we will not have the software. Right? So the demand exists. Supply doesn't exist. And so the supply has to scale faster. And the only way supply will scale faster is when developer productivity…”