https://www.youtube.com/watch?v=7gi7nMuyUc4
He looks real.
I was thinking of setting up a small server that can emulate some up multiplayer games, such as battleship, connect 4, even perhaps monopoly.
Then people submit code, or connect their machines to it, and it becomes "battle of the algorithms".
You'd have to register an algorithm name / version, and compete a few times against other algorithms, to be placed on the leaderboard for that game*.
Each game could just be stored as plaintext, so it would be easy to replay each move and visualise it on the website.
I haven't yet begun creating it, but it'd be great to see how your algorithm would work against another; You'd also have to consider how to place your ships as well. (probably sticking them in the corners could be easily dealt with, right?
Looking at this algorithm it seems like it's pretty optimal, I don't think there's much else that could be done with Battleships. Playing with other human players would be a different outcome..
* I would only really expect algorithms work per game, not across games.
Although there is no specific implementation for Battleship, but I believe that some users sometimes have the possibility to create and submit their own games.
Your app looks very promising. Polished UI. Intuitive. Unlimited habits. Simple "task -> award" principle without added complexity layers.
Something I'm having trouble finding in the apps I've tried is the distinction between "habit" and "task". An habit is something I want to do multiple time in a week. While a task is a one-shot TODO that I would like to execute at some point when I'm not procrastinating. Once done, I don't need to repeat it, but I like to be rewarded.
Your application seems to be more habit oriented. Is the notion of a one-time task something you could eventually incorporate?
x = stuff
while x:
x = stuff while true:
x = stuff
if not x:
break
It's basically impossible to view diffs now because they often fail to load, render correctly, or just are incredibly slow.
They completely redesigned the code navigation to load it dynamically using React. One of the regressions introduced caused the entries to be duplicated when searching for a word using Ctrl+F. Their solution to address this issue? Decompose the source character by character, assigning each individual character its own distinct HTML node...
Needless to say, in addition to abysmal performance (it took seconds to display on my laptop), this also caused new problems (such as the inability to search for certain composite emojis). The worst part is that they seemed proud of their hack, since they wrote a blog post about it.