are merged PRs a measure of velocity? github.com/kimjune01/

No, of course not? I don't even disagree with your main premise but obviously "raw number of merged PRs" is not a high signal metric, even more so in the age of agentic/vibe coding.

This you?

https://june.kim/speedrunning-open-source

> tinygrad I picked on purpose. geohot narrates rejections in public, and a narrated rejection is data; a silent close is noise. Thirteen PRs, one merged, twelve closed. His comments tell the escalation story:

>> be careful with AI usage, we never trade complexity for speed

>> You need to stop with AI PRs, you will be banned.

>> Last warning about low quality PRs before I ban you from our GitHub.

>> I don’t even understand what this does. I’m not reading anything written by AI

> Each line a little more done with my shit than the last.

> Some of those PRs had real bugs with real fixes. The MATVEC pattern rejected equal-range elementwise reduces, a genuine correctness issue. But by that point the maintainer had stopped reading code and started reading provenance. “We never trade complexity for speed” is a valid engineering principle. “I’m not reading anything written by AI” is not.

> I went there for maximum surprise and got it. He had a review queue and a quality bar to protect; I had a clanker and a question. The price was his afternoon, three warnings, an account ban, and real bugs left unfixed.

Because this is Facebook-level "let's make people angry on the internet and see what happens" levels of treating people as if they were means to an end rather than an end in themselves. And you should stop.

No, not any more than lines of code written are measures of velocity