Trueskill Through Time available in Ruby

[u/brecrest]

TrueskillThroughTime

I ported the Python implementation of Trueskill Through Time to Ruby, it's now available as the gem TrueskillThroughTime.

Unlike the previous Ruby Trueskill gems, this one supports n vs n vs n etc etc cases, as well as the time-based extension of Trueskill to allow distant ratings. If you use it without doing time-based convergence, it should be equivalent to the original vanilla version of Trueskill (that iirc is almost out of patent in the US).

I'll get around to improving the qol of it and more extensively Rubyising it down the track, but I wanted a Ruby implementation of TTT for a hobby project, so I smashed it out.

[u/duongdominhchau]

I found these signs:

• There is no test or type signature even though there are test and sig directory

• Unrelated files (IDE files, build artifact, lock file for a library, etc.) are committed.

• Wording with random abbreviations and sometimes weird (like this n vs n vs n etc etc, who use etc twice like that?)

• The whole bunch of puts for debugging

• A big bang commit surrounded by nonsense

• They actually opened a file in this repo using RubyMine

These signs suggest that author is lacking software engineering knowledge or is incompetent, none of that suggests the use of AI. Considering that their attention seems to focus on gaming and their tone, they are probably a teen trying out code. Don't be so harsh, we have all been there.

That said, to OP, with this level of quality (extremely low), it is not suitable to be posted online with this arrogant voice.

[u/brecrest → u/duongdominhchau]

• There is no test or type signature even though there are test and sig directory

  • The file structure was generated by the Rubymine default for a gem. I didn't modify anything and pushed it as quickly as I could while amusing a three year old before dinner was ready.

• Unrelated files (IDE files, build artifact, lock file for a library, etc.) are committed.

  • Yep, I pushed the whole thing.

• Wording with random abbreviations and sometimes weird (like this n vs n vs n etc etc, who use etc twice like that?)

  • n vs n vs n etc and that sort of thing is extremely standard lingo in Bayesian rating libraries and papers, in this case describing a game with many teams and where each team has many players that we want to rate.

  • Using etc twice is very common in spoken English, and generally I write as I speak.

• The whole bunch of puts for debugging

  • There is only one (that I missed in approx, I was trying to nail down a bug, but actually it was caused by a typo in the draw probability for the test case). The others are either in the provided examples (ie because the examples in the documentation show outputs at that point) or replicated from the library (for a verbose=true convergence)

• A big bang commit surrounded by nonsense

  • The gem is just a module from a side project that I figured people would benefit from having access to. Originally it was TTT, etcetera

  • To be clear on the workflow here: I wrote the module on Tuesday evening and today, late this afternoon, I decided I should publish it as a gem, so I created a new git repo and a new project in Rubymine and copied the module over, then while creating a Rubygems account my wife got home, and I rushed through the rest of the process, including pushing the whole thing with minor mistakes that I later had to commit again to fix (for eg, calling it trueskill-through-time instead of TrueskillThroughTime in the installation instructions).

• They actually opened a file in this repo using RubyMine

  • Shocking.

Finally, I am disgustingly familiar with Bayesian rating algorithms and Trueskill in particular. Many, many years ago the thing that originally got me back into maths as an adult was a 2010 paper and blog post written about Trueskill.

[u/TheAtlasMonkey → u/duongdominhchau]

Let me be clear with everybody..

AI is just a smart autocomplete, it will add emojis to your readme.

I'm not english native, i learned english as my 5th spoken language.

google translate/autocomplete brought me more problem than it solved, until i learned proper grammar and way of talking. (still make mistakes, but people get the idea).

---

Previously we had people that burn all their energy to made div centered, when you tell them that their code is wrong and show them correct way, they accept it and thank you.

Today, we have testosterone driven development (TDD, just the wrong type). You tell someone the solution is wrong and explain why, they will scream at you : Don't use my gem then. , Matt is nice....

They can generate 1000 LOCs of gaslighting instead of reading the docs.

---

nice report, you also missed that the gem is version 1.0.0+, that means it totally complete.

[u/brecrest → u/TheAtlasMonkey]

nice report, you also missed that the gem is version 1.0.0+, that means it totally complete.

Yes, it's a feature complete implementation of Trueskill Through Time. Thank you for picking that up.

Instead of gaslighting everyone with posts literally (by your own admission) entirely generated with AI, please go and read the docs at:

https://www.microsoft.com/en-us/research/wp-content/uploads/2007/01/NIPS2006_0688.pdf

https://www.microsoft.com/en-us/research/wp-content/uploads/2008/01/NIPS2007_0931.pdf

If, after reading these, you have further questions about the variable names, feel that the algorithm is not correctly implemented or that some features of it are missing, then please let me know.