Mason McLead

It seems to be a good one. If you don't, and that's just a byproduct of you not having gotten stuff done during the week because you're distracted all the time. It's like, how do you make a Saturday like...

It seems to be a good one. If you don't, and that's just a byproduct of you not having gotten stuff done during the week because you're distracted all the time. It's like, how do you make a Saturday like...

environment during the week so that you can have that same amount of focus to be as productive on those days and like those are some of the the small behavioral shifts that you can start to put into your work week as a team and as an individual so that you can get more focus work done during the week and then actually take time off because you're a person as well and you need to do other things

environment during the week so that you can have that same amount of focus to be as productive on those days and like those are some of the the small behavioral shifts that you can start to put into your work week as a team and as an individual so that you can get more focus work done during the week and then actually take time off because you're a person as well and you need to do other things

Yeah, so we've got several metrics that go into it. And in the coming weeks, we'll have it all connected to Git commits and those sorts of things.

Yeah, so we've got several metrics that go into it. And in the coming weeks, we'll have it all connected to Git commits and those sorts of things.

We're doing that internally right now, just kind of refining the product before we put it out there, where we can look at... If you kind of arrange how development works in line of kind of a physical factory, it's not the same because you're not recreating the same thing over and over again. It's a creative endeavor, but... Right.

We're doing that internally right now, just kind of refining the product before we put it out there, where we can look at... If you kind of arrange how development works in line of kind of a physical factory, it's not the same because you're not recreating the same thing over and over again. It's a creative endeavor, but... Right.

If you kind of look at it that way as a metaphor and say there's all these inputs that go into it and that for us is the time, the amount of characters and lines and like just the raw materials that go into it. And then you look at the outputs. And I think so far the best sort of abstraction for what an output, a unit of output is, is a merged pull request.

If you kind of look at it that way as a metaphor and say there's all these inputs that go into it and that for us is the time, the amount of characters and lines and like just the raw materials that go into it. And then you look at the outputs. And I think so far the best sort of abstraction for what an output, a unit of output is, is a merged pull request.

It's a chunk of work that someone has thought is enough to stand on its own. And it's good enough gone through the quality checks to get merged into the default branch, which would then go to production. So those are the inputs and the outputs of this factory.

It's a chunk of work that someone has thought is enough to stand on its own. And it's good enough gone through the quality checks to get merged into the default branch, which would then go to production. So those are the inputs and the outputs of this factory.

And if you look at the traditional definition of efficiency and productivity, it's how much input does it take to get to some unit of output. So as soon as you have that, now you've got the full view of the development cycle. What is going in? What is coming out? And you can start to get a lot of really interesting measurements about the overall system and then each of the steps along the way.

And if you look at the traditional definition of efficiency and productivity, it's how much input does it take to get to some unit of output. So as soon as you have that, now you've got the full view of the development cycle. What is going in? What is coming out? And you can start to get a lot of really interesting measurements about the overall system and then each of the steps along the way.

So when you hear about things like cycle time, which is typically when someone's looking at that from another tool, they're looking at when the commit was pushed to when it was merged. And I don't know how you like to commit. People do it differently. But I usually code nearly all of everything before I do the first commit.

So when you hear about things like cycle time, which is typically when someone's looking at that from another tool, they're looking at when the commit was pushed to when it was merged. And I don't know how you like to commit. People do it differently. But I usually code nearly all of everything before I do the first commit.

And then I commit, make a PR, push it, and then I'll get feedback and maybe make some changes. But the bulk of the work of the input side is before that first commit, which is completely missed by these other tools. And it also gives you a... Depending on how your behavior is, it gives you a false number about what your cycle speed is.

And then I commit, make a PR, push it, and then I'll get feedback and maybe make some changes. But the bulk of the work of the input side is before that first commit, which is completely missed by these other tools. And it also gives you a... Depending on how your behavior is, it gives you a false number about what your cycle speed is.

Yeah, exactly. So getting a realistic number and just observing... what the team is actually doing gives you an empowerment to go and actually make positive changes to it. And that's really at the core of it. This is what this is about.

Yeah, exactly. So getting a realistic number and just observing... what the team is actually doing gives you an empowerment to go and actually make positive changes to it. And that's really at the core of it. This is what this is about.