Mason McLead

But, you know, at least setting up some boundaries there. And I think, yeah, that's an important thing to see. And it also expresses through the data that we have. And I was going to say, the other thing that was interesting in our data that's not as obvious is some of the patterns that we see that don't grow at a linear pace but go exponential is with...

But, you know, at least setting up some boundaries there. And I think, yeah, that's an important thing to see. And it also expresses through the data that we have. And I was going to say, the other thing that was interesting in our data that's not as obvious is some of the patterns that we see that don't grow at a linear pace but go exponential is with...

pull request review times if you look at how long it takes for a pull request to get reviewed the the time as you would guess increases as the size of the pr in terms of lines of code like how many changes there are increases so from one to two hundred it's certain value from two to five it's a slightly bigger value but when it goes above 500 lines the time to review grows 10x in one jump.

pull request review times if you look at how long it takes for a pull request to get reviewed the the time as you would guess increases as the size of the pr in terms of lines of code like how many changes there are increases so from one to two hundred it's certain value from two to five it's a slightly bigger value but when it goes above 500 lines the time to review grows 10x in one jump.

So there's some particular inflection points in the size of code going through the pipeline that start to take an inordinate amount of time to get through the pipeline because the processing of it is so much harder as a person to go and review and the complexity of it grows by so much. So there's certain...

So there's some particular inflection points in the size of code going through the pipeline that start to take an inordinate amount of time to get through the pipeline because the processing of it is so much harder as a person to go and review and the complexity of it grows by so much. So there's certain...

kind of base rules that you can start to find out at your organization by seeing the state of like, we're good in this phase. So if you can keep your PRs and change sets below a certain amount, they'll generally flow faster.

kind of base rules that you can start to find out at your organization by seeing the state of like, we're good in this phase. So if you can keep your PRs and change sets below a certain amount, they'll generally flow faster.

And the more that you have these like smoother flowing chunks of changes going through, the better cumulative overall you're going to do as your production throughput at the end. So there's a lot of really interesting things there that you can see once you have this data because not everything's linear and most everything that we see follows the power curve

And the more that you have these like smoother flowing chunks of changes going through, the better cumulative overall you're going to do as your production throughput at the end. So there's a lot of really interesting things there that you can see once you have this data because not everything's linear and most everything that we see follows the power curve

Yeah. No, actually that is expressed there. I was going to say that, but when you get these giant ones, people go, whatever, it's probably fine. Click. And like, that's probably not great for the end result as well.

Yeah. No, actually that is expressed there. I was going to say that, but when you get these giant ones, people go, whatever, it's probably fine. Click. And like, that's probably not great for the end result as well.

The time that's captured there is the kind of the culmination of whatever research you're doing there. So if you're on Stack Overflow and you're researching how to solve a problem or reading the docs, if that's what you do. I have some friends that do that. Then going to be investing time in there.

The time that's captured there is the kind of the culmination of whatever research you're doing there. So if you're on Stack Overflow and you're researching how to solve a problem or reading the docs, if that's what you do. I have some friends that do that. Then going to be investing time in there.

And then the output of that is your active code time when you figured it out and you've made the edits and drew out the tests. And so it's kind of a distilled set of time of everything else that you've put into it. But we do track other things that are going on during the day, like meeting time. And in general, developers meet 30 or 40% more during the day than they have active code time.

And then the output of that is your active code time when you figured it out and you've made the edits and drew out the tests. And so it's kind of a distilled set of time of everything else that you've put into it. But we do track other things that are going on during the day, like meeting time. And in general, developers meet 30 or 40% more during the day than they have active code time.

So that's a big other portion of your day. And then we're starting to track Slack data as well. So we'll be able to see how much time is being spent in that, as well as how much does that help or hurt your individual productivity? Like if you have a question and you get it answered via Slack really quickly, and then you have a productive session because you got that answered,

So that's a big other portion of your day. And then we're starting to track Slack data as well. So we'll be able to see how much time is being spent in that, as well as how much does that help or hurt your individual productivity? Like if you have a question and you get it answered via Slack really quickly, and then you have a productive session because you got that answered,

Or you could be coding and then you get a bunch of unrelated Slack messages that pulls your attention away and it ruins your session. So there's positives and negatives that we can start to see from that. And then, of course, that's another big portion of the day is communication and collaboration through that. But yeah, so it's hard to say whether that two hours is a good thing or a bad thing.

Or you could be coding and then you get a bunch of unrelated Slack messages that pulls your attention away and it ruins your session. So there's positives and negatives that we can start to see from that. And then, of course, that's another big portion of the day is communication and collaboration through that. But yeah, so it's hard to say whether that two hours is a good thing or a bad thing.