Selling electronic goods with instructions used to be the norm. It's much rarer now.
What changed? Did consumers stop reading them? Did the average consumer ever read them? Why is it acceptable to skip a manual now?
miniblog.
Chess is beaten (machines can play a perfect game) when there are up to 7 pieces on the board.
This might seem like a simple question of compute power, but clever implementation matters. If you can effectively compress your DB, you can use a bigger one!
https://en.wikipedia.org/wiki/Endgame_tablebase#Computer_chess
Board games seem to have a tendency of giving the first player an advantage, at least with perfect play: https://en.wikipedia.org/wiki/Solved_game
Looking at the increasing dominance of FOSS software in chess programs, I wonder if open source, commoditised implementations are the likely end goal for most software applications.
Perhaps professional programming will become largely glue/business logic?
Optimising the Dart VM, performance cliffs, and the amazing number of string representations in V8: https://mrale.ph/blog/2016/11/23/making-less-dart-faster.html
Contributing etiquette for open source, or why patches should honour the original coding style (however ridiculous): https://tirania.org/blog/archive/2010/Dec-31.html
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!
A reddit bot that applies machine learning to chess game pictures and extracts the game position! https://github.com/Elucidation/tensorflow_chessbot#reddit-bot
Neat concept. You could extend it to analyse the position too.
Advocacy is important for new tech. People are invested in what they know and use. For them to change, you need to be *persuasive*.
We are demanding ever more tasks from our frontend build processes:
https://css-tricks.com/annotated-build-processes/
(No wonder they can be complex!)
The read function (lex+parse) in lisp is really handy for building little analysis or metaprogramming tools. The runtime has it, so why not allow users to use it?
However, there's no equivalent for just lexing AFAIK. It's a shame because the same arguments apply!
Promoting NO_COLOR as an informal convention for controlling CLI output: https://no-color.org/
How do you help yourself (and teammates) prevent your JS bundles from becoming too big?
You could expose library size in the IDE! Really interesting approach.
https://marketplace.visualstudio.com/items?itemName=wix.vscode-import-cost
How do you help yourself (and teammates) prevent your JS bundles from becoming too big?
You could expose library size in the IDE! Really interesting approach.
Finding a bug in GNU Tar, and tracking down the problem: https://utcc.utoronto.ca/~cks/space/blog/sysadmin/TarFindingTruncateBug
(Old tools are often robust, but by no means bug free!)
Estimating the fundamental value of bitcoin by looking at its captive markets: https://medium.com/@dsquareddigest/how-i-guesstimated-the-value-of-bitcoin-in-2014-e64f327753c8
The entertaining consequences of an IoT toaster oven with an internet accessible video camera: https://arstechnica.com/gadgets/2018/12/how-a-toaster-oven-helped-me-learn-to-stop-worrying-and-love-the-internet-of-things/
Prefer API elegance to implementation elegance, and prefer boring code to clever code: https://reactjs.org/docs/design-principles.html#implementation
It's fascinating how smartphone websites often consider *descriptions* to be secondary content!
I've seen this both on Amazon and eBay. Apparently the title and pictures are sufficient.
Porting babel and closure compiler to Rust! https://github.com/swc-project/swc
Showing 1-20 of 657 posts