Post

Haven't even read the article, just smashing shapes around in the top section 11/10 for engaging me before I read a single word

Amazing article! The logs are hilarious. Turtle rejecting a PR due to "bad vibes" is one of my favs. Also 👏👏👏 for shipping readable javascript that I can inspect in the browser.

Easy follow and subscribe. This is exactly the kind of content we need in the dev world. All too often someone doesn't know how to ELI5 because they don't really understand the concept or because they want to gatekeep to sell more content. Truly open source learning. Thank you!

Thank you so much, Greg 😁 I went into this one expecting it to be easy. I knew the algorithm well, it’s easy to implement, and the math behind it isn’t exotic. I was super wrong. Reworked it twice, almost in full both times. Struggled tremendously to explain the math in a way that felt intuitive.

Helps if I link to it, doesn't it. samwho.dev/reservoir-sa...

It’s been posted to the orange site. If you read it and enjoyed it, I’d be super grateful for an upvote over there. 🙏❤️

posted on the red (?) site 🫡 lobste.rs/s/r0axbc/res...

Great article! Maybe I missed something, but for me, Q always replaces K in the final one-card example. I think this is because, in SimpleReservoir, *n* starts from 0. On the second deal, it's 1, so `floor(random() * this.n)` always evaluates to 0, resulting in a replace github.com/samwho/visua...

One potential fix would be to calculate `j` as `floor(random()*(this.n+1))`. Also, in the multi-card example, it wasn't obvious that "generate a random number between 0 and *n*" assumes that *n* is not included. This is also confusing because, up to that point in the article, we counted *n* from 1.

Fixed the off-by-one. Thank you again for pointing that out.