I was there Gandalf…
Before that date their algorithm was soft-locked to around 5k upvotes. If a post was extremely, massively popular it would climb to maybe a bit over 10k but that was insane. There was clearly a logarithmic scaling effect that kicked in after a few thousand upvotes. Not entirely sure why, perhaps to prevent the super-popular stuff from ballooning in some kind of horrible feedback loop.
The change was to uncap the vote counts. One day posts just kept climbing well beyond the 5k mark. Now what they also did was recalculate old posts in order not to fuck up the /top
rankings. Kinda. Took a while and I’m not sure they got to every post.
I don’t know or care if reddit does vote manipulation, but this ain’t proof and I don’t see how it is unbelievable that a website with tens of millions MOA would occasionally have a post with 100k+ upvotes.
What? I’m not privy to RedHat/IBM/Google’s internal processes but they are all massive FOSS contributors at least some of which I assume are using Agile internally. The Linux kernel is mostly corpo-backed nowadays.
The development cycle of FOSS is highly compatible with Agile processes, especially as you tend towards the Linux Kernel style of contributing where every patch is expected to be small and atomic. A scrum team can 100% set as a Sprint Goal “implement and submit patches for XYZ in kernel”.
Also agile ≠ scrum. If you’re managing a small github project by sorting issues by votes and working on the top result, then congratulations, you’re following an ad-hoc agile process.
I think what you’re actually mad at is corporate structures. They systematically breed misaligned incentives proportional to the structure’s size, and the top-down hierarchy means you can’t just fork a project when disagreements lead to dead ends. This will be true whether you’re doing waterfall or scrum.