Recently in writing Category

Acknowledgments

| | Comments (2)

Acknowledgments are one of those occluded genres in our writing. It's rare for us to have the opportunity to issue public expressions of gratitude, although if the general session at CCCC were more like the Oscars, maybe that would change. Not that I'm suggesting, mind you.

Anyhow, a couple of months ago, I contacted my press to see if they would mind if I changed my acknowledgments. The original was a fairly standard set of thank yous to friends, family, colleagues. With my dad's passing, I felt like I needed to spend a little more time thinking and writing about his influence on my life. My intention, once they agreed (which they did), was to spend that weekend drafting a new couple of pages to sub for the ones they currently had.

Well, that was two months ago. I've intended to work on those two pages every weekend since then, and every weekend, I put it off. And off. And off. Here's the thing: I don't really write from pain. I talk it through. It's partly why this space has been as silent as it has for the past six months. I want to write something, but nothing that I can imagine writing is really enough for what I want to say. I talked about this problem with a couple of different friends today--talking about it is easy. Writing? Not so much.

And the fact of the matter is that, if I hadn't written a draft the other night, I would have continued to not write about it some more. It's been an odd experience that way. I have things I want to write--there's a couple of articles in me itching to get out--but I haven't really wanted to write. The connection is obvious, of course, but there's a little more to it, because while I know my dad was proud of me and what I was doing, there wasn't that much of a direct connection between the me who was his son and the me who writes articles, chapters, or books for the discipline. Not blogging makes more sense, because I know that he read this site.

Ah well. Like I said. I have a draft, and an idea or two about revising it. My guess is that getting this done will make it more likely that I'll come round here a little more. And maybe I'll finally get around to giving myself permission to write again. Here's hoping.

That's all.

1 step forward?

| | Comments (1)

Lindsay Waters has a piece in yesterday's IHE about how we evaluate what we do in the academy, "A Call for Slow Writing." Now, you might recall that my own feelings about Waters are, shall we say, less than glowingly positive. But I will say that my feelings about this essay are mixed, and not in the worst way.

First, it's a well-wrought piece, showing off Waters' own skills at prose, and it is replete with erudition. I don't usually write like that, but there you have it. And second, I'm actually in complete agreement with the major point of the essay:

I have claimed elsewhere that the book-for-tenure system is coming to an end, that it is unsustainable, that its growth has been an obscenity, because it was mindless, because it sought to make something automatic and machine-like play the role that should only be played by the soul....There is no good reason why the essay should not replace the book, and a lot of good reasons why it should. I am tempted to say -- in order to be maximally provocative -- that anyone who publishes a book within six years of earning a Ph.D. should be denied tenure. The chances a person at that stage can have published something worth chopping that many trees down is unlikely.

Waters' argument is that we need to start unlearning the system that prompts us to push out writing as quickly as we do, in the interests of bumping up our pre-tenure numbers. I don't know that he'll have many takers for denying tenure to those who do publish books, but I will say that I very consciously reset my tenure clock when I moved from ODU to SU. And my book was better for it, I believe.

So far, so good. It's a little curmudgeonly of me, but I am willing to grant that most of our writing would be improved by shaking it free of the shadow of tenure. But then...

What I'm saying is that the first step to re-establishing the essay as the standard in humanistic writing is to reinvigorate the sentences we write, so that, when one reads an essay, one feels it. One feels it the way one tastes -- and here I'm going global -- a good curry. It really sets you back. Or maybe forward. Style, maniera, modo is what we readers demand.

It's hard for me not to react negatively--and here I'm going local--to the modo for modo's sake here. But the larger point is where I'm set back. To imagine that an entire profession sits around thinking, "hmmm, how can I write a really crappy sentence here?" is beyond laughable to me. Is there writing in the humanities that is largely indefensible from a stylistic point of view? Almost certainly. Are there writers in the humanities who consciously set out to produce inelegant prose? I seriously doubt it. So the notion that an entire tenure system is going to be changed by our conviction about the quality of our prose just sounds cranky to me, to be honest, and not serious at all.

Now, Waters goes on to talk about the editorial changes going on at boundary 2, and they sound great. I'm even willing to grant as part of a thought experiment that other journals follow suit. Not all, I'd imagine, but some. Let's even suppose that some of the essays written in this renaissance of clarity trickle upwards into book form. How long will that take? And where does the system tip?

Most importantly, though, what will any of this have to do with the demands placed upon us by our institutions? Who will be the first top-flight university to say that their tenure expectations are aberrant, and should be scaled back to allow more quality work? Which administrator, content with a system that translates qualitative work into quantities, is going to admit the "obscenity" when most university and college budgets already build into their calculations the retirements and tenure denials, and the budget line resets that they bring?

Seriously.

I've never been all that adept at the kind of nominal-dense, code-wordy prose that Waters and others decry, so I don't really take this stuff that personally. What I do take personally is the transfer of value judgments from the work (this work is difficult, obscure, and personally offensive) to the folk who write such works, in some kind of weird moral algebra. Honestly, I find that a little sloppy.

There are things that we can do. That much I agree with. We can strive to write as well as we can, certainly, and we can try to hold each other accountable as we read manuscripts, offer advice, direct projects, etc. But to imagine that we are the ones who have driven this system within which we toil is a little facile.

And this is from someone who's been fortunate enough to receive tenure. I'm not one of those who believes that the current system was good enough for me, so it's good enough for anyone else. But I don't see this essay offering anything like a solution for the problem it poses.

That is all, except to note that I'm not the CB who left a comment on the original post...

Exposed!

| | Comments (3)

I need to get a-typing, if I'm going to meet my goal of reaching the 1000-entry plateau this summer. These entries won't write themselves. It's been a light first week, for various reasons. One of the biggies, though, is that I think I'm getting a little touch of arthritis in my right hand, which suggests to me that I need to rethink my current approach to mouse usage. It hurts when I type as well, but I think that my mice are curving my hand in a way that my knuckles aren't pleased with.

Anyhow, enough of the whine. One thing I wanted to note this week was Donna's entry about Jason Jones' interview with Steven Johnson. I'm a big fan of all of SBJ's books, but Ghost Map is one that I keep meaning to review (and in more detail than my discussion of it here). But the funny thing about Donna's entry was that I felt a little exposed. Not in any dramatic fashion or anything. But when she notes

Ah ha! I thought. So now I get the connection among many of the things Collin blogs about: Moretti, Johnson, and Latour, too.

I feel a little like I've had a secret made public. I'm not ashamed of my influences--far from it, in fact--nor of the fact that I have influences. We all do. But it's strange to have them named like that, the texts that recently have resonated with me and with each other. One of the things we do as academics is to assemble our own private bibliographic networks, and inevitably, the texts we value most highly drift towards the center of our network, and become the default frames that we bring with us both to subsequent reading and our own writing.

And interestingly enough, we don't always pay attention to each other's networks. Sure, every couple of years or so, there's a thread on a discussion list about the disciplinary desert island books, but even those threads ask us to represent the discipline. I would guess that most of those books/articles have very little to do with us personally. Moretti, Johnson, Latour, and others affect the way I see the world academically, but none of their works are rooted primarily in my discipline. I wonder from time to time about my colleagues' networks, and about what it would tell us about each other if we could generate and share an honest "cloud" of our influences.

It makes me curious to go back and assemble all of my bibliographies (the way that Derek did with coursework a ways back) and to see if there are patterns that I can detect. Are there thinkers I rely upon unconsciously? Probably. But for the moment, I'm going to pursue the various angles that writers like Moretti, Latour, and Johnson supply me, because I'm not close to done with them yet.

That is all.

I thought I might return one more time to the carnival and add a couple of more thoughts. Be warned, though. I suspect that this will be more a loose affiliation of thoughts than a careful essay. It was prompted most recently by an entry over on Cara Finnegan's blog, wherein she asks whether method chapters are strictly necessary anymore. Of our own neighborhood in Rhetopia, she writes:

And I could be wrong, but it doesn't seem that my friends on the rhetoric/composition side of things have anxiety about "methods" in quite the same way.

I started a reply over there, but followed the 2 paragraph rule (when a comment gets much longer than a couple of paragraphs, I tend to copy and paste it into an entry here). First things first, I disagree with her observation. Or rather, I agree with it only in a certain way. She describes the work of "rhetorical critics and historians" thusly:

The obligatory methods section feels to me more and more like a prehensile tail, something rhetorical critics evolved at one point because it was institutionally useful (particularly in communication departments concerned with questions of legitimacy in the academy). First of all, does anybody really work that way? Aren't most of us using a variety of "methods" and approaches in our work? Most rhetorical critics and historians approach discourse more or less inductively, and adjust their critical approaches accordingly.

I wouldn't call this "a variety of methods," but rather a variety of perspectives informing a single method. I don't say this to be critical, because I do think that this is a nearly overwhelming default position in rhet/comp as well. So if indeed our field enjoys a lack of anxiety over methodology, that lack itself strikes me as a worthy cause of anxiety. As much as I tease friends for going meta with their neuroses, this is a case where we should be worried about not being worried.

This is not a direct engagement with Trimbur, but I think it's one of those layers that we might add to the questions that he discusses. To the question "Should writing be studied?" then, my gut response is to ask instead, "How should writing be studied?"

In part, my thinking on this is motivated by the fact that I'll be teaching our methods course in the fall, and I'm already thinking about what I want to do there. But it's also motivated by own lack of training in methods beyond the textual (which is what I take Cara to be describing in her entry). And finally, it's motivated by my perception that at one time, rhet/comp engaged passionately with questions of how we might study writing, but now we do a lot less of it. I could be wrong, of course, but here's a little evidence:

First, Chris Anson's talk last year at WPA (discussed by Becky here and here) Follow that second link, and you'll see a list of activities, almost all of which strike me as necessary in order for us to claim the study of writing as our province.

Second, Rich Haswell's essay, which Anson cited in his talk, on the "NCTE/CCCC’s Recent War on Scholarship." Although there's a part of that essay that I've critiqued, the essay overall is an important one. The consistent devaluation of replicable, aggregable, and data-driven scholarship in our field is interesting to me, as it supports the emergence of celebritocratic, reading virtuosity as the coin of the realm.

Third, I'd point out a couple of interesting projects, neither of which was "published" in our field, but both of which strike me as just the sort of thing that scholars in writing studies could and should be doing. The first is Joseph Williams' "Problems into PROBLEMS: A Rhetoric of Introductions," (PDF) which is one of those 'tweeners, too long for an essay, too short for a book. "Problems" attempts a structural account of introductions (as opposed to the inductive work of Swales and others), supported with several small-scale studies. (I've gushed about it before) I'd also point out one of the winners of last year's Ig Nobel prizes, Daniel Oppenheimer's "Consequences of erudite vernacular utilized irrespective of necessity: problems with using long words needlessly" (Wiley), an essay that combines various small-scale studies about whether using longer words makes a text more effective. It's a little statisticklish, but nevertheless understsandable, and worth the read.

The thing about projects like these is that I can see them functioning as dissertation topics, but I could also easily imagine tailoring the studies so that they could be conducted in a graduate classroom, or even an undergraduate classroom. Another thing about them is that they take writing seriously, which strikes me as the sine qua non of answering the question of writing studies affirmatively.

This is to say nothing of my own methods, which increasingly take new media both as object and as an influence on method. And there are plenty of other methods I'm passing over here, from ethnography to activity theory to case studies, that might be more appropriate for writing-as-verb rather than writing-as-noun.

And finally, I should note that I started drafting this a couple of days ago, but only just got around to looking it over and touching it up. In the interim, I got a copy in the mail of Raul Sanchez's The Function of Theory in Composition Studies (Amazon). It's a fast read, but a good one, wherein he writes, among other things:

Globalization and the proliferation of technology make it imperative that compositionists develop a new kind of composition theory, one that understands its object of study very broadly and is conscious of its methodologies (72).

I couldn't have said it better myself, but have tried to say it somewhat longer here, I guess. My answer to the question "Should writing be studied?" depends in large part on what we mean both by the word "writing" and the word "studied." Not all our answers would be the same, I suspect.

That is all, except for the brief postscript that I've started brainstorming texts for the methods course (and am already at 25 books at the time I post this). Feel free to take a look--I'm using an Amazon Listmania list to do it, but may switch over to Library Thing if the list grows too big. You'll find it listed as CCR 691. Feel free also to suggest additions.

Now that is all.

Going out with a whimper

| | Comments (4)

Although I still use them from time to time, as their affordances are useful for a particular context, I don't spend much time anymore on listservs. And today, I unsubbed from my last holdout, a disciplinary listserv ostensibly devoted to my specialty. As with the blog, I go through phases of listserv fatigue, but over the last few years, the fatigue periods seem to grow longer and longer, punctuated more by silence than by activity.

My unsubscription was prompted by a message today which, under the auspices of continuing a discussion from earlier this week, launched into what, as best as I can tell, was a largely unprompted invective against blogging. I won't repeat it here, both because I'm not sure the list is public and because I'm not interested in dignifying it. Long and short, though: blogging, the message suggests, "atomizes, isolates, and individualizes knowledge." A few more sweeping generalizations, and a strange fascination with the idea that blogs are assholes, or like assholes, or bloggers are assholes. I don't know.

And honestly, I don't really care. My experience with blogging is so different--of course, it could matter that I actually maintain a blog--that the message could have been in another language for all the sense that it made to me. I was sitting in Panera today, reading Amanda Anderson's The Way We Argue Now (Amazon), and in it, she has a chapter on ethos in the Foucault/Habermas debate. Anderson is accounting for a comment from Foucault that he is "a little more in agreement" with Habermas than Habermas is with him. By saying this, Anderson explains:

Foucault implies that there is no external perspective from which one might adjudicate their differences or agreements, precisely because one essential element of agreement stems from the attitude of the thinker towards the other's work.

This stuck with me, because it fits nicely into the network-y/visualization thinking I've been doing, particularly when it comes to thinking about ways to map conversations and/or disciplines, and to chart changes. One of the things that Anderson's doing in that chapter is shifting the relationship between Foucault and Habermas, undoing the knee-jerk binary through which that relationship is frequently viewed. The link between the two is still there, but its character is altered, assuming that Anderson's various interpretations are persuasive.

It sticks with me not because I can really disagree with the specific charges leveled against blogging in that message, because I'm sure that there are plenty of examples that anyone could trot out to validate them. What irked me most is the foreclosure of any sort of conversation; it was almost beside the point that it was initiated by someone with little to no direct experience of our community. Almost. Anderson explains that this comment from Foucault is consistent with his "dislike of polemic":

The polemicist...proceeds encased in privileges that he possesses in advance and will never agree to question. On principle, he possesses rights authorizing him to wage war and making that struggle a just undertaking; the person he confronts is not a partner in search for the truth but an adversary, an enemy who is wrong, who is armful, and whose very existence constitutes a threat. For him, then the game consists not of recognizing this person as a subject having the right to speak but of abolishing him as interlocutor, from any possible dialogue.

There's something to this for me, not the least reason for which is my own general avoidance of confrontation. And it's also not to say that I don't fall back into polemic myself. I do. But I've got a lot more interest in figuring out how my ideas connect to, diverge from, and/or relate to someone else's than I do in waging a polemic/war. Even though, I suppose, it could be argued that my entry is doing just that.

Or it would be, were I to do two things, both of which are equally tempting. I'm tempted to refute those claims, drawing on my own experiences, talking about all of the collaboration, networking, and working-with that maintaining a blog has prompted in my academic life for the past three years. I'm also tempted to critique the listserv post, and perhaps even the list itself.

But I think I'll refrain. Which isn't to say that my entry here is snark-free--that'd be some sort of record, I think. It is to say, rather, that a community where someone feels comfortable (much less justified) in making those sorts of comments is not the kind of community I have any interest in being a part of.

That's all.

[x-posted at Rhetworks]

It's been too long since I tended to Rhetworks, but one of the first essays I took note of (and took notes on) when I started the site was Anne Stevens' and Jay Williams' "The Footnote, in Theory." My notes on the essay are hardly complete, but I do cite the essay with some approval and interest. At a time when I was exploring the disciplinary implications and applications of Franco Moretti's "distant reading," FIT was for me a nice example of what could be accomplished by aggregating what is a fairly occluded feature of academic prose, the footnote.

Stevens and Williams begin their essay with what I find to be a manageable and worthy set of goals:

We set out to determine, first and most simply, who and what works are most often cited in our pages. Second, we wanted to track trends and fashions, as well as constants. Over the past thirty years, theory has seen any number of upheavals and innovations, so we wanted to see if certain writers remained touchstones for our authors. Third, we wanted to investigate a related question, the question of the status of the footnote in our pages. Elaborating upon Anthony Grafton’s book The Footnote: A Curious History, we sought to investigate how theory is transmitted through notes, what sorts of conversations are held below the main text, and to thus discover in a different sort of way the identity of our journal, a journal that has been identified with theory for so long.

I quote their introduction at length for a reason. My main qualm with this essay is not a methodological one, although I think that their method does have its limits. As I commented in my entry on FIT, my biggest reservation is that there are a lot of visualization possibilities in a data set like the one that Stevens and Williams generate, and their article only scratches the surface of those possibilities. But this is one of those critiques that has its roots more in my interests than in any necessary shortcoming in the essay itself.

Little did I know, back when I was jotting down my thoughts, that Lindsay Waters, he of the Eclipse of Scholarship (Amazon) fame and Executive Editor for the Humanities at Harvard UP, had already provided a pithy, pop-culture-laden putdown of Stevens and Williams, some 3 or 4 months before I even found it, at the Chronicle: The Lure of the List. (I have Scott to thank for pointing it out today.)

The lure of the list refers to the temptation that "klutzes" like Richard Posner and "clowns" like David Letterman yield to, but above which we in the humanities should hold ourselves. Lists are, and I'm quoting variously here, like pornography, bogus social science, hocus pocus, pseudoscience, a Trojan horse, and so forth. I'm not sure "wastage" is a real word, but it's the cost of an article like this apparently, as is our neglect of scholarly "fruit wasting on the vine, whose cultivation might have benefited us all." It's hard for me to recite this giant list of mixed metaphors without rolling my eyes, just a little. It's really over the top.

And I say this as someone who genuinely appreciates the efforts of Waters to shake loose some of the entrenched assumptions about the relationship between the publishing and tenure industries. Even so.

I'll restrict myself to two criticisms and one compliment. The first criticism deals with Stevens' and Williams' introduction, which in Waters' review, becomes the following:

But my heart sank when I saw that the premier egghead journal of the land, Critical Inquiry, published an essay last winter that purported to rank the greatest literary theorists in its pages (and, by implication, the world).

Maybe there's a history here that I'm not privy to, but wow. I'm afraid I take the authors at their word when they say they're interested in charting the trends that occur in the pages of their journal. The master list of citations (and one should add, citation in footnotes) is only one of the charts provided, and the information it provides hardly translates into The Greatest Theorists in the World!!™

Maybe I'm just defensive here, but one of the things that we're trying to do with the CCC Online Archive is to provide this kind of information. We're not trying to generate tenure industry kinds of information, though; rather, we're interested in providing newcomers and veterans alike with new pathways into the scholarship collected in the journal. We're proud of pages like this one, which dynamically tracks the self-citation in the journal. Are these the "most important" articles, and their authors the Greatest Scholars in Our Discipline? Not at all. But it tells you something about the journal that would be hard to glean even from years of reading, unless you're particularly fond of bibliographies and have a particularly mighty memory.

My first criticism, then, is the cavalier way that Waters attributes motives to the Stevens and Williams, thereby doing the work that they actually do a great disservice. My second criticism is related: I'm not sure that Waters actually read the article, or made any effort to understand that work. His description of their method, once you get past the snottiness of "very likely bogus social-science tools," is curious. Why "very likely" in a review that is not exactly notable for the application of kid gloves?

Waters' only real critique of their methods is to smack at them for neglecting the work of sociologists like Robert K. Merton. Now as it turns out, Merton's work is on my Rhetworks list, and in my pile, so I actually have read it. Scott notes that

The casual, condescending quality of his dismissal fails to embody the standards it claims to uphold.

Merton's "Matthew Effect," which Waters cites approvingly, is in part a discussion of the reward structure in the sciences, where famous scientists receive disproportionate attention and reward for their efforts, and non-famous scientists get the shaft. The Matthew Effect is a rich-get-richer notion. But there's more to it than that. Merton also emphasizes the communication system; if attribution is the currency of the reward system, then visibility is the currency of the communication system. Famous scientists, he explains, may receive disproportionate rewards, but they also are able to make their ideas visible and diffuse more quickly, contributing to the development of knowledge.

What's interesting about Merton's original article on the Matthew Effect (.pdf from UPenn) is his interviews with various Nobel Laureates, who are acutely conscious both of their struggle to gain recognition and the privilege that accrued to their position once they did. What's interesting to me are the various strategies that they discuss for using their disproportionate visibility to help younger scholars. In other words, there's an ethical component here to the Matthew Effect, one felt strongly by many of those that Merton interviews.

What I take Scott to mean is that Waters, as the Executive Editor for the Humanities of Harvard Press writing for the Chronicle of Higher Education, might himself reflect upon the ethical dimension of the Matthew Effect. Were he to do so, he might rightly conclude that reviewing an essay by misreading its intentions, distorting it, and calling it all sorts of names, is exactly the kind of disservice that Merton might find less than kosher. Whether or not Scott means it, that's my second criticism.

Now for a compliment. There's a legitimate argument lurking beneath all of the verbage and vitriol that characterizes Waters' column here. After recalling the top ten or so (and making note of all on the list who are affiliated with Harvard (??)), Waters writes

[The authors] note that "Benjamin's works are cited nonargumentatively," which I think is a nice way of saying his ideas are just window dressing, not engaged with. That must be why he ranks high as one of the most perfectly citable authors of all, because you can cite him reverently without having to figure out what he said. With Benjamin a citation is the academic equivalent of the purely ritual move, like a ballplayer's sign of the cross.

This is a genuinely interesting thesis, and speaks to the flux located just beneath the smooth surface of any list. At another point, Waters accuses the authors of "substitut[ing] accounting methods for critical judgment," and yet, just a few paragraphs later, Waters demonstrates that it's possible to generate critical judgment out of the evidence provided by these so-called "accounting methods."

And that's the real point here. Our institutions may indeed be on a quest to reduce what we do to numbers, and the tools are out there for them to do that. But in the humanities, we've avoided these kinds of evidence and these methods, out of a misplaced faith that if we simply close our eyes to them, they can't affect us. But the Nobel Laureates that Merton interviews are very conscious of the asymmetries attendant upon their activity, and it is that consciousness that allows them to try and redress them. There's a great deal of knowledge that we could be generating and building upon if we were to turn to information design, visualization, and yes, even some of these "accounting methods," not as ends in themselves, but as starting points for the kinds of critical judgments that Waters advocates.

For me, this kind of knowledge is far more likely to be the fruit that withers on the vine, at least in the field where I work.

That is all.

MLAccompli

| | Comments (1)

As the regular reader will remember, this year's MLA kicked off with a stirring rendition of the second chapter of my book manuscript, with the unusually expository (for me, at least) title "The Rhetorical Canons as an Ecology of (New Media) Practice." Gee, I wonder what the talk was about?

Hee. Today was also the 3rd step in the epic self-transformation that will see me turn from a reader of conference papers to a speaker of conference presentations. I worked from an outline and from the slides, but otherwise, did not script the specifics. I think it went okay, but I do have to confess that the fellow in the 3rd row who used his cameraphone to take snapshots of each of my slides, and whose phone rang not once but twice during our session, was a bit of a distraction.

And yet, it was he who inspired me to go ahead and try out SlideShare, which is basically a YouTube-like service for PP presentations. Keynote exports to pdf, which I can then upload and turn into a shareable Flash doodad.

(Update: The doodad was taking serious download time, so I'm replacing it with a link to the SlideShare page instead. Those readers uninterested in unnarrated PP slides may now breath an appropriately grateful sigh of relief.)

The pdf option, far as I can tell, preserves original layout and font better, and has the virtue of being about 1/10 the size of a PP export. So even though there's no support for a Keynote native presentation, it works out just fine.

The slides themselves are probably a little oblique without commentary, so I'll use ProfCast when I get back to Syracuse and offer a full-service version. In the meantime, suffer in silence. I'm done with my talk, and have a much more leisurely conference ahead of me.

That is all.

Comic zen

| | Comments (1)

There are days where I wish I could do more with Garr Reynolds's Presentation Zen than just send adulatory links his way. But oh well. He has a great piece on translating Scott McCloud's work on comics into presentations. Maybe it's more accurate to say that he's talking about learning from comics when it comes to presentations. Either way, as I gear up for what will be several talks this year, I'm going to keep going back to PZ over and over as I plan out this year's presentations. You should, too.

Update: It is a conspiracy. McCloud is giving a talk next Monday in Rochester, and where will I be? Yes, that's right. At a faculty meeting. AARGH.

Keepin on

| | Comments (3)

Paul has a nice reply to my earlier post, Derek's, as well as the comments that Jeff and I left over at his place. A couple of quick things I wanted to mention, maybe to pick up later:

I also feel that reading the professional literature has become much easier. I know what to read carefully (and several times) and what to skim through quickly because I can often predict where I might find certain arguments or pieces of information because of my genre knowledge. Sometimes I can even predict what the text is going to say before reading it based on my knowledge of what's been said and done; in those cases, reading is a matter of confirming my predictions and noting any discrepancies.

That's something that I should have mentioned but didn't, the fact that it does get easier. The advantage of any relatively closed network of texts is that we read for content, yes, but we also read for the strategies and tropes that frame that content. I like "genre knowledge" as a description of it. While it may be somewhat disconcerting to realize that there really aren't all that many ways to say what we have to say, I've always found that it makes my reading easier, too.

And lately, in the past year or two, I've really become interested in the kinds of mental mapping that we inevitably do as scholars. My personal crusade has been to think of ways that this mapping can be aggregated so that we aren't each reinventing the wheel, but on a smaller scale, I've been asking my students (in the last 3 grad courses I've taught) to really think explicitly about mapping as knowledge production.

And that's part of what I mean by managing the collection of academic texts and ideas. I think that there are intermediate steps between reading on the one hand and writing on the other, steps that can, if not shorten the distance between the two, at least allow us to make the transition with more certainty.

The tools that we're using to put together CCC Online are almost all available to anyone with a web browser, and I think they're scalable to the individual user pretty easily. Paul's right to note at the end of his entry that it's crucial to reach a critical mass, though, which is the flip side of the sustainability argument that I make. Any system must be simple enough to accomplish on a regular basis, and done often enough that it achieves critical mass. I look at the tag cloud emerging from our work with del.icio.us, and while it's only a map of 11 or so years of the journal, I feel like it gives me a pretty good idea of that span. And when you add in the fact that the tags themselves link out to specific essays, it's a pretty darn useful little "paragraph." Imagine having a cloud like this for each of several exam lists, for example:

I'm going to be doing some experimenting over the next couple of weeks to try and make our own process even more useful and streamlined. With a little luck, I'll be posting about it soon enough. But this is one of the ways that a collection might be managed to a scholar's advantage, emerging or no...

That's all.

Collections vs Conversations

| | Comments (6)

Derek's citation of an entry over at Paul Matsuda's blog tripped a bit of a switch for me this evening, and the result is probably going to be a sizable post. Buckle your seat belt.

What I want to take issue with, ever so slightly, is the tried and true bit of wisdom that entering academia is a matter of "joining the conversation." We're fond, in rhetcomp, of Kenneth Burke's passage from Philosophy of Literary Form, as a metaphor for disciplinarity:

Imagine that you enter a parlor. You come late. When you arrive, others have long preceded you, and they are engaged in a heated discussion, a discussion too heated for them to pause and tell you exactly what it is about. In fact, the discussion had already begun long before any of them got there, so that no one present is qualified to retrace for you all the steps that had gone before. You listen for a while, until you decide that you have caught the tenor of the argument; then you put in your oar. Someone answers; you answer him; another comes to your defense; another aligns himself against you, to either the embarrassment or gratification of your opponent, depending upon the quality of your ally's assistance. However, the discussion is interminable. The hour grows late, you must depart. And you do depart, with the discussion still vigorously in progress.

There are critiques of the Habermasian character of the Burkean parlor, but that's not my concern. My concern is with the ease with which "putting in one's oar" is translated into the nominalism of "publication." As in, I need a publication, or to get a publication, or I don't have enough publications. I'm being somewhat specific here: I'm objecting to "publication" as a thing you have as opposed to "publishing" as an activity you engage in. And thus my concern is also with how we translate "listen for a while," because I think that's key for publishing (and perhaps less of an emphasis in publication).

For the past couple of years, I've been handing out Paul Matsuda's chapter "Coming to Voice: Publishing as a Graduate Student," from Casanave and Vandrick's Writing for Scholarly Publication (Amazon). In fact, I wrote about it, almost exactly a year ago, in the context of a discussion about the ongoingness of blogging. So it was kind of cool to see Paul repeat some of that essay in a blog entry a couple of weeks back. And it reminded me about why I hand out his chapter in the first place.

I wrote a year ago that "What's important about the essay is that it narrates a process that's not about acquiring disciplinary content so much as it is learning about the conversations, about seeing publication as an ongoing process," but I want to amend that statement slightly. I'm now beginning to wonder if even the metaphor of "conversations" pushes us too quickly towards the "publication" end of things.

As I mentioned early on, over at Rhetwork, the idea of collection has been gathering steam for me for a while. And so I want to contrast collection with conversation as a guiding metaphor for academic/intellectual activity, particularly at its early stages, i.e., in graduate school.

I'll add some citations to this eventually, but this summer, at RSA, I gave a paper where I suggested that collection, as Walter Benjamin describes it in "Unpacking My Library," operates as a hinge between narrative and database, in part based upon our affective investment in it. I may look at my big wall of books and see all the various connections among texts, in terms of their content, chronology, and my own encounters with them. In short, I may perceive it as a big wall of conversations, of disciplinary narratives. Someone else may happen upon it, and simply see a library, a database of rhetoric, critical theory, technology studies, et al.

The value of the collection, of having all these books here, is that I'll never know what's going to be useful. I can't predict, when I begin an essay, what will find its way in and what won't. I have the luxury of being able to work my way through my collection, following up on dimly perceived connections, my own added marginalia, etc. And the wall enacts on a material scale what's going on in my head as I constantly add articles, books, ideas, etc., to the collection of disciplinary knowledge that occupies a certain portion of my mind.

It probably feels like I've wandered from my point. My point is that we tend to think of our disciplines largely in terms of the narratives we construct, stories of the field's progress from point A to B to C or as conversations among certain luminaries occurring in the pages of journals and books. To treat the discipline as a database (where, a la Manovich, it's just "an infinite flat surface where individual texts are placed in no particular order” ) is to foreclose, initially at least, on the narratives that we tell ourselves about our fields.

But of course, disciplines are neither one nor the other; they're both. From the outside, the publications in a given discipline comprise a growing mountain of discourse that no one person could possibly master. From the inside, even a single article may yield all sorts of narrative information about where the writer's from, with whom she studied, to whom she's responding. We become quite adept at reconstructing conversations from a single voice, and the occluded genres of footnotes, citations, and bibliographies can only help us do so.

And when faced with the conceptual metaphor of a discipline as a gathering of conversations, as a parlor, our response is to want to join it, to enter the conversation. The uber-competitive job market only fuels this desire, as if it needed feeding. When faced with a conversation, there aren't a lot of other options.

I want instead to think about collection as an alternative metaphor for what we do, or an earlier stage of a longer process. In part, I'm prompted by Brendan's Katamari Interface and by Jeff's comments about DJs as researchers. When I think of the tools that I use most often, I can see them in terms of collecting:

  • blogs, collecting my thoughts and notes
  • del.icio.us, collecting my bookmarks
  • Library Thing, collecting my books
  • Bloglines, collecting my feeds

and so on. In talking about why it's important to "read it all," Paul explains:

I then scan through [the library] to explore the intertextuality--which sources get mentioned more frequently and how. I then collect more sources if I don't have them handy. Without this process, it wouldn't be possible to come up with viable research questions or to know what questions or concerns reviewers and readers might have.

This is exactly the kind of data mining that we become proficient at as academics, but it's awfully tough to accomplish unless you have that collection to begin with. As we gain experience, we learn how to read articles for their intertextuality, for the differences between primary and secondary sources, etc. But the conversations emerge from collection, not the other way around. And in fact, I want to suggest that the discipline as database also emerges from collection, but that's a different essay.

I'm most certainly not trying to sneak around the back way to saying that "grad students these days are too focused on publication blah blah blah," although there are probably hints of that here. To take a course is to engage in collection, as you read texts and add them either to your active memory or your shelves. It's something we all do, period. To read a journal is to add to your collection.

I'm doing a guest shot in our gateway course this week, and what I'll be talking about, what I'm interested in here, are the logics of thinking as a collector. There are all sorts of tools, not to mention plenty of great examples, for the process of managing your collection, but it's important, I think, to make the figural leap. That is, it's important to understand that what we do in graduate school is to collect.

When I was a kid, I collected baseball cards. And for the first couple of months, I would buy the random packs of cards, always with the assurance that there'd be at least a few cards that I didn't have. As that number began to shrink, I'd start trading my doubles for friends' doubles, of ones that I hadn't gotten yet. And it would get to the point where I'd need only a few to complete a team or even a season, and so I'd go and pay premium prices at the card shop for the one or three that I needed. As a collector, it was important to have the whole set, of course. Reading the journals in a field is a lot like buying store packs, and I don't mean that as an insult. But their output is constrained by their input. Some journals are like being able to buy a store pack with the guarantee that the cards are all from the same team. That's also what taking graduate courses are like, I think. At some point, though, you have to get really specific, and spend your time strategically, to find the key elements missing from your collection, and that means going beyond course work or journals, and tracing bibliographies, asking experts, etc. It means thinking like a collector.

On the one hand, thinking like a collector means just accumulating, rolling your brain/katamari over everything and anything it can pick up. But it also means thinking about how you're going to manage it, how you're going to be able to use, in two years, what you're reading now. I can tell you from experience, "Well of course I'll just remember it" won't work. Seriously. It was just about a year ago that I was coming off of a discussion of note-taking (I taught our gateway course last year), and wrote:

One of the things that I emphasized in class today was the need to develop systems that are sustainable, things you can do (and keep doing) after the initial motivation has passed and the glow has faded.

And that's what I'll end with this year. And probably this week in that course. Use folders, notebooks, blogs, whatever, but build sustainable collection practices that you can engage in tomorrow as well as two years from now. Collect, collect, collect.

Told you it'd be long. That's all.

technorati tags:

Archives

Pages

Powered by Movable Type 4.1

About this Archive

This page is a archive of recent entries in the writing category.

tunes is the previous category.

Find recent content on the main index or look in the archives to find all content.