[ About | Features | Music | Pictures | Software | Writing ]
Crummy: The Site
We fight 'em until we can't.


News You Can Bruise

[Archives]
Buy my books!

8 years ago: I got a fancy Ruby gem set up on RubyForge, so now...

10 years ago: Then, Her Sari Flaps In The Wind!

11 years ago: Tragedy

14 years ago: Today's Checkerboard Nightmare

[No comments] What's New in RESTful Web APIs?: I was asked on Twitter what changed between 2007's RESTful Web Services and 2013's RESTful Web APIs. I've covered this in a couple old blog posts but here's my definitive explanation.

First, let me make it super clear that there is no longer any need to buy Services. It's out of date and you can legitimately get it for free on the Internet. O'Reilly is taking Services out of print, but there's going to be a transition period in which copies of the old book sit beside copies of the new book in Barnes & Noble. Don't buy the old one. The bookstore will eventually send it back and it'll get deducted from my royalties. If you do buy Services by accident, return it.

If you're not specifically interested in the difference between the old book and the new one, I'd recommend looking at RESTful Web APIs's chapter-by-chapter description to see if RESTful Web APIs is a book you want. As to the differences, though, in my mind there are three big ones:

  1. The old book never explicitly tackles the issue of designing hypermedia documents that are also valid JSON. That's because JSON didn't become the dominant API document format until after the book was published. If you don't know that's going to happen, JSON looks pretty pathetic. It has no hypermedia capabilities! And yet, here we are.

    In my opinion, a book that doesn't tackle this issue is propping up the broken status quo. RESTful Web APIs starts hammering this issue in Chapter 2 and doesn't let up.

  2. There are a ton of new technologies designed to get us out of the JSON trap (Collection+JSON, Siren, HAL, JSON-LD, etc.) but the old book doesn't cover those technologies, because they were invented after the book was published. RESTful Web APIs covers them.
  3. New ideas in development will, I hope, keep moving the field forward even after we all get on board with hypermedia. I'm talking about profiles. Or some other idea similar to profiles, whatever. These ideas are pretty cutting edge today, and they were almost inconceivable back in 2007. RESTful Web APIs covers them as best it can.

Now, for details. Services was heavily focused on the HTTP notion of a "resource." Despite the copious client-side code, this put the focus clearly on the server side, where the resource implementations live. RESTful Web APIs focuses on representations—on the documents sent back and forth between client and server, which is where REST lives.

The introductory story from the old book is still present. Web APIs work on the same principles as the Web, here's how HTTP works, here's what the Fielding constraints do, and so on. But it's been rewritten to always focus on the interaction, on the client and server manipulating each others' state by sending representations back and forth. By the time we get to Chapter 4 there's also a pervasive focus on hypermedia, which is the best way to for the server to tell the client which HTTP requests it can make next.

This up-front focus on hypermedia forces us to deal with hypermedia-in-JSON (#1), using the tools developed since 2007 (#2). The main new concept in play is the "collection pattern". This is the CRUD-like design pioneered by the Atom Publishing Protocol, in which certain resources are "items" that respond to GET/PUT/DELETE, and other resources are "collections" which contain items and respond to POST-to-append.

We covered AtomPub in Services, but over the past six years it has become a design pattern, reinvented (I think "copied" is too strong a word) thousands of times.

RESTful Web APIs focused heavily on the collection pattern, without ever naming it as a pattern. I'm not dissing this pattern; it's very useful. I'd estimate about eighty percent of "REST" APIs can be subsumed into the collection pattern. But REST is bigger than the collection pattern. By naming and defining the collection pattern, we gain the ability to look at what lies beyond.

Attempts to encapsulate the collection pattern include two new JSON-based media types: Collection+JSON and OData. The collection pattern also shows up, more subtly, in the Siren and Hydra formats. Which brings me to the second major change.

In 2007, there were two big hypermedia formats: Atom and HTML. Now there are a ton of hypermedia formats! This is great, but it's also confusing. In "The Hypermedia Zoo", Chapter 10 of RESTful Web APIs, we give an overview of about two dozen hypermedia formats. The ones we seriously recommend for general use (HAL, Siren, HTML, JSON-LD, etc.) are covered in more detail elsewhere in the book. The quirkier, more specialized media types just get an exhibit in the zoo.

Now for the third new thing, profiles. If you go through the RESTful Web APIs narrative from Chapter 1 to Chapter 7, you'll see that we introduce a problem we're not able to solve. Hypermedia is great at solving the following problem:

How is an API client supposed to understand what HTTP requests it might want to make next?

But there's a superficially similar problem that hypermedia can't solve:

How is an API client supposed to understand what will happen in real-world terms if it makes a certain HTTP request?

How do you explain the real-world semantics of an HTTP state transition? Before chapter 8, the two solutions are to do it ahead of time in one-off human-readable documentation; or to define a domain-specific media type, a la Maze+XML. Both of these approaches have big problems. Chapter 8 introduces profiles, which lets you get some of the benefits of a new media type without doing unnecessary work.

Maybe profiles will turn out not to be the right answer, but we gotta solve this problem somehow, and the old book is not equipped to even formulate the problem.

There are also a few additions to the book I consider minor. There's a whole chapter in RESTful Web APIs on Semantic Web/Linked Data stuff; in Services there was nothing but a cursory discussion of RDF/XML as a representation format. There's a chapter in RESTful Web APIs about CoAP, which didn't exist in 2007. These are good chapters that took me a long time to write, but I don't think it's worth buying the book if you only want to read the chapter on CoAP. (Or maybe it is! There's not a lot of competition right now.)

So, what hasn't changed? HTTP hasn't changed all that much. RESTful Web APIs's information about HTTP has been brought up to date but not changed significantly. So if you were using Services solely as an API-flavored HTTP reference, you don't need the new book. You can just read up on the protocol-level additions to HTTP since 2007, like the Link header and standardized patch formats for PATCH.

Hopefully this helps! RESTful Web APIs has a lot of distinguished competition that the old book didn't have, but its competition is newer books like Designing Hypermedia APIs and REST in Practice. If you compare APIs to Services I think it's no contest.

[Comments] (1) Reading After-Action Report: In preparation for my reading at Enigma Bookstore I asked people on Twitter which bit of Constellation Games I should read. I decided to read Tetsuo's review of Pôneis Brilhantes 5 from Chapter 18, both by popular Twitter demand and because Sumana had reported success reading that bit to people.

I practiced reading the review and also practiced another scene: Ariel's first conversation with Smoke from Chapter 2. No one suggested that scene, but it's one of the last scenes I wrote, so I personally haven't read it a million times and gotten tired of it. I abandoned this idea after a test reading because it's really hard to do a dramatic reading of a chat log, especially when most of the characters have insanely long names. So, Pôneis Brilhantes it was.

However, shortly before the reading I learned that Anne and I were each going to be reading two excerpts! Uh-oh. On the spur of the moment I chose to read a scene I had never practiced and that only one person (Adam) had suggested: the scene from Chapter 11 where Ariel meets Tetsuo and Ashley and they go visit the moon.

That scene has three good points: a) it introduces Tetsuo, increasing the chance that the Pôneis Brilhantes scene would land; b) it's full of the most gratuitous nerd wish-fulfillment I could write; c) it ends strongly with the call from Ariel's mother, which unlike a chat log is very easy to read because it's a Bob Newhart routine where you only hear one side of the phone call.

This was a really good idea. People loved the moon scene, even though my unpracticed reading stumbled and ran too quick. But when I read the Pôneis Brilhantes scene, it wasn't such a great hit! The room wasn't really with me. That's the scene I had practiced, and I think it's the funniest, most incisive thing in the whole book. Not a big hit! I think if I'd only read that scene I wouldn't have sold many books that night.

So, thank goodness for the moon scene, is all I can say. But what was going on? How had I misjudged my audience so badly? Sumana said she'd read Pôneis Brilhantes and gotten big laughs.

I think you have to be a very specific kind of computer geek to find Tetsuo's Pôneis Brilhantes review funny as a review of a video game, rather than as an expression of the personality you've just spent seven chapters with. That's the kind of geek that Sumana and I habitually hang out with, but it's not representative of the SF-reading population as a whole. I think that computer-geek population hosts a lot of the readers who wish that the second half of Constellation Games was more like the first half. Whereas someone who really digs the moon scene is more likely to stay with me the whole book.

I guess you could say the moon scene is just more commercial. And I guess I subconsciously knew this, because my current project gets more of its humor from the plot-driven character interaction found in the moon scene, and less from high concept Pôneis Brilhantes-style set pieces.

[No comments] "Constellation Games" reading: Anne Johnson and I are doing a comedy SF reading on Wednesday at the Enigma Bookstore, a new genre bookstore in Astoria. It starts at 7 PM. The details, as you might expect, are on a Facebook page. Hope to see you there!

[No comments] API Design is Stuck in 2008: I've got a guest post up at ProgrammableWeb with the provocative title of "API Design is Stuck in 2008". Often an author can blame their editor for that kind of title, but no, that's my title. The good news is that over the past few years we have developed the tire chains necessary to get ourselves unstuck.

I don't think there's anything in the article you won't find in the RESTful Web APIs introduction and my discussion of my RESTFest talk, but I wanted to let you know about it and provide a forum on NYCB for asking me questions/taking issue with my assertions.

[Comments] (1) RESTful Web Services now CC-licensed: Hey, folks, I got some pretty exciting news. Now that RESTful Web APIs has come out, there's really no reason to buy 2007's RESTful Web Services. So Sam Ruby and I and O'Reilly have gotten together and started giving the old book away. You can get a PDF from the RESTful Web APIs website or from my now-ancient RESTful Web Services site. The license is BY-NC-ND.

If you've bought RESTful Web APIs (and if you haven't, you should), you may have noticed that we promise that this will happen in a footnote of the Introduction. It took a while to get the contract amended, but now it's all complete.

Here's a direct link to the PDF in case you just want to grab the book instead of hear me talk about it.

Obviously I think the new book is a lot better than the old book, but the old book is still very good. The source code is long obsolete (this is why RWA contains no source code, only messages sent over the wire), but the sections on HTTP still hold up really well. A lot of RWS Chapter 8 went into RWA Chapter 11. With a few edits and additions, RWS Appendix B and C became RWA Appendix A and B. Those are the only bits of RWS that I reused in RWA.

From my vantage point here in 2013, my main critique of RWS is that it makes HTTP do too much of the work. It focuses heavily on designing the server-side behavior of resources under a subset of the HTTP protocol. I say "a subset" because RWS rules out overloaded POST ahead of time. You don't know what an overloaded POST request does. It's a cop-out. You're sweeping something under the rug. It's better to turn that mystery operation into a standalone resource, because at least you know what a resource does: it responds to HTTP requests.

In retrospect, RWS is that way because in 2007 hypermedia data formats were highly undeveloped whereas HTTP was a very mature technology. Nowadays it doesn't matter so much whether an HTTP request uses POST or PUT, so long as a) the state transition is described with a link relation or other hypermedia cue, and b) the protocol semantics of the HTTP request are consistent with the application semantics of the state transition. That's why RWA focuses on breaking down a problem into a state diagram rather than a set of static resources.

So, RWS is very much a 2007 book, but that's the meanest thing I can say about it. A lot of it is still useful, it's historically interesting, and I'm glad to give it away. I'd also like to give my thanks once again to Sam Ruby and O'Reilly, for their work on RWS.

[No comments] September Film Roundup: I missed a whole lot of museum movies in September because I was out of town for two weekends. And yet I still managed to see nine movies, plus wrap up a TV show, and write a huge blog post about it. Wonders, or at least me writing about them, will never cease.

What's up for October? More Howard Hawks, it looks like. See ya then.

[No comments] Beautiful Soup 4.3.2, and all previous versions: Through long practice I'm able to write decent code while I'm sick, but I should not try to release code while I'm sick. While putting up the release of Beautiful Soup 4.3.2, I accidentally deleted the entire beautifulsoup4 project on PyPI and had to recreate it manually. I've given PyPI all the crummy.com tarball URLs for releases going back to 4.0.1, and I've installed each one via pip to verify that it works, so if your build process depends on installing a specific version of Beautiful Soup 4 via PyPI, it should still work. And indeed, random versions of BS4 have been downloaded about 200 times since I switched over. I'm sorry about this screwup. Let me know if there are any remaining problems.

4.3.2 itself is a pretty minor bugfix release. Still left unfixed is a bug I can't reproduce because the federal government is shut down. When you file a bug that happens with a specific web page, please provide the HTML of the web page, not the URL.

Smooth Unicode: For reasons of his own, Adam Parrish recently created the Unicode Ebooks Twitter bot. I offered some helpful suggestions for improving the visual appeal of the Unicode Ebooks, suggestions which Adam mocked as unworthy of his artistic vision of dumping a bunch of line noise onto Twitter every five minutes.

So I created my own Twitter bot: Smooth Unicode, the Lite FM to Adam's unending Einstürzende Neubauten concert. My bot does its best to construct aesthetically pleasing output by combining scripts that complement each other visually. The code is part of olipy and I'll be adding to it as I come up with more nice-looking ways to present gibberish.

Less talk. Less noise. More browser-visible glyphs. That's Smooth Unicode.

[Comments] (2) LCODC$SSU: At RESTfest last week I put on an old Mozilla shirt and my Al Gore campaign button and gave a talk from the year 2000: "LCODC$SSU and the coming automated web". I'll link to video when it goes up on Vimeo, and I'll also point to my five-minute talk about ALPS, which not only took five minutes to deliver, it took five minutes to put together.

But right now, there's some more stuff I want to say about "LCODC$SSU", and some stuff I couldn't say in the talk due to the framing device.

When I first mentioned this talk to Mike Amundsen, he told me about Bret Victor's talk from 1974, "The Future of Programming", which Victor gave in July and which had a similar conceit. Victor is also a much better actor than I am, but I went ahead with my talk because wanted to do something different with "LCODC$SSU" than happens in "The Future of Programming". I get a strong "You maniacs! You blew it up!" vibe from Victor's talk. And there's some of that at the end of "LCODC$SSU"—I really feel like we've spent thirteen years making five years worth of progress, as you can see from my frustration at the beginning of "How to Follow Instructions"—but I also wanted to do some new things in my talk.

While writing Appendix C of RESTful Web APIs I came to appreciate the Fielding dissertation as a record of the process used to solve an enormous engineering problem. Comments from RESTFest attendees confirm that seeing it this way helps folks grasp the dissertation's gem: the definition of LCODC$SSU (a.k.a. REST). Thinking about it this way doesn't require a historical-fiction framing device (Appendix C has no such framing device), but it does require you stop treating the Fielding dissertation as a prescient guide to the 21st century and see it as a historical record of the 1990s.

And once you do that, the missing stair we've been jumping over or falling through for thirteen years becomes visible. The Web works because it has four domain requirements that reinforce each other: low entry-barrier, distributed hypermedia, extensibility, and Internet scale. But there's also a fifth implicit requirement: the presence of a slow, expensive human being operating the client and making the final call on every single state transition. In the talk I identified the inverse of this implicit requirement as an explicit requirement: "machine legibility". In RESTful Web APIs we use the term "semantic gap" to describe what happens when you remove the implicit requirement.

Making the human unnecessary on a transition-by-transition basis (the goal of "Web APIs" as a field) is a really difficult problem, and it's partly because of the phenomenon I describe in the talk and in RWA Appendix C. Getting rid of the human raises the entry-barrier dramatically. Looking around for a cheap way to lower the entry-barrier, we decide to get rid of distributed hypermedia. But distributed hypermedia is the only thing that allows Internet-scale and extensibility to coexist! We must lose one or the other. We end up with an increasingly ugly system that can never be changed, or else a fascist dystopia.

And here's the bit I couldn't put in the talk because it would break the framing device. We've seen a decade-long obsession with lowering entry-barrier at any cost, and although the cost has been enormous I can't really say the obsession is misplaced. Low entry-barrier is the main reason why the Web succeeded over all other hypermedia systems. Low entry-barrier drives adoption. You get adoption first and you deal with the other problems (which will be enormous) down the road.

Well, we're down the road. The bills are coming due. If we want this to go more smoothly next time, we need to stop chasing entry-barrier local minima and come up with a better solution. We need to make change easier so we can make progress faster.

The "machine legibility" problem will still be very difficult, and frankly I can't see a way to a complete solution. But there's cause for optimism: every step forward we've taken so far has illuminated the space a little more and made the next step visible.

It's always been this way. That's how hypermedia works. That's why I called my now-infamous 2008 QCon talk "Justice Will Take Us Millions Of Intricate Moves" (after William Stafford), and that's why I take my motto from a Johnny Cash song that's probably not on most peoples' list of inspirational Johnny Cash songs.

I built it one piece at a time.

RESTful Web APIs Monkeypatch: The RESTful Web APIs ebook came out earlier than we thought it would, and there are some important URLs in the book that don't work yet: the home page at restfulwebapis.org, and the example application at youtypeitwepostit.com. There's also one URL in the book (the book's GitHub repository) that will never work, because we wrote down the wrong URL.

I've submitted an erratum for the wrong URL, and I'm here to give you some temporary URLs that will work for the other stuff. They're temporary because Mike controls the DNS for restfulwebapis.org and youtypeitwepostit.com, and he's out of commission at the moment.

Awesome Dinosaurs Update:

  1. On Sunday I saw the 1926 Howard Hawks film Fig Leaves. I'll publish a full review in the roundup at the end of the month, but I couldn't wait to mention the dinosaurs! This movie (briefly) features two very cool-looking puppet dinosaurs. There's Adam's pet Apatosaurus, named Dobbin:

    Exactly as depicted in Genesis 2.

    More amazingly, there's also a budget-busting life-sized Triceratops that pulls a bus!

    Awesome! Not gonna spoil the review, but the first reel of this movie used all the good Flintstones jokes, thirty-four years before The Flintstones even premiered. Except for the unfortunate bus dinosaur saying "It's a living." in a morose voice. And I'm sure that's just because the joke would be really awkward if you had to do it with title cards.

    (Screen image simulated.)

  2. If you share my belief that dinosaurs are the most interesting part of any movie that includes dinosaurs, you'll love Kevin Maher's deleted scene from King Kong.
  3. A recent Ureddit course on narrative structure in short fiction used "Let Us Now Praise Awesome Dinosaurs" as one of its example stories. I thought this was a) a good choice, and b) pretty funny, because I deliberately wrote "Dinosaurs" to be opaque to traditional analyses of narrative structure.

    If you'll forgive me being serious about a very silly story, here's what I mean. Nearly every plot event in "Dinosaurs" is a red herring. It's actually a New Yorker type story, in which a series of insane infernokrusher interventions leads to Entippa's epiphany that humans are exploiting dinosaurs' tendency to get involved in insane infernokrusher interventions for their own entertainment. (Those humans including, in a bit of Hitchcock-type moralizing, you for reading the story and me for writing it.)

    I wrote the first scene to have something very close to a literal Chekhov's gun. It's Tark's gun, or at least his desire for a gun. Later on, Chekhov's gun goes off: Tark gets his gun! But as soon as the literal gun goes off, Tark discovers that literal guns are loud and painful, and he throws it away. The Chekhov's gun was fake. Sort of like the keys in my old text adventure Degeneracy, which don't unlock anything—you're supposed to melt them down for the metal.

    But! In the Reddit thread dissecting "Dinosaurs" and the other example stories, the person running the class proves my intellectual superior. It turns out there was also a real Chekhov's Gun in that first scene: Tark's "killing claws", which are in fact used to kill someone later in the story, just like they would in a regular story about dinosaurs killing humans.

    I didn't even notice that. I'd assumed the human-killing scene worked because everyone knows meat-eating dinosaurs have claws. I didn't even realize I'd made a big deal about the claws in the first scene. You win this round, literary analysis!

PS: Never forget.

[Comments] (2) RESTful Web APIs!: After about a year of work, my and Mike Amundsen's new book RESTful Web APIs is going to the printer. It's a replacement for RESTful Web Services, a book that's now seven years old. The replacement may be overdue, but it's only been in the past couple years that technology and attitudes have advanced to the point where I could write the book I wanted to write.

In fact, there's one subfield (profiles) where you could argue this book is premature. The way RESTful Web Services was a little premature in describing an OAuth-like system before OAuth was released. But I don't think we can wait any longer.

Back in February I discussed the differences between APIs and Services. That hasn't changed much, though we have added more stuff:

This post is mainly my way of asking you to pre-order your copy of RESTful Web APIs through my O'Reilly affiliate link. That's a hypermedia-driven change in resource state which will get you the book in a couple weeks, and get me some extra cash. (I estimate about $1.70 extra. Don't do this if the shipping charge on a physical book is prohibitive, or whatever.)

But this post is also a back-door way for me to brag about what a great book Mike and I have written. You don't have to take my word for it. Here's the blurb we got from John Musser of ProgrammableWeb.

A terrific book! Covers a lot of new ground with lots of valuable specifics.

Here's Steve Klabnick of Designing Hypermedia APIs:

The entire time I read this book, I was cursing. I was cursing because as I read each explanation, I was worried that they were so good that it would be hard to find a better one to use in my own writing. You will not find another work that explores the topic so thoroughly yet explains the topic so clearly. Please, take these tools, build something fantastic, and share it with the rest of the world, okay?

You get the picture. I've tried to recreate the relevatory experience a lot of people got from RESTful Web Services, on a higher level, in a way that gives access to more powerful tools. Time will tell if I've succeeded, but I don't think I, or anyone, could have done much better. I'm really proud of this book, and I hope it helps you.

August Film Roundup: Not the blockbuster month as I was anticipating—I missed all of the museum's big-name Pacino/de Niro movies due to other committments—but a lot of interesting movies, and movies that were uninteresting in interesting ways, among the nine I did see.

This month and next the museum is showing every film Howard Hawks ever made, so search for his name on IMDB and prepare for the Cary Grant-fest. SEE IT BIG is also returning, and I'm looking forward to seeing the Howard Hawks Scarface on the 21st and then the Brian De Palma Scarface on the 22nd.

[Comments] (1) July Film Roundup: Oh man. As promised last month, July was an epic month of moviewatching, and I decided to try a little epic experiment with this roundup, inspired by the "The Balcony is Closed" game on No More Whoppers. For every movie I saw in July, I came up with a nonobvious connection between that movie and every other movie I saw in July. For instance, if I saw both Die Hard and Live Free or Die Hard, the connection between them would of course be "fresh-faced hacker".

I saw nine movies over the course of the month (well, eight and a half), and by the end this exercise became kind of ridiculous, as I strained to remember obscure aspects of earlier movies. But I knew it would become ridiculous, so when it did, I had no standing to complain. Here we go:

This month the museum panders to me with a festival of classic crime and grime. New York in the 1970s: a lousy place to live, a great place to make a movie about. Looking forward to seeing films like Cotton Comes to Harlem, Serpico, Superfly, The French Connection, and Across 110th Street. We'll probably also catch some Wong Kar-Wai. I will not be repeating July's movie connection experiment.

Correction: "I'd never seen an Altman film before" is one of the least accurate claims I've ever made. I've seen Gosford Park, The Company, and A Prairie Home Companion. And I've probably seen M*A*S*H, given how often they showed it on Comedy Central back when I was in high school. But I came out of all those films thinking "that was good/terrible/okay", whereas I came out of Nashville thinking "No wonder this guy's a legend!" It was like watching a whole nother director.

Loaded Dice 2013 Update: I fetched the BoardGameGeek data again, a yearly tradition, and put up another Loaded Dice update.

A few highlights:

If you go to the main page, you can download an amazing 17-megabyte JSON dump of BGG data I've compiled. It includes descriptions and genres for every game in the dataset, and three data samples that convey historical rating data over three years. At this point I feel like I'm adding enough on top of what the BGG API can give you (the historical rating data) that I can make the data dump available without apology.

Apo11o ll: To celebrate the anniversary of the first moon landing, I packaged up a project I came up with a while back: Apo11o ll, a generative piece that performs Queneau assembly on the Apollo 11 transcripts (from The Apollo 11 Flight Journal and The Apollo 11 Surface Journal).

Duke: Rog. [Long pause.]

Armstrong: That's one small step for (a) man; one giant leap for mankind.

McCandless: Roger, 11. I have a T13 update for you. AOS Tananarive at 37:04, Simplex Alpha. Readback. If you want to go that way, crank it up, and then you can drive it around and look where you want. Over. 11, this is Houston. And we copy the VI.

Aldrin: Does it look to you like the [garble] the right way? Yes, they were working out - this elaborate scheme.

Collins: Unless you'd rather sleep up top, Buzz; I like - you guys ought to get a good night's sleep, going in that damn LM - How about - which would you prefer? I say the leak check is complete, and I'm proceeding with opening the hatch dump valve.

Aldrin: That enough?

McCandless: Apollo 11, this is Houston at 1 minute. Over.

First Mashteroids and now this? How am I doing all this Queneau space-magic? The answer is simple: Olipy, my library for artistic text generation (focusing on Queneau assembly, because it's the best). Check it out of Github and you'll have everything you need to create home versions of many of my works. It's like my own personal Boîte-en-valise! Want to create something new? Just grab some data and feed it to an Assembler class.

Reunion: I got a misdirected flyer in the mail inviting Leon Richardson to a high school reunion. Class of 1983. I was not yet in kindergarten in 1983, so I thought I might go and drop hints about the youth serum I'd invented.

On the other hand, the invitation is addressed to "Richardson Leon, or current resident". So I can go as myself. Anyone can show up to this high school reunion! They don't care!

In fact they're probably hoping a few current residents will show up to boost the numbers. The flyer seems acutely aware that high school reunions are increasingly an anachronism in this world of "Facebook, Twitter, and Smartphones", and is really desperate to prove the worth of in-person reunions.

It also informs me that "The bio-sheet deadline is Friday, August 30, 2013." Interestingly enough, that's also what a supervillain recently told the United Nations.

[Comments] (4) Billy Collins, Stand-Up Comic (Bonus: How To Write Poetry): For reasons that need not concern us, I recently gave some advice on writing poetry. I don't know anything about poetry, but I was able to derive the most basic advice from first principles: "read a whole bunch of poetry before you try to write some." Adam Parrish knows more about poetry and offered some poetry-specific advice: "get over yourself".

I think a lot of incipient poets get caught in the idea that poetry is somehow about free self expression, and that the best poetry is that which most freely expresses the self—which, of course, isn't true. Poetry is a genre that you have to be literate in and a toolbox that you have to learn how to use.

If reading a bunch of poetry is too much work for you, you should at least take the time to reverse-engineer the findings of this paper by Michael Coleman (also via Adam), which uses machine learning to model the differences between poems written by members of the Academy of American Poets, and poems written by the general public. It gives some clues as to how the genre works and what's in the toolbox. e.g.:

The negative association with the PYMCP variable ‘Rhy’—a proxy for the extent to which words elicit other words that rhyme with the stimulus word—indicates that professional poets use words that are somewhat unusual but not necessarily complex. Professional poems have fewer words denoting affect but more words denoting number. Professional poems also refer less to the present and to time in general than amateur poems.

Run your stuff through Poetry Assessor until you start getting good scores. Now you're a poet! Well, sort of. The machine-learning algorithm can reliably tag crappy poems as crap, but it mainly looks at vocabulary and I don't think it knows about scansion at all. I ran the first paragraph of Bleak House—three ponderous Victorian sentences—through Poetry Assessor and it got a 1.8, making it a decent twentieth-century American poem. (And it's a very good paragraph, but you see the problem.)

I formulated my "read a lot of poetry" advice because that was also the techinque I used to figure out if I had any more specific advice to give. (I don't.) While reading a lot of poetry, I got really into the work of former US Poet Laureate Billy Collins. Collins has written a number of what I would call "NPR poems", poems that you could imagine him reading aloud on NPR, some of which he probably did read aloud on NPR. He's on NPR a lot. And at first glance the NPR poems have more in common with stand-up comedy than traditional or contemporary poetry.

I think it's best to think of the narrator of a Billy Collins poem as a fictional poet named "Billy Collins", a man whose bouts of incompetence and perpetual lack of inspiration are exploited by the real-world Billy Collins. Stand-up comics do the same thing. I became very interested in how Collins is able to use this persona to do serious poetic work through poems that aren't serious at all—again, something analogous to what a good stand-up comic does.

Some examples. I'm gonna start with Cheerios and Litany, two poems I don't really like. These poems are about as confrontational as Billy Collins gets, but it's not because of their subject matter: it's because they're poetry hacks.

"Cheerios" has a Poetry Assessor score of 0.8--barely professional quality. In "Cheerios" the incompetent poet "Billy Collins" keeps trying to launch a flight of poetic fancy using the overwrought abstract language associated with amateur poetry: "stooped and threadbare back", "more noble and enduring are the hills". But he can never get it off the ground because the engine keeps stalling on concrete imagery--the objective correlatives associated with professional poetry. The problem with that is the concrete imagery consists of nothing but different breakfast foods ("waited for my eggs and toast", "that dude's older than Cheerios", "illuminated my orange juice"). So it's deliberately bad amateur poetry interrupted by deliberately bad professional poetry. Just saying it's a bad poem isn't enough. It's bad in a very interesting, bathetic way.

On the other hand, "Litany" has the incredibly high Poetry Assessor score of 4.4. (The maximum score given in the Coleman paper corresponds to a PA score of 5.2.) What's his secret? Collins spends the entire poem blasting out objective correlatives at high speed. Some of them are taken directly from other poems ("the crystal goblet and the wine"), some of them are allusions ("the plums on the counter", "the burning wheel of the sun"), some are original ("the boat asleep in its boathouse"). But as he shoots those images out, he classifies them, like he's working on an assembly line, or brainstorming the poem he will eventually write. "Litany" is the opposite of "Cheerios". Collins is hacking the part of your brain that evaluates poetry, pushing all your buttons with free-floating imagery. It's a bad poem because you don't know enough about the people in the poem to understand what the imagery means.

Some other NPR poems, arranged roughly in ascending order of seriousness:

Pay special attention to "Another Reason Why I Don't Keep A Gun In The House" and "Nostalgia", two hilarious poems that are literally highbrow stand-up comedy. "Gun" is Seinfeld-esque, employing the tricks of modern poetry to take an exasperating everyday situation and blow it up into series of escalating fantastic images. (In case you were wondering, its Poetry Assessor score is 2.2, squarely on the "professional" side.) "Nostalgia" (1.3) is more of a Steve Martin kind of comedy, presenting logically flawed arguments and the dumb things people say when they're arguing on autopilot.

"Nostalgia" escalates not to a punchline--a funny kind of absurdity--but to a reductio ad absurdum, a logical absurdity. That makes it a good transition to two Collins poems that, although they deal with ephemeral topics, are more serious and less jokey. They both deal with words, the relationship between words and reality, and the fact that we're always putting words into boxes that themselves have no relationship with reality:

"First Reader" (2.9) is my favorite Collins poem. I feel like "American Sonnet" is the most professionally composed of his poems, and Poetry Assessor agrees, giving it the highest score (3.2) of any of the poems I tested. (Apart from "Litany", which is a poetry hack.) I tried writing down some analysis but these two are easy poems to appreciate, so I'll spare you. I want to close with two poems that I'm not crazy about as a whole, but which do a really interesting thing in the last stanza: they anthropomorphize individual words.

"Paperwork" shows fictional poet "Billy Collins" not being able to write a poem, dreaming in the end of gaining inspiration from an "ancient noun who lives alone in a forest." "Thesaurus" is all about anthropomorphizing words, but it's not until the end that the words leave "the warehouse of Roget" and take on independent lives, "wandering the world where they sometimes fall/in love with a completely different word."

Anthropomorphizing words is how Collins deals with the fact that poetry is a lonely business: writing things down all day, making sure to use exactly the right word all the time. Who else needs to be that careful about individual words? Stand-up comics, that's who. A punchline and a poem both rely on an unexpected word at exactly the right time. That word, when it comes along, is your best friend.

PS: Minor error in the Coleman paper which confused me when I was trying to convert between the paper's scores and Poetry Assessor scores.

For example, Robert Hass has two poems in the corpus, The Image and Our Lady of the Snows, which score in the high to very high range of .72 and .94, respectively.

Those numbers should be reversed. "The Image" has a score of .94 (PA: 5.2), and "Our Lady of the Snows" has .72 (PA: 1.1)

Mashteroids: As my birthday present to you, I present Mashteroids, Queneau assemblies of the IAU citations for minor planets. This showed up briefly on NYCB two years ago, but I've expanded the dataset, improved the sentence tokenization, and created a platform for future Queneaux.

A few samples:

Boltebshon

Robert Shelton (b. 1948), nineteenth president of the University of Arizona, chaired the Keck Telescope Board from 1997 to 2000. The book promoted the Copernican system and became a best seller. Besides his scientific work, he is also the author of the well-known popularizations A Brief History of Time and Black holes and Baby Universes and Other Essays.

Blulinkury

Named for the province of New Zealand on the eastern side of the South Island. He published his first story in Pilote magazine in 1972 and his first album in 1975. He has written several papers on the history of optics.

Junkumi

Junttura embodies the Finnish mentality to get things done, stubbornly and at all costs. He is also an authority on the poet and novelist Kenji Miyazawa and currently directs the museum at the Kenji Miyazawa Iihatobu Center. "Miminko" is Czech word that expresses the unique stage of innocence at the beginning of human life.

You also got an RSS feed.

June Film Roundup: I guess the theme of June was mixing fact and fiction? I dunno why I feel the need to come up with a theme for all the random movies I watched in a month. This thing is long enough as it is. Here you go:

July is gonna be a huge month at the museum, as their theme for the month is "The American Epic". Movies that might show up in next month's review include Citizen Kane, The Grapes of Wrath, Do The Right Thing, Reds, The Right Stuff, Nashville, There Will Be Blood, and The Night of the Hunter. I'm tired already!

The Interesting Parts: I've wanted to write this post for a long time, so long that the main guy I'm writing about, Iain M. Banks, announced that he had cancer and then died of the cancer. That doesn't really affect what I'm going to write, but it does give it an air of speaking ill of the dead, and it just sucks in general.

The Banks novel I read most recently was The Algebraist, and it was a mixed bag for me. The epic scope of Banks's imagination has always been a big inspiration to me as a writer, but The Algebraist is dominated by Banks's "normal human" characters, who channel that epic scope into activities I have always found really boring. I mentioned this in my commentary for "The Time Somn Died", and I assumed it was a side effect of the fact that there's just nothing to do in the Culture. But The Algebraist isn't a Culture novel. Its "normal human" characters don't sit around all day being post-scarcity. I'm just not interested in most of what they do.

Fortunately, eventually the spectacle and the aliens spin up and save the book. I speak mainly of the Dwellers, aliens who make their way onto my list of SF favorites for the way they combine Bertie Wooster joie de vivre with a complete disregard for the value of individual lives, including their own. Great stuff. I loved it. Colonel Hatherance: another awesome alien.

(The other flaw in The Algebraist is one I am perhaps too quick to notice in other writers. There's a puzzle, and a solution to the puzzle, but no explanation as to how the solution--which, by necessity, can be explained in a few paragraphs to a reader who's only been immersed in the universe for a few hours--has evaded all the in-universe people who've been desperately trying to solve the puzzle for thousands of years. That has nothing to do with this post, but I thought I'd mention it because it's a tricky problem, and if you start looking for it you'll see it a lot.)

After Iain M. Banks's The Algebraist, I naturally turned my reading eye to A History of Engineering and Science in the Bell System: Communication Sciences (1925-1980), by Iain Banks. No, just kidding. It's a corporate history published by Bell Labs in 1984 to keep track of all the stuff they'd invented over the years. My copy used to be in the library of the Union Presbyterian Seminary in Virginia--not sure why they had a copy in the first place.

You might think these two books have nothing in common, but one commonality was clear as soon as I cracked the latter tome: they both start out super boring.

Unlike The Algebraist, A History of Engineering and Science... is boring most of the way through. There's a lot about switched telephone networks, radio and fiber-optic cables. That's actually why I got this book; I wanted to do research for an alt-history story about phone phreaking. But the details were so dry I'm either gonna give up on the idea or just read Exploding the Phone instead. Here are the interesting parts of that book:

Hopefully you see the problem. Nothing about those quotes, or about stereograms or classifying two-person relationships, is intrinsically more interesting than the stuff about circuit-switched telephone networks. It's all subjective. When I reached Chapter 9 of A History of Engineering and Science... I had the feeling of encountering the Dwellers in The Algebraist. "At last, this is my chapter!" But there's obviously an audience for that earlier stuff. I'm just not it. So... there must be people who really enjoy the human-centric parts of The Algebraist, right? Perhaps those people even enjoy the human-centric parts of the Culture books?

What madness is this? I knew that interestingness was subjective for nonfiction. As the author of a novel about alien video games, I am familiar with the idea that a reader might decide a novel is just not their thing. But it had escaped me that the same logic might apply within a novel. This made me re-evaluate the parts of Banks I don't like. However, I came to the same conclusion: I still don't like them, and I'm gonna try to avoid writing that sort of stuff. But it's not so strange anymore that there'd be an audience for it.

Last week I went to the Met and checked out an exhibit of prints from the Civil War. There's a Thomas Nast print from Harper's called "Christmas Eve", divided into two halves: the woman at home with the kids on Christmas Eve, praying for her husband, and the soldier in camp looking at a picture of his wife. It's a moving piece but at first glance there's not much to distinguish it from other "war sucks" pieces of the time.

But if you look in the left and right corners of the print, you'll see Santa Claus with his reindeer. On the left he's climbing down the chimney, and on the right he's driving through the camp, tossing out gifts. The cover for the same issue of Harper's shows Santa giving toys and socks to Union soldiers. These prints are the origin of the modern image of Santa Claus.

Nast first drew Santa Claus for the 1862 Christmas season Harper’s Weekly cover and center-fold illustration to memorialize the family sacrifices of the Union during the early and, for the north, darkest days of the Civil War.

Which are the interesting parts? How do you tell?

[Comments] (1) Sycorax Transcends Your Puny Version Numbers: Last night I'd finally had enough with all of my Twitter bots not working due to sending POST requests to a resource that was 401 Gone. The one I really need to keep going is Frances Daily, and that one's on break right now because the planner page for June 1988 was unfortunately missing. But we're running out of June, so I fixed it.

To do that I had to fix Sycorax, the way-too-advanced piece of software that enacted an elaborate running commentary during the serialization of Constellation Games, a commentary that about eighty people saw. Since I'm pretty sure I'm the only person using Sycorax, I've decided to stop doing a tarballed release every time I change something, and just put the code up on Github.

Robot roll call!

The robot in the shop is @RoyPostcards, which I'll fix around the same time I get some more postcards ready to put up.

Update: @CrowdBoardGames prayed for a friend, and he came! His name is Timmy!

[Comments] (2) May Film Roundup: Lots of travel in May, so not many movies this month either. But I do have heterodox opinions for you. Read on!

Beautiful Soup 4.2.0: My work on RESTful Web APIs is pretty much done, so I went through the Beautiful Soup bug tracker and fixed everything I could. The result is a new, stoner-iffic release of Beautiful Soup.

Here are the release notes. The main new features are a much more capable CSS selector engine, and a diagnostics module that should help with tech support.

Story Bundle: Constellation Games is featured in the current video game-themed StoryBundle. It's a pay-what-you-want, like the Humble Indie Bundle. This means that if you're the ultimate cheapskate, you can get my book and six others for the Steam-sale-level price of three bucks. Pay ten bucks, and you also get three bonus books, including Jordan Mechner's "The Making of Prince of Persia and a Ralph Baer memoir which--just guessing here--is probably enjoyably cranky.

And for people who discover Constellation Games based on this bundle, this is my occasional notification that there are tons of free extras: four bonus stories, in-character Twitter feeds, and an episode guide with commentary.

Side note: the bundle was assembled by Simon Carless, who is the reason I wrote Constellation Games in the first place.


This document (source) is part of Crummy, the webspace of Leonard Richardson (contact information). It was last modified on Monday, September 09 2013, 18:05:52 Nowhere Standard Time and last built on Monday, October 21 2013, 18:20:04 Nowhere Standard Time.

Crummy is © 1996-2013 Leonard Richardson. Unless otherwise noted, all text licensed under a Creative Commons License.

Document tree:

http://www.crummy.com/
Site Search: