Looking at the CSS classes, it references the procedence of the mathematician: (North) America is green, Middle East orange, Asia red, and so on. Tao is the only blue: he is from Oceania (Australia.)
I came to the comment section to compliment the choice of Garamond.
The web would look much more beautiful with proper justification. It's a pity technology is not there yet. TeX solved the problem for DVI/PDFs long ago, so maybe we should start blogging on PDFs!
The author has written the novel "Permutation City", which I read after seeing it recommended here on HN a lot. It is a great book. I never thought I would be interested in sci-fi, but this book changed my mind. It deals with simulating conciousness and its implications.
If you enjoyed the post, and the author's website, be sure to read some of his books too!
In the subject of Artificial Intelligence it says:
> Theorem: No AI will bother after hacking its own reward function.
and then goes on:
> The picture [263] is that once the AI has figured out the philosophy of the “Dude” in the Cohen brothers movie Lebowski, also repeated mischiefs does not bother it and it “goes bowling”. Objections are brushed away with “Well, this is your, like, opinion, man”. Two examples of human super intelligent units who have succeeded to hack their own reward function are Alexander Grothendieck or Grigori Perelman.
I guess that for some people, and particularly in small reviews, it is enough with the list of files and inline comments.
I would like to have a tree view where I can see all the files at a glance, and, more importantly, switch back a forth between them. I find it hard to follow the code in Github's UX.
Also, Fisheye/Crucible gives you more flexibility to edit the review, by allowing you to remove files, and add or remove commits. Github PRs are based on branches, while Fisheye/Crucible code reviews are based on commits; it is an entire paradigm shift that gives the user more control. For example, I can create two separate reviews from the same branch on Crucible; that's impossible on Github.
By reading the stream of comments on the PR, and from my own experience, I feel that it is extremely cumbersome to do code reviews on Github. Atlassian's Fisheye/Crucible looks like a better solution. Does anyone think otherwise? I think Github has a large room of improvement in this regard; a PR is not the same as an issue.
I love essays in commit messages! They can be very useful, especially when they describe why the change is being applied, instead of what is being done, which is usually the case.
