Mason McLead

So there's a trust factor there and in a transparency that with a responsible and well put together team, you don't really need to hide this stuff when it's abstracted to the team level. Everyone can benefit from it. So there's no point in hiding it. So I think as long as you stick with the individual data belongs to the individual and team to the team,

So there's a trust factor there and in a transparency that with a responsible and well put together team, you don't really need to hide this stuff when it's abstracted to the team level. Everyone can benefit from it. So there's no point in hiding it. So I think as long as you stick with the individual data belongs to the individual and team to the team,

Yeah, that's always the big question. Like, okay, now I have data. I can see stuff. What do I do? Because that's always the point of the data is to get something out of it, not just to see it. So there's particular things that we show, like your code time to meeting time ratios, which... Generally, for your development team, you want them to probably be coding more than meeting.

Yeah, that's always the big question. Like, okay, now I have data. I can see stuff. What do I do? Because that's always the point of the data is to get something out of it, not just to see it. So there's particular things that we show, like your code time to meeting time ratios, which... Generally, for your development team, you want them to probably be coding more than meeting.

Yes. Yeah. So there's specific things that you can do there. And we'll find out when you as an individual and then also your team has their kind of peak hours in the day. And then you can use our tool to block out the calendars for everyone during that peak time so that no meetings can get put there.

Yes. Yeah. So there's specific things that you can do there. And we'll find out when you as an individual and then also your team has their kind of peak hours in the day. And then you can use our tool to block out the calendars for everyone during that peak time so that no meetings can get put there.

So it's just protected code time on everyone's calendar so that you've got that set aside where you know that people are generally at their peak productivity and their peak output. So that's one thing to do is just protect that time. Using the flow mode tool in the extensions gets you to block out notifications and distractions whenever you are in the zone. And we're actually coming out very soon.

So it's just protected code time on everyone's calendar so that you've got that set aside where you know that people are generally at their peak productivity and their peak output. So that's one thing to do is just protect that time. Using the flow mode tool in the extensions gets you to block out notifications and distractions whenever you are in the zone. And we're actually coming out very soon.

We're experimenting with it internally where we can detect when you're about to get into what we call a flow session. This is a high productivity, high focus section of coding. and automatically enable it.

We're experimenting with it internally where we can detect when you're about to get into what we call a flow session. This is a high productivity, high focus section of coding. and automatically enable it.

So your computer will just react to what you were doing and start blocking out notifications and put you into flow mode whenever you ramp up into it so that you don't get that ping right at the time that you're right into it. So that's something that's really interesting right now. It's a button click. So you click that and it does it. So those are things that you can do.

So your computer will just react to what you were doing and start blocking out notifications and put you into flow mode whenever you ramp up into it so that you don't get that ping right at the time that you're right into it. So that's something that's really interesting right now. It's a button click. So you click that and it does it. So those are things that you can do.

And then once you have the data and you're seeing trends over time, that's when you can actually start to do experiments internally with your team to see what does optimize it. And when you break down

And then once you have the data and you're seeing trends over time, that's when you can actually start to do experiments internally with your team to see what does optimize it. And when you break down

your like the the lead time for code into the different sections of here's the input time that it takes here's the pull request review time and and then how long does it take from there to get merged into the default branch you can start to look at the different sections of the cycle and say okay this part is taking too long and you can hone in on where as a as a system of processes you've got something a little bit awry and then you can really hone in okay why are reviews taking so long which is a common complaint

your like the the lead time for code into the different sections of here's the input time that it takes here's the pull request review time and and then how long does it take from there to get merged into the default branch you can start to look at the different sections of the cycle and say okay this part is taking too long and you can hone in on where as a as a system of processes you've got something a little bit awry and then you can really hone in okay why are reviews taking so long which is a common complaint

or from the time that I open the PR to the time it's first reviewed, it takes this much time. Or once it's reviewed, it's still not getting merged for two days for some reason. It's like, what's going on there? So you can start to really hone in on different behaviors that are adding unnecessary delay into the process. and watch what happens as the behaviors change.

or from the time that I open the PR to the time it's first reviewed, it takes this much time. Or once it's reviewed, it's still not getting merged for two days for some reason. It's like, what's going on there? So you can start to really hone in on different behaviors that are adding unnecessary delay into the process. and watch what happens as the behaviors change.

So there's a lot of really cool stuff that you can start to do once you just see the data and then have a few little tools there to start to control the environment around it.

So there's a lot of really cool stuff that you can start to do once you just see the data and then have a few little tools there to start to control the environment around it.