marcusbuffett

Ah this is a great find, the bullet chess clock. It's partly inference time before the intentional delay, and partly the animation of the move counts towards the bot's time. Should be fixed now though.

Fixed the premove thing too, I think.

Do you find the bots on chess.com play human-like chess? I'm not sure what they're using under the hood but I assume they've also put some effort into this sort of stuff.

Yeah the intention is to make them available on my chess site eventually (Chessbook). It's in very early alpha though, so it's breaking constantly as I tweak things and try playing against it with different configurations.

I used this for spaced repetition for opening training on Chessbook, can vouch that the Rust package is excellent. Easy to use and immediately lowered the training load on our users while keeping retention high. FSRS is awesome.

I strongly recommend "A Philosophy of Software Design". It basically boils down to measuring the quality of an abstraction by the ratio of the complexity it contains vs the complexity of the interface. Or at least, that's the rule of thumb I came away with, and it's incredible how far that heuristic takes you. I'm constantly thinking about my software design in these terms now, and it's hugely helpful.

I didn't feel like my code became better or easier to maintain, after reading other programming advice books, including "Clean Code".

A distant second recommendation is Programming Pearls, which had some gems in it.

Yeah as someone working on educational software, anything hand-rolling their own SRS is a pretty big red flag. Beating FSRS is going to be next to impossible, especially FSRS with parameters optimized from your users’ review history.