1,145 pull requests per day
saile.it
1,145 pull requests per day
1–10 of 91 posts
Re: 1,145 pull requests per day
#2My previous company averaged 2 PRs (and deploys) per engineer per day across a small team. At my current company I'm averaging about 2.5 CLs per day (they're a bit smaller changes). Stripe is good at this, but this is very achievable.
Often the problem is that we put too much into a single change. Smaller changes means easier reviews, better reviews, less risky deploys, forces better tooling for deployments and change management, often lower latency, and even often leads to higher throughput because of less WIP taking up head space and requiring context switching. The benefits are so compounding that I think it's very undervalued in some orgs.
Re: 1,145 pull requests per day
#3My previous company averaged 2 PRs (and deploys) per engineer per day across a small team. At my current company I'm averaging about 2.5 CLs per day (they're a bit smaller changes). Stripe is good at this, but this is very achievable. Often the problem is that we put too much into a single change. Smaller changes means easier reviews, better reviews, less risky deploys, forces better tooling for deployments and chang…
I think better tooling for deployments allows small changes.
Not the other way around.
Re: 1,145 pull requests per day
#4My previous company averaged 2 PRs (and deploys) per engineer per day across a small team. At my current company I'm averaging about 2.5 CLs per day (they're a bit smaller changes). Stripe is good at this, but this is very achievable. Often the problem is that we put too much into a single change. Smaller changes means easier reviews, better reviews, less risky deploys, forces better tooling for deployments and chang…
I think better tooling for deployments allows small changes. Not the other way around.
That's sort of what I mean by small changes being a forcing function. The tooling we have available rarely makes this level of small changes untenable, it's just clunky. When you send 1k PRs a day though you'll notice things that are too clunky and fix them, and then that makes it easier to get to and maintain that level of productivity.
Re: 1,145 pull requests per day
#5Lol, yeah but a PR won't fix that expired cert.
Re: 1,145 pull requests per day
#6PRs merged is the LOC count. Completely useless measure of anything really.
Re: 1,145 pull requests per day
#7Is counting the number of pull requests a useful measure of engineering performance ergo product performance and company perf?
Isn't it more like a BS counter that keep incrementing and that is indicative of churn but nothing else reliably.
One of the most low effort, easily to game metric that can be skewed to show anything that the user wants to show.
Re: 1,145 pull requests per day
#8This sounds like how PMS sometimes tout the number of tickets per sprint. It's not a relevant metric, and it's easily gamed
How many of those prs were small fixes? How many went to low used services, or services only used internally?
They clearly have strong set of tooling for dev ops stuff, and I do believe that stripe has strong technical chops, but this number does not show that they are delivering value. It just shows they are delivery something... Somewhere
Re: 1,145 pull requests per day
#9Sure, looks cool but really means nothing without looking at the type of changes. I could think of many tricks if I wanted to chase this stat
Re: 1,145 pull requests per day
#10I would think they have elite testing and QA team to make that happen