Mason McLead

the way that other tools traditionally do this where it's per person you're going to see one person did everything and the other person did nothing based on who committed what and that wasn't the case at all like this is definitely a team effort and so if you just abstract it away to the proper level then you don't fall into that trap of having this false stack rank

the way that other tools traditionally do this where it's per person you're going to see one person did everything and the other person did nothing based on who committed what and that wasn't the case at all like this is definitely a team effort and so if you just abstract it away to the proper level then you don't fall into that trap of having this false stack rank

of individuals assuming that they're all doing their own individual stuff which is never the case when you're on a team that's working well together and the communication side of it is a it's kind of an invisible and i think undervalued in a lot of times aspect of team building that that really you'll see the effects of it when it's going well at the team level but you can't really see it if you just look at all the individuals by themselves

of individuals assuming that they're all doing their own individual stuff which is never the case when you're on a team that's working well together and the communication side of it is a it's kind of an invisible and i think undervalued in a lot of times aspect of team building that that really you'll see the effects of it when it's going well at the team level but you can't really see it if you just look at all the individuals by themselves

Since we've been digging into this a lot, there's a big difference between what Git by itself is and what GitHub or Bitbucket does on top. Git itself is this wild web of there is no default. Well, actually, I think in the newest version, there is now the concept of a default branch in Git itself.

Since we've been digging into this a lot, there's a big difference between what Git by itself is and what GitHub or Bitbucket does on top. Git itself is this wild web of there is no default. Well, actually, I think in the newest version, there is now the concept of a default branch in Git itself.

All of the structure and the hierarchy that makes it really workable at scale came from the providers on top of it. which I found really interesting because I was trying to just figure it out at the get level. And it's just, it's really, really difficult because it's designed to be very widespread and non-hierarchical so that it can be as scalable as it is.

All of the structure and the hierarchy that makes it really workable at scale came from the providers on top of it. which I found really interesting because I was trying to just figure it out at the get level. And it's just, it's really, really difficult because it's designed to be very widespread and non-hierarchical so that it can be as scalable as it is.

GitHub or Bitbucket, you'd be able to have multiple authors on pull request. It's kind of their main object. In the commit level itself, you've got an author and a committer. They can be the same. They usually are. They could be different. Basically, if you take someone else's commit, rebase it, kind of rewrite history, they're still the author, but you're the committer.

GitHub or Bitbucket, you'd be able to have multiple authors on pull request. It's kind of their main object. In the commit level itself, you've got an author and a committer. They can be the same. They usually are. They could be different. Basically, if you take someone else's commit, rebase it, kind of rewrite history, they're still the author, but you're the committer.

So you can get kind of mixed identities in it that way. But otherwise, you got to use what abstractions and additions other companies put on top of it.

So you can get kind of mixed identities in it that way. But otherwise, you got to use what abstractions and additions other companies put on top of it.

Yeah. I mean, the thing about the way that I look at someone getting credit for... like an individual getting credit for a PR for a commit or something like that, I think it makes sense when the individual's looking at their own data, but from a team perspective, if the group is getting it done well together, then I think that's the main thing that matters. And if there's someone that's not

Yeah. I mean, the thing about the way that I look at someone getting credit for... like an individual getting credit for a PR for a commit or something like that, I think it makes sense when the individual's looking at their own data, but from a team perspective, if the group is getting it done well together, then I think that's the main thing that matters. And if there's someone that's not

pulling their weight or there is a performance problem with the individual, you're going to be able to know that without looking at the stats here. I'm sure we've all experienced that over the years. And I've done that personally in years ago.

pulling their weight or there is a performance problem with the individual, you're going to be able to know that without looking at the stats here. I'm sure we've all experienced that over the years. And I've done that personally in years ago.

I got a tool that did the stack ranking based on commits and all that stuff, basically just to prove what I already knew and that I, as the manager, needed to let this person go because it wasn't a good fit for the team. And The data that I pulled in that did that was really just a crutch. I already knew. I didn't feel confident in myself as a manager at that point to do it.

I got a tool that did the stack ranking based on commits and all that stuff, basically just to prove what I already knew and that I, as the manager, needed to let this person go because it wasn't a good fit for the team. And The data that I pulled in that did that was really just a crutch. I already knew. I didn't feel confident in myself as a manager at that point to do it.

The data didn't really help. And then actually, the team knowing that that tool was in place and that I had access to it and no one else did because that's the way the tool was set up, they actually... really, really didn't like it. And we kicked it out after two months.

The data didn't really help. And then actually, the team knowing that that tool was in place and that I had access to it and no one else did because that's the way the tool was set up, they actually... really, really didn't like it. And we kicked it out after two months.