It's a little free tool for planning groups with good mixing and various constraints, based on a near-solution to a neat combinatorics problem. Originally designed for teachers planning discussion groups, and I've had folks use it for lunch tables and board game tournaments. Recently I get about 1k uniques per month (but that might be a lot of bots).
Whether they're gone or not, I definitely want _more_ of these. I've had great success with shared Tampermonkey scripts at work, augmenting off-the-shelf tools my team uses with conveniences specific to our team. For example, automatically extracting relevant bits within noisy logs when browsing CI results, or providing buttons that kick off narrow re-runs or link to relevant source files. CSS injections are great too, a very lightweight way to improve the accessibility and usability of tools.
Actually, that's a fascinating part of the story. We run the entire test262 ECMAScript Conformance Suite (https://github.com/tc39/test262) against our JS-Interpreter fork. We don't pass the whole thing yet, but it ensures we only ratchet toward conformance to the language spec.
We checked, and this particular bug was not caught by the test262 suite - the broken sort worked for enough cases to slip past the Array.prototype.sort tests there. We've added a regression test for this issue in the layer that consumes the interpreter, but I've thought about proposing more aggressive validation of sort behavior to the test262 project.
It was a great reminder to me that while tests may be necessary for quality, they are not always sufficient!
It's a little free tool for planning groups with good mixing and various constraints, based on a near-solution to a neat combinatorics problem. Originally designed for teachers planning discussion groups, and I've had folks use it for lunch tables and board game tournaments. Recently I get about 1k uniques per month (but that might be a lot of bots).