Charles Maxwood

And so the reality is, is if you're not measuring it as a team, you're not measuring all of that other stuff and you're going to miss really a big part of how this all kind of comes together. Because at the end of the day, everything that I'm working on and everything that you're working on and everything that everybody else is working on, on this particular app or set of apps,

And so the reality is, is if you're not measuring it as a team, you're not measuring all of that other stuff and you're going to miss really a big part of how this all kind of comes together. Because at the end of the day, everything that I'm working on and everything that you're working on and everything that everybody else is working on, on this particular app or set of apps,

it all goes into the same bucket and we're all measuring that progress on the same rubric. Yeah, exactly.

it all goes into the same bucket and we're all measuring that progress on the same rubric. Yeah, exactly.

then it all works out pretty well there. So one thing that I'm wondering about then is, so let's say that we have this aggregated team data, right? We know how the team's doing. We can kind of see how the team flows, how things generally work. I mean, what do we do with it? Do we just try different things to see what makes it better?

then it all works out pretty well there. So one thing that I'm wondering about then is, so let's say that we have this aggregated team data, right? We know how the team's doing. We can kind of see how the team flows, how things generally work. I mean, what do we do with it? Do we just try different things to see what makes it better?

Or will it actually give us indicators of what to try to make things better?

Or will it actually give us indicators of what to try to make things better?

Oh, please.

Oh, please.

So most of the stuff you're talking about here is stuff that I guess seems pretty common sense to most developers, right? You know, you're coding to meeting time. Maybe your music, some music's going to help you get into flow. Others won't. Protecting kind of your peak times. A lot of this stuff makes a lot of sense. Are there any counterintuitive things?

So most of the stuff you're talking about here is stuff that I guess seems pretty common sense to most developers, right? You know, you're coding to meeting time. Maybe your music, some music's going to help you get into flow. Others won't. Protecting kind of your peak times. A lot of this stuff makes a lot of sense. Are there any counterintuitive things?

ideas around productivity that people kind of get hung up on? It's like your data is telling you one thing and people's intuition will tell them something else.

ideas around productivity that people kind of get hung up on? It's like your data is telling you one thing and people's intuition will tell them something else.

Oh, wait, wait. Not exactly. Me too.

Oh, wait, wait. Not exactly. Me too.

No, I can't see why that would be a problem at all. Yeah. I wish people would review my PRs that way. Oh, it's Chuck. Yeah, he always writes good stuff. Done. Always. Always. Anyway, I did want to ask another question, though, about when you were talking about how people generally get like two hours of editing slash code time per day.

No, I can't see why that would be a problem at all. Yeah. I wish people would review my PRs that way. Oh, it's Chuck. Yeah, he always writes good stuff. Done. Always. Always. Anyway, I did want to ask another question, though, about when you were talking about how people generally get like two hours of editing slash code time per day.

Does that mean that the other six hours is like mental time or stack overflow time or Google time? Or is that like realistically how productive we are?

Does that mean that the other six hours is like mental time or stack overflow time or Google time? Or is that like realistically how productive we are?