One fascinating property of chess engine design is that a deeper tree search can be more valuable than a smarter board value metric.
If a metric is more accurate but more computationally expensive, it might not be worthwhile! It's a precision/brute force tradeoff.
Related Posts
I like that most LLM UIs show your previous queries prominently.
When figuring out where LLMs are useful in your workflow, it's nice to see what worked well (or not) in the past.
Web search doesn't have this property. I rarely look at what I've previously googled.
One advantage I've come to appreciate about Dash/Zeal docsets: it's really nice having focused search.
The text search is constrained to the languages I care about enough to download the docset, substantially increasing the relevance. In Google I'd need to specify the language.
I've been using "Expected Int, but got String" for my type error messages, but I've been wondering if I could do better.
"Expected Int here, but this value has type String" or "This expression requires Int, but the value is String".
Do you have a favourite?