I've posted a few times about how readers don't pay attention to what they read, and so tend to completely miss the point; this can be incredibly frustrating for writers. It's one thing to be criticized for what you actually wrote, but being criticized for the version of what you wrote that exists in the critic's head is maddening. I include myself among those bad readers, by the way. Like anyone, I can be too self-absorbed to give someone's writing its due.
But I may have never seen a more egregious example of willful bad reading than that by Peter Maass in an article from The Intercept on August 11th. In it, Maass revealed what he claimed were seven editorial columns from the National Security Agency's internal website, written by a working-level translator. The translator's name was known to Maass, allowing him to do some basic research on the NSA employee. Maass dubbed the translator "Socrates" because six of the editorials were supposedly written for a column NSA called "The SIGINT Philosopher." (I will call this translator "Melville" instead of "Socrates," because the writer himself joked about how little Philosophy he had studied.) Maass combined these editorials with what he found on what he believed to be Melville's personal, non-work blog about life as a failed fiction writer to create a composite, conjectural portrait. The picture was not flattering, as the title "What Happens when a Failed Writer Becomes a Loyal Spy?" might suggest.
Maass's eight-page article included long sections on his search for information on Melville--not much of a challenge, as Melville was attempting to be found rather than hide on the internet, and Maass already had a lot to go on from the editorials. Maass played a tongue-in-cheek game of "tell you who he is/not tell you who he is," sharing many paragraphs of detail about Melville's life taken from the blog, including hints about his family, apparently to make the point (already known by everyone) that people can find out a lot about you if they are really determined to, even if you work for NSA. He explained that even if readers managed to decipher Melville's true identity, he had a "get out of guilt free card," because he was certain he had interpreted Melville's editorials sufficiently. As he saw it, Melville wanted the government to collect everything on everybody, because it made us all safer. Maass found irony in Melville's desire to keep his name out of Maass's story, because, after all, hadn't Melville just said that the more others know about you, the safer you are?
Since Maass's decision to provide so much personal information on Melville was entirely built on his certainty of his own interpretation, it's odd he spent so little time actually, you know, reading the articles. He and NPR's On the Media referred unproblematically to Melville's belief in "total surveillance." Nobody seemed to notice that this phrase, appearing in some re-posts of the story in quotes as though it were Melville who said it, is Maass's restatement, not Melville's words. As I'm about to show, it isn't a good restatement.
"Melville's" Actual Writing: What it says and doesn't say
What did Melville actually say? Maass dealt mostly with two of the editorials, so I will look at the same two. One editorial was the first Melville wrote as SIGINT Philosopher. With what looks to be roughly a one-page word limit, Melville attempted to answer the question not--as Maass thinks--of whether NSA should grab all communications on Earth, but whether it is morally acceptable to conduct surveillance on foreign targets who are not clearly "enemies." When Melville first stated work, he had misgivings. He wasn't targeting terrorists or drug lords, but foreign government officials who seemed like good people. They were folks, like Melville, who had taken government jobs because work for one's country seemed like a respectable calling in life and because it enabled them to care for their families. They weren't being targeted for doing bad things; they simply knew information that Melville's employer also wanted to know.
Melville then recalled a moment when he was himself a "target": his employer was re-investigating him for his security clearance at work. He apparently had problems with the polygraph (not an uncommon occurrence, even for those who are telling the truth). He passed a month later, it seems, but in the meantime, he felt depressed while waiting to retake the test after failing it. Sardonically, he listed two wishes he had while nursing his wounds:
1) That he could run away from it all, take his family out onto the prairie of old and live in a mud hut.
2) That his employer would just know everything about him, rather than just the flawed information from a polygraph.
I don't think either with was a real wish. If given the chance, he wouldn't go back to the 19th century and rub elbows with Ma and Pa Ingalls. Neither did he really want his employer to look through everything of his. These were his depressed, illogical thoughts, and they are presented as such. These ideas made sense when he was under duress, but now that he has recovered his equilibrium he is making fun of his own thoughts. He's poking fun at himself, not expressing a true desire. These crazy thoughts do relate to what comes after, but the later thought expresses a different wish than total surveillance.
He drew an analogy between himself as a target and his own targets he eavesdrops on. He wanted to be "complete and competent" in monitoring them. Not to listen to everything they said, but to listen to enough to be "competent," to not misunderstand them, to not misrepresent them based on bunk data, such as the bunk data from a polygraph. He said this was as much for the targets as it was for the Unites States, thinking of the repercussions that can result from a powerful agent that misunderstands an innocent target.
This is what David Hume (I think I have this right) would have called an "imperfect analogy." The two parts of Melville as target and Melville as eavesdropper only partly line up. He had a crazy desire to have the government know everything about him, and it led him to a less crazy realization that his job has meaning when he does it well enough to prevent propagating bad information.
I think Melville made a rather important punctuation error at one point. In a paragraph right after talking about his crazy desires, he began with "This is the attitude I have brought to my SIGINT work since then." That makes it sound like he meant "I've taken this crazy idea of the government knowing everything about me and put it to work." Some commenters have found this so outlandish they have even wondered if this was a mock piece, the NSA version of The Onion. But taking the whole article into consideration, I see it as a simple punctuation error. It should have said "This is the attitude I have brought to my SIGINT work since then <COLON>," thereby tying it to what came after.
This would have made it clear that the actual attitude he adopts is the next phrase: "If we are going to work on targets that fall short of being technically 'enemies' but are rather informative for our policy makers--and we are--then even looking at it from the target's perspective, we are honor-bound to do more and better monitoring rather than less." The more is not on everyone, only on his small set of foreign targets. And it's not infinite; it's only "more" to the extent it leads to "better."
There is a bizarre finale about seeking a "deity-like monitoring of the target." It's a weird, sudden insertion of a new metaphor of the government spy as God and the target as the humanity that God watches. I don't believe this was even Melville's original line. He's an agnostic. He just said the government "does not have godlike powers" a paragraph before that line. I think there might have even been a smiley-face emoticon stuck in there that didn't show up in Maass's version, and I don't think Melville would EVER use one of those outside a text message.
I'd wager that something happened here Maass can probably relate to. Melville had an editor. The editor thought this was a pithy way to wrap up, and Melville, in his first article, didn't feel he could fight too hard. But even if my textual postulations are wrong, and we take the text at its word, it's clear the text is not calling for monitoring "all of us," as Maass put it during his On the Media interview. It's deity-like monitoring of his targets. Those targets are apparently both foreign and few. He seems to have some level of familiarity with them, which would be impossible if he monitored thousands of people. He's a translator, after all. Ever try to translate just one person? It takes a long time.
All in all, I look at this article as a government employee saying that he finds monitoring other people to be a little unnerving, but that he has come to grips with it by determining to do his job competently. The government is going to do it anyway, so it's better for everyone if they at least get the right information. He has developed an ethic of trying to get "more and better monitoring of (his) targets," so that he can pass on information in a "complete and competent" manner.
This is certainly a position that you could still call into question. It does not interrogate many larger issues about the U.S.'s role internationally as a superpower and the effects thereof. I don't think he could have addressed all of this--short word count. In any event, these critiques, though important, are a long way off from a guy who thinks the government should find out everything about its own citizens.
Contents of second article
In the second article Maass quoted from, Melville, drawing on his newfound love for studying the American Civil War, found lessons from the past for civil servants of today. Melville believed that if he had been an adviser to Lincoln at the start of the war, he'd have urged Lincoln that he couldn't win, and therefore, Lincoln had no choice but to live with secession. Melville would have had a lot of solid-sounding pragmatic reasons why the war was doomed to failure, but his reasons, though brilliant in his own mind, would have been completely wrong. (Partly, he'd have been wrong because he'd have underestimated Lincoln's ability to make the impossible possible.)
Extrapolating from this, he suggested that civil servants like him may want to think twice before opposing too stridently policies they think are wrong. Those civil servants, though well-informed and well-intentioned, might be wrong, even though they could explain so well why there were right. Even if the employees were right and the policies from leaders were wrong, bad policies can sometimes work out: Lee made stupid decisions that his soldiers found a way to make look brilliant just by carrying them out in a brilliant way. (And luck.)
As a former military guy myself, I can't help but interpret this in the context of grousing government employees. Nobody can complain like a government employee can. Melville may have heard a lot of this type of complaint. Although his NSA colleagues are no doubt intelligent people who have brilliant reasons to pick apart policies, Melville apparently felt that to oppose every policy, to think he has everything figured out more than those who made the policy, would amount to hubris.
Maass saw in this a loyal-to-a-fault Melville willing to follow even unethical policies. But Melville did not say that Southerners who opposed slavery should have fought for it because their country demanded it. He said that those who accepted the South's cause were doing the "right thing" (within the context of being utterly wrong about slavery), to try to make the flawed strategies of their leadership work. If NSA employees accept NSA's overall mission of using foreign communications to provide foreign intelligence for America's military and policy makers, then they should generally work to make policies in support of that mission achieve their intended results. In this context, the policies Melville thought that workers might object to are more likely to be inefficient or counter-productive in nature, not unethical. This is clearer if one reads some of the other columns Melville wrote, in which he himself groused about a number of those policies, such as a promotion system that discouraged the collaboration it was supposed to reward.
In fact, Melville listed three valid responses to policies employees might not like. One was "I might be wrong." Second was "I might be right, but the wrong thing might work anyway." Third was--directly quoting here: "My oath is to uphold the constitution, and as long as those decision makers are operating constitutionally, I will put my own feelings aside, and support them." (Bold mine.) Melville was willing to give his leaders a lot of latitude, but not infinitely so.
Melville's far from a perfect writer. His blog is sometimes intolerably self-indulgent. In his SIGINT Philosopher columns, he tried to avoid bureaucratic speech and write something interesting, but in the process he left daylight for an uncautious reader to arrive at interpretations that I don't think he meant. But there is no reason to read the worst into what is there unless you've already made your mind up beforehand that you know what he's talking about. That is to say, you might not have the necessary context, and should approach with caution. Melville was wary about pretending he knew more about his targets than he really did (one of his columns was entirely about this). That's why he wanted to know more about those targets. He was worried that the government might take action against the target based on a faulty understanding of the context.
Maass seems to have done exactly the thing Melville wanted to avoid in his work. He pulled the trigger on an accusatory story without having enough context. He read into Melville what he assumed he would find. He assumed, anachronistically, that Melville's admonition to follow policies he didn't like was about NSA metadata programs that have since come under fire (even though those weren't an issue of public debate until months after Melville wrote). It seems more likely, though, that Melville was referring to something entirely different, possibly government policies Melville thught were counterproductive concerning parts of the world he cared about. Maass also assumed that Melville meant "more" monitoring equaled "total" monitoring, and monitoring of everyone, and for whatever reasons suited his fancy. A remotely careful reading, though, clearly shows Melville wanted better monitoring of a limited number of foreign targets picked for specific reasons so that the government had the correct information.
I don't fault The Intercept, The Guardian, or any other venues for trying to write stories about NSA. The Intercept does some important journalism. Last month, they had a story about women on Riker's Island who faced sexual abuse for seeking medical care. After the Kalief Browder story, I don't see how anyone could not see this as critical journalism. Giving a voice to the voiceless is journalism at its best. But a story like Maass's, so blatantly missing the point of writing that was right there in front of him, calls his reliability into question. By extension, it calls The Intercept into question. As the de facto mediators between the Snowden documents and the public, they have to do better than this, or the entire public discourse about surveillance will be off course.
I understand, given the age we live in, anxiety over monitoring of electronic communications. The public will never feel easy about monitoring its government does in secret, just like Melville did not feel easy about his employer monitoring him. NSA must do a better job of explaining how it balances the 4th Amendment rights of its citizens against the need to protect its citizens. A much better job. As in, it should allow the people who actually do and know the work to explain their jobs instead of marching its leaders in front of us to give broad and generic reassurances. Providing a declassified version of USSID SPOO18, NSA's regulations for protecting 4th Amendment rights while carrying out the Foreign Intelligence Surveillance Act, was a great start, but there is much more NSA could do to make clear to Americans what NSA actually does.
It won't be easy. NSA is, I imagine, worried that every reassurance it makes to the American people has a cost in what it teaches adversaries about how to evade NSA. And they might be right--since we don't know everything about how they work, we can't imagine how seemingly innocent revelations might hurt NSA. But it can be done. It just takes creativity and political willpower. I appreciate that The Intercept is part of creating that political willpower, although they are doing it, like all us writers are, imperfectly. Because honestly, nobody would rather see NSA open up more to its citizens about how it does what it does than I would.
In any event, it's another warning to writers. Do everything you can to avoid being misread. But know you'll still be misread, anyway. Me, I take solace in recalling the scorn the real Melville, Herman, received for Moby Dick when it came out. Commenters in America noted that it didn't make any sense how Ishmael was telling the story, when the entire crew of the Pequod died. But it was a simple printer error. The American version left off the end, "I alone have escaped to tell thee," where Ishmael survives. There's no end to things that can go wrong in writing. But keep writing anyway. Someday, perhaps, you'll be vindicated.
Showing posts with label really catty criticism. Show all posts
Showing posts with label really catty criticism. Show all posts
Thursday, October 8, 2015
Thursday, July 30, 2015
how to be lazy as a writer (and still write a decent story)
Before I get into all the things "wrong" with the short story "Long Tom Lookout" by Nicole Cullen, which was included in the 2014 Best American Short Stories collection and is therefore, presumably, a exemplar of the best of the species, the tl;dr is actually this: This is a pretty good story, in spite of how its mechanics fall back on what I will argue are modern literary fiction conventions. I want to make two points by this:
1) Literary fiction is no different from any other kind of fiction. There are expectations and a kind of standard for the field. Some writers break out from this, but you can follow the pattern--sometimes without any innovation at all--and make readers believe you have succeeded in the genre.
2) There's nothing wrong with this. All genres are capable of providing life-changing imaginative connections even when being genre-conventional. Plot, theme, and characterization can make up for the lack of innovation in style and language for a writer.
What are these conventions that I see in Cullen?
1) Listing, often in triples, the things that a character notices as a way to establish scene
2) Highly specific nouns that most people would not really know the names of as a way to establish scene.
"Sin" #1:
When I'm reading a story, particularly a story in third-person limited, I am often distracted when there is a tone of narration going on that seems at odds with the character's POV the narration is providing. A third-person limited POV should give us only what a character can see, touch, taste, think, feel, etc. It is okay for the narrator to interpret for the audience, even to do so with thoughts that the character herself could not verbalize, e.g. "Monica was, in short, getting to that point in her relationship when she would start to invent reasons why the relationship would not work out." This is fine, and doesn't interrupt my enjoyment of the story. But when the author (not just the narrator) seemingly takes over the sensory apparatus of a character and uses the character's eyes, nose, and ears to sense what the author wants to sense, I want to call foul. Examples from "Long Tom Lookout":
I could go on (and on and on), but since all of these examples are within the first 750 words of the story, I think that will suffice. Oh, fuck it, let's do one more:
-Through the grain of the screen Lauren sees a woman impossible to please—dirt-caked knuckles and a gray braid. Glasses hang from a gold chain around her neck.
I included that last one because it looked for a moment like there would only be two things the narrator picked from Lauren's POV to show the reader, but then...BLAMMO!! The third was just waiting in another sentence. These examples are all before Lauren and her son get out of the car to meet her mother, which is when the action really starts.
Why do I have such a critique hard-on for picking out these tripled scene-setters? (To be fair, the second one in the list is more of a catalog of things that have happened than things in the scenery.) Well, I don't really think this is such a great sin, to be honest. Writers are told to present "details that matter," and I suppose most of these details reasonably set tone and Lauren's interior landscape.
I guess one problem I always have in a 3d person limited PoV is the leakage between what is the PoV character's observation and what is the author interpreting those observations for the reader. This very much kills the magic of the story for me on many occasions. I realize that the narrator's voice isn't the same as the character's voice, unless we're in first person. But when the narrator continues to pick up on things in the main character's field of view in triplets, it starts to take over the attention of the reader in a way I don't think is intended. The narrator can pick and chose from what the character has available to inform the story, but the narrator can't move too far away from the voice of the character without being a character him/herself. When Cullen writes "Through the grain of the screen Lauren sees a woman impossible to please," that's Lauren's thoughts that the narrator is giving us access to. Presumably, then, all of these sensory details are things that Lauren perceives. And if she perceives everything in groups of three, we have to wonder if this character has some kind of OCD.
Three is a satisfying number. If the character sees three things, we feel like this is a more authentic description somehow. But falling back on it so much that even I noticed it is going to the well a lot.
"Sin" #2
I don't know who started the tendency to go crazy with Google and look up the exact words for things (or find things you didn't know about and put them in your story), but I see this everywhere. I don't believe Lauren would know pyrite from granite. Or what balsamwood, cheatgrass, and Canada thistle are by sight. But all these things appear in the description. To me, this is a break in the direction of third person omniscient, to a narrator who is able to break the surly bonds of the character and be a lot smarter than the character is. I honestly believe that lit fic has developed an unspoken rule that it is permissible if not outright expected that a narrator will break from the constraints of the character whenever scene is being described. Why? Well, I think it's kind of a bourgeois sentimentality. We want beautiful descriptions of scene, because when we go to our book clubs and don't really understand what the book is about, we can always pick out a few passages of description and talk about how beautiful we think they are. I mean, it's fine. I've done it. I looked up the kinds of grass that would grow in the lowlands of Illinois down by the Illinois river and put that in my story. But I really could go for an easing up of this tendency.
NONETHELESS..
This is a really compelling story. Lauren is feeling all the powerful emotions of new parenthood, all that sudden being needed. She is trying to connect, but failing. Her attempts to nurture end up vomited back up like the Huckleberry milkshake she gives "the boy." She is telling herself that her reasons are altruistic, and that she is being much put upon, but the reactions of others seem to call this into question. It's clear that we at least have a mix of altruism and a desire to somehow reconnect with Keller through Jonah. She's a lookout who can't look out for herself, certainly not for Jonah, which makes her doubly isolated. This is good stuff that scratches at the meaning of parent-child bonding, how it complicates the play between romantic love and our fear of being alone. None of this is weakened because Cullen employed some modern lit-fic stock techniques. She makes up for her mechanical plainness with a good plot and a good character working toward a complicated and meaningful theme.
I get tired of always hearing about how much people value original language or language that makes you stand up and take notice. That's not really what people want. If that were true, then 70% of stories in literary journals wouldn't sound an awful lot like one another. So what I'd like is for us to just drop the charade that great technique is what we want because we're such smart, literary readers. I'd like "literary" fiction to open up to stories that don't sound so "literary," that is, that follow conventions other than the ones that lit fic uses. Because at heart, lit fic isn't really better writing or more linguistically virtuosic most of the time. It's just people doing what they've read other people do in order to tell a story that nobody else has told yet. That's what this story did.
1) Literary fiction is no different from any other kind of fiction. There are expectations and a kind of standard for the field. Some writers break out from this, but you can follow the pattern--sometimes without any innovation at all--and make readers believe you have succeeded in the genre.
2) There's nothing wrong with this. All genres are capable of providing life-changing imaginative connections even when being genre-conventional. Plot, theme, and characterization can make up for the lack of innovation in style and language for a writer.
What are these conventions that I see in Cullen?
1) Listing, often in triples, the things that a character notices as a way to establish scene
2) Highly specific nouns that most people would not really know the names of as a way to establish scene.
"Sin" #1:
When I'm reading a story, particularly a story in third-person limited, I am often distracted when there is a tone of narration going on that seems at odds with the character's POV the narration is providing. A third-person limited POV should give us only what a character can see, touch, taste, think, feel, etc. It is okay for the narrator to interpret for the audience, even to do so with thoughts that the character herself could not verbalize, e.g. "Monica was, in short, getting to that point in her relationship when she would start to invent reasons why the relationship would not work out." This is fine, and doesn't interrupt my enjoyment of the story. But when the author (not just the narrator) seemingly takes over the sensory apparatus of a character and uses the character's eyes, nose, and ears to sense what the author wants to sense, I want to call foul. Examples from "Long Tom Lookout":
- The headlights flood an irrigation canal black with water, a jack fence, and the beginnings of a field.
-The last few days on the road have been an experiment in cause and effect—the boy’s inability to communicate, his self-destructive behavior, his obsession with maps.
-...she thinks back to the rare find of a buried railroad tie, the smell of wet sagebrush, her father bending to touch the pink of a bitterroot flower.
-Nine years have passed and now she’s back with sixty-four dollars in cash, a truck in her husband’s name, and a boy that isn’t hers
-She passes a Wonder Bread truck then a flatbed hauling hay bales and two barking dogs. On the hillside above town, houses begin to wake.
-...the property has gone steadily downhill: warped cedar shingles, rusted wrought-iron fence, flowerbeds usurped by star thistle.
-Her mother stands in the side yard, dressed in a mud-hemmed housecoat and muck boots, throwing feed to the chickens.
I could go on (and on and on), but since all of these examples are within the first 750 words of the story, I think that will suffice. Oh, fuck it, let's do one more:
-Through the grain of the screen Lauren sees a woman impossible to please—dirt-caked knuckles and a gray braid. Glasses hang from a gold chain around her neck.
I included that last one because it looked for a moment like there would only be two things the narrator picked from Lauren's POV to show the reader, but then...BLAMMO!! The third was just waiting in another sentence. These examples are all before Lauren and her son get out of the car to meet her mother, which is when the action really starts.
Why do I have such a critique hard-on for picking out these tripled scene-setters? (To be fair, the second one in the list is more of a catalog of things that have happened than things in the scenery.) Well, I don't really think this is such a great sin, to be honest. Writers are told to present "details that matter," and I suppose most of these details reasonably set tone and Lauren's interior landscape.
I guess one problem I always have in a 3d person limited PoV is the leakage between what is the PoV character's observation and what is the author interpreting those observations for the reader. This very much kills the magic of the story for me on many occasions. I realize that the narrator's voice isn't the same as the character's voice, unless we're in first person. But when the narrator continues to pick up on things in the main character's field of view in triplets, it starts to take over the attention of the reader in a way I don't think is intended. The narrator can pick and chose from what the character has available to inform the story, but the narrator can't move too far away from the voice of the character without being a character him/herself. When Cullen writes "Through the grain of the screen Lauren sees a woman impossible to please," that's Lauren's thoughts that the narrator is giving us access to. Presumably, then, all of these sensory details are things that Lauren perceives. And if she perceives everything in groups of three, we have to wonder if this character has some kind of OCD.
Three is a satisfying number. If the character sees three things, we feel like this is a more authentic description somehow. But falling back on it so much that even I noticed it is going to the well a lot.
"Sin" #2
I don't know who started the tendency to go crazy with Google and look up the exact words for things (or find things you didn't know about and put them in your story), but I see this everywhere. I don't believe Lauren would know pyrite from granite. Or what balsamwood, cheatgrass, and Canada thistle are by sight. But all these things appear in the description. To me, this is a break in the direction of third person omniscient, to a narrator who is able to break the surly bonds of the character and be a lot smarter than the character is. I honestly believe that lit fic has developed an unspoken rule that it is permissible if not outright expected that a narrator will break from the constraints of the character whenever scene is being described. Why? Well, I think it's kind of a bourgeois sentimentality. We want beautiful descriptions of scene, because when we go to our book clubs and don't really understand what the book is about, we can always pick out a few passages of description and talk about how beautiful we think they are. I mean, it's fine. I've done it. I looked up the kinds of grass that would grow in the lowlands of Illinois down by the Illinois river and put that in my story. But I really could go for an easing up of this tendency.
NONETHELESS..
This is a really compelling story. Lauren is feeling all the powerful emotions of new parenthood, all that sudden being needed. She is trying to connect, but failing. Her attempts to nurture end up vomited back up like the Huckleberry milkshake she gives "the boy." She is telling herself that her reasons are altruistic, and that she is being much put upon, but the reactions of others seem to call this into question. It's clear that we at least have a mix of altruism and a desire to somehow reconnect with Keller through Jonah. She's a lookout who can't look out for herself, certainly not for Jonah, which makes her doubly isolated. This is good stuff that scratches at the meaning of parent-child bonding, how it complicates the play between romantic love and our fear of being alone. None of this is weakened because Cullen employed some modern lit-fic stock techniques. She makes up for her mechanical plainness with a good plot and a good character working toward a complicated and meaningful theme.
I get tired of always hearing about how much people value original language or language that makes you stand up and take notice. That's not really what people want. If that were true, then 70% of stories in literary journals wouldn't sound an awful lot like one another. So what I'd like is for us to just drop the charade that great technique is what we want because we're such smart, literary readers. I'd like "literary" fiction to open up to stories that don't sound so "literary," that is, that follow conventions other than the ones that lit fic uses. Because at heart, lit fic isn't really better writing or more linguistically virtuosic most of the time. It's just people doing what they've read other people do in order to tell a story that nobody else has told yet. That's what this story did.
Sunday, October 26, 2014
A book I should have read a long time ago
I just ordered Against the Academy: Provocations, Polemics, Controversies by Anis Shivani. Given that this whole blog is nominally dedicated to my dislike of the university workshop (and the literature it engenders, which seems to occupy most of the journals considered worth reading by the literati), I guess I should have read this a long time ago. I've been busy. Mostly doing stuff having nothing to do with literature.
I found the book when I came this review while looking for criticisms of The Road by Cormac McCarthy, which I just read. Man, Shivani is a strident son of a bitch. Too strident, I thought, in his sweeping smashing of nearly all literature that DOESN'T deal with death and the thinness of capitalism. But maybe that will be just the ticket for something I think is as obviously a failure as university writing programs, but that seems to go on and on like McCarthy's road. I am planning to read it just to enjoy vicariously feeling his seething rage and he makes points I've thought about, but do not have the wit to phrase as sharply as him.
I found the book when I came this review while looking for criticisms of The Road by Cormac McCarthy, which I just read. Man, Shivani is a strident son of a bitch. Too strident, I thought, in his sweeping smashing of nearly all literature that DOESN'T deal with death and the thinness of capitalism. But maybe that will be just the ticket for something I think is as obviously a failure as university writing programs, but that seems to go on and on like McCarthy's road. I am planning to read it just to enjoy vicariously feeling his seething rage and he makes points I've thought about, but do not have the wit to phrase as sharply as him.
Subscribe to:
Posts (Atom)