A "tech conference" called LambdaConf, after a blind reviewing process, accepted a technical presentation proposal from someone who had written about unpopular views on politics. Pressure groups demanded the conference exclude him; when the conference organizers decided not to do so, the pressure groups campaigned to have corporate sponsors withdraw support. Much to their discredit, most of the corporate sponsors did in fact do so. A "crowdfunding" campaign has been organized to replace the money those sponsors could have provided. I have donated, and I hope you will as well.
I would like to say a few words about my close friend Axel Harvey, who I'm informed died yesterday.
My text for today is from Pink Floyd (Another Brick in the Wall, part II): "If you don't eat your meat, you can't have any pudding!" I'd like to talk about the fallacy embedded in that statement. It's related to many well-known fallacies, but I haven't been able to find an existing name that applies specifically to this fallacy in this form without mixing it up with other things. So I'd like to give it a new name: let this be known as the fallacy of the Pudding.
Shortly after I finished my PhD in 2008, I took about half a year off from other work, and wrote a 100,000-word science fiction thriller called Shining Path. That was half a year for the actual writing. It was a synthesis of notes and other material I'd been collecting for a number of years previously. I then spent the next three years or so looking for an agent to represent it.
日本語が分かっても、時々英語で植字をしなければならないです。 英語では文章と言葉の中で、いつも空白あります。 LaTeXを使えば、もしかしたら文章と言葉の空白が難しいです。 今日本件の勉強をしましょう。
これはTeX & LaTeX Advent Calendar 2015に僕の寄贈です。
I found an interesting problem while working on a test case generator for the Tsukurimashou Project. The thing is that I'd like to assign an identifying code, which I will call an address, to each line of code in a code base. It's to be understood that these addresses have nothing to do with machine memory addresses, and they need not be sequential; they are just opaque entities that designate lines of code. Anyway, I would like lines of code to keep the same addresses, at least probabilistically, when the program is modified, so that when I collect test information about a line of code I can still keep most of it after I update the software.
I have posted a detailed set of notes (PDF file) describing the theory behind my Black Swan Suite, detailing the endless chase of Elmer and Daffy across Penrose, pinwheel, and other nonperiodic tilings of the plane. Fans of music and computational geometry may find the document interesting. At the very least, it was fun to typeset.
This was originally a Facebook comment, to one of my friends who had posted one of the original articles there, but a lot of other people in my circles are re-sharing the same articles, more general distribution of these comments is appropriate, and anyway Facebook is an untrustworthy platform. So, here's a repost. For necessary context, see the earlier articles from Edward Schlosser and Koritha Mitchell. Both of these articles have received a whole lot of circulation in the last few days, but I'm not sure they've received enough serious attention.
On this first day of 2015 I'm writing down some things that are important and that I wish people around me would know. There's nothing here that I haven't said before. My usual pattern is to say something and treat it as settled, because I expect everyone present at the time to remember it once they've been told. But not all of my friends have been paying attention to all of my writings for all of the decades I have been writing, and maybe at this time some repetition is appropriate. I wish I could have ten thousand readers for this and for all of my important postings. I may be lucky to get as many as ten readers. But if nothing else, the exercise of choosing what I want to say today is of some use to me personally, whether anybody reads it or not.
It's New Year's Eve in Copenhagen, and time for another update.