One crucial factor in Stockfish becoming a leading chess engine is its test framework.
Summary: https://en.wikipedia.org/wiki/Stockfish_(chess)#Fishtest
Initial announcement: https://www.talkchess.com/forum3/viewtopic.php?start=0&t=47885&topic_view=flat&sid=b5662f579ad4c7bea91668bb9d9723a4
Lots of engines have clever programmers, but a strong test technique gave it an extra edge!
miniblog.
Related Posts
I sometimes see blog posts lamenting how inconsistent UIs are in modern apps.
When did consistency peak? Windows 3? After the release of Aqua for macOS? The era when Bootstrap was the default CSS framework for many web developers?
Has the JS ecosystem reached a point where people agree roughly what a good architecture looks like?
I don't see as many blog posts complaining about new framework churn and I'm wondering why.
Watching https://youtu.be/KWB-gDVuy_I and I'm struck by how weird constructors are as an API.
* They promote total functions, making it hard to do validation.
* They're hard to split up, because they have special access to unfinished data.
* They're like a framework: you get called.
