The Atlantic, Fiction 2010, and How to Write in 700 Easy Lessons

The Atlantic‘s fiction issue showed up this weekend and has, as usual, some fascinating material—most notably How to Write in 700 Easy Lessons: The case against writing manuals, which argues that books that teach you how to write like writing is an exercise in carpentry aren’t a good way to actually learn how to write. As he says:

The trouble of course is that a good book is not something you can put together like a model airplane. It does not lend itself to that kind of instruction. Every day books are published that contain no real artfulness in the lines, books made up of clichés and limp prose, stupid stories offering nothing but high concept and plot—or supra-literary books that shut out even a serious reader in the name of assertions about the right of an author to be dull for a good cause. (No matter how serious a book is, if it is not entertaining, it is a failure.)

The real solution for writers? Reading:

My advice? Put the manuals and the how-to books away. Read the writers themselves, whose work and example are all you really need if you want to write. And wanting to write is so much more than a pose.

Note that he makes a distinction between books that deal with the craft of writing or the aesthetics of writing (“we have several very fine volumes in that vein (Charles Baxter’s Burning Down the House and John Gardner’s The Art of Fiction come to mind”), but rather the books that act like you’re merely laying down two by fours (think of the old wheels that allegedly helped writers by things like “heroine declares her love”).

The books I offered in The very very beginning writer are geared toward the craft/aesthetic approach, not the model airplane approach, although I admit that I’ve ready some of the ones using the model airplane approach and promptly gone back to studying characterization with Robertson Davies, plot with Elmore Leonard, and depth with Francine Prose. D.G. Myers said, “I do not believe that anyone can learn to write fiction from a guidebook […]”, and he’s right. But I think that many if not most artists benefit from reflecting on their craft, especially when they’re learning it, and there’s a difference between guidebooks and ones that help shape fundamental skills, rather than merely giving a formula or recipe.

Some of the fiction in the issue is excellent too: The Landscape of Pleasure is fascinating for its half-knowledgeable narrator in the late adolescent mold, and T.C. Boyle’s The Silence almost ends with “And what was its message? It had no message, he saw that now,” a statement that feels deserved in the context.

Melville and the theme of boredom

I’m writing a paper on Melville’s Pierre: or, The Ambiguities, which is slowly driving me crazy (I leave it to the reader to decide whether I refer to paper or book). While searching the library last week, I came across a book whose content has no doubt been contemplated by many a student over the years:

In case you can’t read the spine, it says Melville and the Theme of Boredom. If I hadn’t seen it in a research library, I’d assume the title to be a work of parody.

Tax day links: Gender stereotypes, sexual mores, universities, and more

* Why men don’t listen. Except they do, as this post into the pseudo science of gender brain differences shows.

* “Generation Scold: Why millennials are so judgmental about promiscuity.” Of course, what people say and what they do are still separate, as we know from descriptions of the Puritan practice called “bundling.”

* Why are novels the length they are? And, implicitly, how will technology change that length over time?

* Where professors get their politics.

* Why humanity loves and needs cities.

* A Defense of Abortion is a fascinating thought experiment in moral philosophy.

* On healthcare nationally and in Massachusetts:

When Massachusetts rolled out its coverage program in 2007, many more people signed up for the new heavily subsidized insurance than was originally predicted by budget officials. Almost immediately, costs far exceeded what had been budgeted, forcing state officials to scramble to find cuts elsewhere in government and other sources of revenue.

After three years, no real progress has been made on rising costs. The program remains well over budget, with no end in sight. Further, state residents who now must buy state-sanctioned coverage are bristling at their rising premiums and the inability to find coverage which covers less and thus costs less.

* Along the same lines as above: For every doctor, there are five people performing health care administrative support. This may be part of our national problem, like the growth of administrators relative to professors in academia. (Hat tip Tyler Cowen.)

* Universities set their prices based on what people will pay. Consequently, they raise their sticker price and then offer discounts to woo top students.

* D.G. Myers’ suggestions for the Library of America, (apropos of the kerfuffle discussed here):

Novelists with large untapped bodies of work, and who are likely candidates, are fewer and farther between, although I would make a case for Stanley Elkin and (less passionately) for Wright Morris. But a two-volume set of New York Jewish novels, including The Rise of David Levinsky (1917), Anzia Yezierska’s Bread Givers (1925), Call It Sleep, and Daniel Fuchs’s Summer in Williamsburg (1934), would be a terrific addition.

Kindle land, with requisite ruminations on the iPad

EDIT: See this comment on my long-term analysis of this generation of Kindle.

James Fallows says that in order to avoid becoming a Kindle bore, you should “Just shut up when tempted to say or write anything about it. Otherwise you’ll be driving people crazy with your enthusing about how useful and convenient it is, and what its potential might be, and how many elegant decisions are evident in its conception and design.” I’m going to violate that right now by enumerating the number of things the Kindle does right and huge, giant thing it does wrong. If this makes me a bore, proceed to the next post.

Things done right: The screen is very, very nice, as is the tactile feel of the device itself. Although notes aren’t as satisfying to write as they are in paper, they work reasonably well and are easily aggregated. Using the “search” feature allows effectively infinite, immediate concordances in realtime. Shopping in the Kindle store is easy, although I think I’ve only bought two books from it because of the DRM.

The most useful thing about the Kindle for me isn’t actually reading books bought from Amazon—I’m reluctant to spend much money on them, knowing there’s a decent chance that in five years I’ll have a different device or won’t be able to transfer the books I buy now. Rather, Marco Arment’s Instapaper makes the Kindle insanely useful. If I find a longish article online, I hit the “Read Later” bookmarklet in Firefox. About once a week, I log into Instapaper and download all those articles on my Kindle. Bingo: I don’t have to keep printing and losing papers and I still get to read everything I want to read.

Things done wrong: The big-time, number one problem with the Kindle is its terrible software for organizing and managing documents. Actually, scratch that: it doesn’t really have software for managing documents.

The Kindle shows up as a generic USB device on OS X. Want to load it with .pdfs? Be prepared to drag them into a folder labeled “documents.” This process reminds me of .mp3 players… before the iPod. This doesn’t bode well for Amazon, especially now that the iPad is out.

The closest third-party app I’ve found so far is Calibre, which is clunky and doesn’t work that well, especially out-of-the-box. It won’t automatically sync to my Kindle at the moment for reasons not abundantly clear to me; it doesn’t have built-in optical character recognition (OCR) for .pdfs; it doesn’t automatically copy things bought off my Kindle to the computer. The list goes on. The difficulty of writing really good, really intuitive software like iTunes is really, really high.

I’m reminded of this post comparing Tumblr and Posterous, which compares those two “reblogging” tools. The basic point: design counts more than technology. At the moment, the Kindle’s technology is impressive. The physical hardware isn’t bad, although the screen should be bigger: there isn’t enough space before I have to scroll. But until iTunes for the Kindle comes along and whisks the searching and sorting problems away, the Kindle is effectively crippled by software.

I’m sure the omission of iTunes-for-the-Kindle is intentional on Amazon’s part: what they really want you to do is pay them money every time you buy a book or convert a .pdf. That’s okay but seems penny-wise and pound-foolish; think of Scott Adams’ complaint about bad user interfaces. At the end he asks, “What is your biggest interface peeve?” I now have one.

In other news, Apple released the iPad not long ago, which virtually every media outlet on the planet has covered. Megan McArdle says of it:

I’m still unsure how the iPad gets around the core problem: it doesn’t replace anything. Buying an iPhone let me take my phone, my camera, and my iPod out of the briefcase. Buying a Kindle let me remove a newspaper, several books, and some documents I have on PDF.

You can see similar comments here.

But if the iPad software is sufficiently better than the Kindle, users might end up chiefly with it.
One should read this article from Paul Buchheit’s blog, in which he notes the three reasons why the original iPod succeeded where others didn’t. It was:

1) small enough to fit in your pocket, 2) had enough storage to hold many hours of music and 3) easy to sync with your Mac (most hardware companies can’t make software, so I bet the others got this wrong).

Emphasis added. The weird thing is that Amazon is getting this wrong right now. Syncing the Kindle to my computer is cumbersome; there isn’t a good program for organizing my books and .pdfs. Charlie Stross writes about why he, a self-described UNIX bigot, uses a couple of Macs, instead of cheaper Linux boxes:

The reason I choose to pay through the nose for my computers is very simple: unlike just about every other manufacturer in the business, Apple appreciate the importance of good industrial design.

(Note: he’s British, which explains the “Apple appreciate” rather than “Apple appreciates.” The Brits think of corporations as plural, we think of them as singular. What would Steven Pinker say?)

I would also add that Apple has fewer and different hassles than running Linux boxes, which I say as someone who had periodic problems with audio drivers and other things in the ~2001 – 2003 range before I gave up. But the Kindle’s hassles are reminiscent of a product that should be better than it is. I’ve drifted somewhat from the main point regarding the Kindle, but the device is one of these “close, but still wrong” items that is somewhat frustrating, much like Linux, the last Volvo I drove, the Ikea desks I’ve seen, and chairs that unsuccessfully mimic the Aeron.

The Kindle is very, very good for English majors who get assigned a lot of pre-1923 fiction (which they can get free online) or for people who like reading from that era and do so voluminously. For the rest of us, it lacks, especially in the nonfiction department, where it’s hard to skip from section to section quickly.

Reading fiction on it is a substantially better experience because I seldom skip long sections in novels—it’s pretty hard to decide an entire chapter should be skipped, since that chapter will usually contribute something important to the story (and, if it doesn’t, the novel isn’t very good). In addition, novels are relatively unlikely to have research citations, which are sometimes important in evaluating nonfiction, especially if that nonfiction makes extensive or dubious claims. Right now, the small amount of nonfiction I’ve got doesn’t come with footnote hyperlinks. It shouldn’t be all that hard to create a style named, say, footnote with an automated number linking it to a later number so that one can jump freely back and forth between them. But that’s rare in the books I’ve read.

Amazon has released a kindle Software Development Kit (SDK), which might improve some of its current problems. But until it solves the “organizing home” problem that iTunes does so well, it’s not going to be a tremendously useful device for me and many other heavy readers who need some way of getting articles to and from the device. That’s a huge missing feature that Instapaper (somewhat) solves, but not well enough. The Kindle is an “almost” device, like many of the “almost” mp3 players before the iPod. But I don’t think almost is enough.

The Library of America and literary canons

Newsweek asks: has the Library of America jumped the shark? If so, you won’t find a good argument for it in this article: there’s a lot of innuendo and little of substance about who deserves to be in the “canon” and why. But the last paragraph gets a (very) little bit deeper:

Kidding aside, one sympathizes with the directors of a publishing venture increasingly dependent on the idea that great American writers just can’t die fast enough. In such a situation, conventional publishing goes head to head with curating, and financial concerns go to war with esthetics, which, depending on how conservative one cares to be, can argue for little or no growth at all. And of course all this plays out against a literary landscape where the idea of a literary canon has been pretty much shot to hell anyway, so maybe no one should care who gets into what anymore. Or maybe they should just turn the whole thing into a—you knew this was coming—lottery.

Shelfari (mostly) agrees with my comments and says:

For me, when the LOA started adding people like Lovecraft, Dick, and Powell (or personal favorite Nathanael West) was when it started getting lively and interesting. I’m glad they do beautiful editions of titans like Lincoln, Whitman, and James, but I’m far more glad that they haven’t just been passive about transmitting the canon, as it was spoken to them from above.

Agreed. I can’t think of anyone I’d love to see included, except perhaps Robertson Davies, who is Canadian (but Canada is part of North America, right?), and Elmore Leonard, who is still alive. Regardless, I’ve been impressed with a lot of the recent picks, like Philip K. Dick, who deserves his spot; tomorrow I’m going to hear a scholarly lecture on his work at the Arizona Quarterly Symposium, and I’ve heard talks on him elsewhere in academic venues. Maybe Jack Vance will be next, although he’s not been as cinematically popular as Dick.

Oh, and one other small note about the LoA: I tend to write in my copies.

How to find books

Apropos of this post on influential books, a reader e-mailed me to ask how to find interesting books to read. My answer: looks for books that are important to people who are smart, and ideally smarter than you. That’s one reason I like the “top ten influential books” meme that’s been going around: it introduces a lot of books I probably wouldn’t have found otherwise.

Other (obvious to me) places: The New Yorker; professors or highly literate friends; the better book/arts blogs, like About Last Night, although you can find others in the sidebar; and author interviews, in which novelists or other writers mention important/influential books. The last one is probably among the most useful because writers, in order to work effectively, have to read almost all the time. As a result, the top few books of the many thousands they’ve read are probably better than the top few of the dozens or hundreds random friends have read. I used to find a lot of books by browsing, either at the library or at used bookstores, but I tend not to find that very satisfying any more.

The problem with books is that you can’t really say whether they’re right for you until you read them, and what’s right for you depends on how much you already know about the subject, taste, what else you’ve read, development, background, and more. So book recommendations are by their nature hard, especially for someone like you, who I (probably) don’t know. I have a few go-to recommendations that many people seem to like—Carlos Ruiz Zafon’s The Shadow of the Wind; Alain de Botton’s On Love; Umberto Eco’s The Name of the Rose; and Robertson Davies’ The Deptford Trilogy are high on that list.

So Many Books: Reading and Publishing in an Age of Abundance discusses how hard the sifting process becomes as more books pile up while time to read remains constant.

Risks, Realizations, and Barry Schwartz’s The Paradox of Choice

People mistook the pervasiveness of newspaper stories about homicides, accidents, or fires—vivid, salient, and easily available to memory—as a sign of the frequency of the events these stories profiled. This distortion causes us to miscalculate dramatically the various risks we face in life, and thus contributes to some very bad choices.

That’s from Barry Schwartz’s The Paradox of Choice: Why More is Less, a book that’s probably easy to misinterpret as arguing that more choices are always bad or always make us unhappy. But it does provide a lot of useful explanation of why many people disproportionately fear crime, which is falling (that link is merely one of the first found in an Internet search; the general trend is well-known), as opposed to, say, car crashes or heart disease, neither of which are as memorable.

Still, I don’t think all choices are bad ones, but the cognitive effort necessary to make a choice should probably make us more wary of doing things like shopping than we, as a society, appear to be. Mental investments in one field (i.e. deciphering features, costs, etc.) might take away from those in another, as cognitive load theory implies. Overall, I think The Paradox of Choice can be usefully combined with a couple of other sources, most notably Paul Graham’s essay Stuff, about the perils of possessiveness in an age of abundance, and The Myth of the Rational Voter, which the New Yorker discusses here. Our (collective) beliefs aren’t very rational, whether you call them a mistake of “pervasiveness,” as Schwartz does, or something else. It’s unfortunate that Schwartz doesn’t go in more depth about the “very bad choices” we might make as a result of availability heuristics.

Tender is the Night — Fitzgerald

Early in Tender is the Night, we find this about a relatively minor character named McKisco:

“I don’t see what it’s all about,” he said helplessly. “I don’t see why I’m doing it.”

The context is a conversation putatively about duels, but one could take McKisco’s confusion as a synecdoche for the novel as a whole: no one see what it’s all about or why they’re doing it. Even Dick Diver, psychologist, doesn’t really; he’s supposed to have mastered the mind but hasn’t mastered his own. Some of the novel’s descriptions and transitions mirror this confusion or uncertainty, which makes Tender is the Night feel more Modernist than its predecessors. Take, for example, this:

When there were enough Americans on the platform the first impression of their immaculacy and their money began to fade into a vague racial dusk that hindered and blinded both them and their observers.

The description goes from a relatively literal rendition of the Americans’ surface into a metaphoric one of their souls. But I have no idea what “vague racial dusk” means, which is perhaps why it needs “vague” out in front, or why that would blind observers; perhaps those theoretical observers are used to judging based on categories that Americans defy, or think they defy. If so, the novel is a journey into the ways Americans are more ensnared by history than we might want to be, and why we might be more obscure than we’d like to imagine. In this way, the structure of the novel mirrors its themes: it cuts many of the “she shifted her attention to the fight” transitions that might otherwise make this easier to follow:

Nicole was glad he had known so many women, so that the word itself meant nothing to him; she would be able to hold him so long as the person in her transcended the universals of her body.
“Hit him where it hurts!”
“Yah-h-h-h!”
“Hey, what I tell you get inside that right!”

A chorus shouts after Nicole’s Deep Thought, and in re-reading Tender is the Night I see where Tom Wolfe got some of his techniques for representing speech.

Some of the stylistic tics, like the “vague racial dusk” are meant to make us poetically see something in a new light, but they often feel more like work compared to a novel like Gatsby. It feels more indulgent, too: this is Fitzgerald wanting to write a novelist’s novel, meaning that it should have enough strangeness to make it hard to figure out what’s happening and why. This brings pleasures of its own, especially on second reads, but the danger of obscurity for obscurity’s sake remains, as when a voice suddenly shifts from third person limited to first:

All that saved it [the offer of marriage? something else?] this time was Nicole finding their table and glowing away, white and fresh and new in the September afternoon.

How do you do, lawyer. We’re going to to Como tomorrow for a week and then back to Zurich. That’s why I wanted you and sister to settle this […] (166)

My confusion mirrored McKisco’s in this narrative jump. Eventually that confusion was (mostly) remedied, but not so remedied as to make the novel boring.

Continuing was worth it: Fitzgerald knows how to end a novel. Tender is the Night isn’t quite so overtly poetic as Gatsby, with its boats being beaten back into the past, but it has a sense of melancholy and emotion that few novels do. I’m being vague because I don’t know how to describe the feelings evoked; perhaps that is one definition of a powerful novel. Melancholy is a part, but like a good wine, it’s only a single strand of a complex weave, one cannot appreciate the whole without appreciating all its parts.

There’s one other thing that Tender is the Night reminds me of: the habit that literary history has of doubling back on itself. Received opinion—so received that I don’t know where I got it from—holds that people didn’t start really writing about divorce and affairs and torrid sex and so forth until Updike and Roth. Marriages were more stable, at least as depicted artistically, and the really great fireworks caused by social changes didn’t hit until the 1960s. But the more I read the less that narrative seems to fit: Tender is the Night encapsulates Updike’s Marry Me: A Romance and maybe even Couples. Middlemarch has marriages that end. Even Pride and Prejudice has its affair between Lydia and Wickham, although the sex they’re having is so powerful that it remains unspoken.

Madame Bovary doesn’t encapsulate Tender is the Night but at least presages it. The drama of adult relationships, which I’d thought a (relatively) recent invention in fiction, isn’t. Neither is the childishness that such relationships sometimes entail. More continuity exists over the course of history than I thought, and what seems new in terms of content no longer does. Even the style of Tender is the Night holds up: if it were published today, I’d not know the difference. one can see greater stylistic continuity from Fitzgerald to the present than from, say, Middlemarch to Fitzgerald (this is part of what James Wood discusses in his nominal discussion of Chang-Rae Lee’s The Surrendered, a topic that I will return to later).

I don’t know what to do with this idea concerning continuity and change save note its existence, at least in my reading. Perhaps the rhetoric of the love story hasn’t changed that much, except perhaps for the inclusion of overt female desire in a larger number of more recent novels; it’s hard to see a good precursor of Allison Poole in Jay McInerney’s Story of My Life. Poole feels a long way from Nicole Diver, but the feeling of a search for something that cannot be adequately defined continues, and the inability to find that absent something propels novels and stories forward.

Ian McEwan day – Solar released

It’s Ian McEwan day: Solar is out, and reviews are easy to find online, and my copy is supposed to arrive in a day or two. Once it does, the calendar gets cleared, other books get bumped down, and reading commences.

Influential books (on me, that is)

Econ (and generally interesting) blogger Tyler Cowen lists the 10 books that have most influenced him and invites other bloggers to do the same. Here’s mine, in the order I thought them up rather than importance:

1. Tolkien’s Lord of the Rings: I think many people find that their first “adult” books is a powerful influence, and I first read Lord of the Rings in late elementary or early middle school and reread it periodically: its commentary on power dynamics, the limits of knowledge, and the challenge of understanding still affect me. And it makes its way into a surprising amount of otherwise unrelated academic work. And the story. And, and, and…

2. Robert Jordan’s The Wheel of Time and the DragonLance series: Another early influence, this time mostly for the worst: the view of sexuality in both series is juvenile, the writing atrocious, and the mindless glorification of battle and power for its own sake is, from my current vantage, almost sickening. But they now show me what not to do as a writer and thinker and probably contributed to the lost, unhappy middle school years so many have.

3. Geoffrey Miller, The Mating Mind: Robin Hanson recommended this. Its ideas about the role of art and culture in sexuality and why the second half of Darwin’s theory—sexual, as opposed to natural, selection—clarified a lot of my thinking. Even today, many people focus on “natural” selection but miss the importance of sexual selection. I still don’t think I’ve exhausted the book, although I have read others in the genre. Along with some of the books below, it pointed me toward a better understanding of how people signal and how people perceive, which I didn’t understand previously.

4. Dan Ariely, Predictably Irrational: I’d read many critiques of our rationality, but before Predictably Irrational I probably would’ve argued that we should look solely at behavior to discern individual wants and that individuals are independent in an almost Ayn Rand way. Although Predictably Irrational isn’t solely responsible for this shift and others, it probably catalyzed them.

5. Conrad’s Heart of Darkness: By most of the conventional tropes of creative writing classes, Heart of Darkness is terrible. But it reminded me of the power of the unknowable and of the limitations of what we know. The most famous scene is of course Kurtz’s “The horror! The horror!”, but what strikes me in rereadiang it is how little time Kurtz actually gets and how great Marlowe’s anticipation of Kurtz is. The novel is more about how Marlowe perceives (and thinks he will perceive) Kurtz than about Kurtz himself, which taught me the power of how perception shapes reality.

6. Paul Graham’s essays: Although not technically a book, some of Graham’s essays have been collected into Hackers and Painters. I pay special attention to the essays about social structure and the role of the individual in social structures. Some of the ones about school, especially high school, I assign to students.

7. Umberto Eco’s The Name of the Rose: This is the kind of novel that I wish someone had demanded that I read earlier than I did. Claiming that something is the “greatest novel” strikes me as silly, but if I were forced to choose one, this would be in the running and seems like it contains the world as few novels do. Is this vague? That’s because trying to encompass it is beyond me.

8. Robert Penn Warren’s All the King’s Men: This book made me more cynical and hopeful about politics—at the same time. Its style isn’t baroque but tends toward long, beautiful sentences; Jack Burden’s understanding of what actually matters, which doesn’t really occur until the last chapter, is so authentic and wonderful that it seems truer to life than the darker ending of Gatsby. Still, its depiction of sexuality now feels very much of its time, rather than of all time.

9. James Wood, How Fiction Works: Wood asks a critic’s questions and gives a writer’s answers with such precision and beauty that this essentially defines the terms of the novel for me. The last two words of the preceding sentence are essential: the joy of the novel is the inability to define or encompass it.

10. Neil Strauss, The Game: I didn’t love The Game for its stories about pickups, but it has a central, important idea: most conversations in most situations are boring and predictable. Solution: shake things up. Predictability can be boring; in social situations around an attractive person, many people (not just men) get scared, and when they’re scared they become more conversationally conservative, and then fail through excess caution. Chances are, no one wants to tell you where they’re from; ask them for an opinion that elicits interpersonal beliefs instead. Most guys are also poorly educated and socialized around dating, women, and sex. The Game may not be a perfect book but it moves the conversation about dating and sexuality forward in a way that few other books have accomplished. Most of the negative discourse around the The Game doesn’t address the elisions The Game is addressing. If you have a prosocial equivalent of The Game I’d be happy to hear about it.

I’ll stress that I’m not most proud of these books: The Wheel of Time is terrible, some seem like lightweight popularization, others are not books I would necessarily recommend today, or to everyone—but they all did their work. If I could pick an 11th I’d choose Daniel Gilbert’s Stumbling on Happiness, which has several core insights that I try (and often) to fail to apply: money above something like the median household income won’t make us happy; our sex and social lives matter more; and our ability to predict what will make us happy is weak. Robertson Davies continues to be a favorite author because he has perspective in a complicated way I can’t easily define, but he combines much of the best of Victorian fiction with a modern sensibility and style that’s his and yet universal. In the His Dark Materials trilogy Philip Pullman shows how fantasy can be done not just right, but spectacularly well.

Another omission: I wish I could think of an individual book that convinced me dense cities are vital because of their networking effects, environmental improvements, the possibility (seldom achieved) of affordability, and the well-intentioned but wrong preservationist/anti-growth types. I’ve had several arguments with people who are a) pro-affordability, b) anti-sprawl and c) anti-height. You can’t consistently have all those things; a) is most often neglected. Newspaper articles in particular like to pretend these trade-offs don’t exist.

Many others have answered the call for books too, and I find their posts fascinating even though I don’t read most of the bloggers involved. But the books themselves (and the rationale for their influence) point to deeper ideas about how influence works and the serendipity of the right person finding the right book at the right time. Most of the answers are political science- and/or economics-oriented, but a fair amount of fiction crops up.

At some point I’ll also post a list of books that I wish someone had shoved into my hands when I was younger with a demand that I read said books.

EDIT: Julian Sanchez has an interesting meta post about influence, in which he posits that people mean influence in two major ways: on a formal/substantive axis (does it show me how to do something?) and on a theoretical/practical axis (does it show me what I should think/believe?). The distinction seems useful. Most of my list is heavier towards the theoretical/practical level. One thing that I’ve noticed about meta lists is that they very seldom have examples of what not to do—in other words, books that one reacts strongly against.