I am thoroughly embarrassed

| | Comments (0)

to note that less than a week ago, the five-year anniversary of my blog passed without mention by me.

In all fairness, it's probably because the last year or so has only barely counted as a year blogging-wise. It's been a real struggle for me, on multiple levels, to maintain a consistent presence here, although I'm hoping to change that this fall.

In all unfairness, that change will have to wait a bit, however. I'm not quite ready to talk about that unfairness, but you'll understand when I do.

That's all for now.

I'm only slowly re-looping into political discussions, following my summer backlash against all social media (inc telephone and television), but David Weinberger has a succinct account of McCain's technology policy that's worth reading if you're interested in that kind of thing.

Short story even shorter: "the Internet to McCain is a set of tubes for delivering content to an awaiting public."

As if there was any doubt about it, I should say that, yes, it would please me greatly to have a President with some glimmer of understanding about these issues.

Syllabus Muse?

| | Comments (2)

So here's a question.

I'm working up my syllabus for a course I'm teaching this fall, a doctoral seminar on Computers and Writing. I've got tons of notes on it, but I'm struggling a little bit with exactly how I want to (a) organize it, and (b) reduce the readings to a manageable set. Later today, I'll probably toss up a page that offers up my progress-to-date, but in the meantime, I thought I'd ask for a little collective wisdom. Here are my constraints:

The course is going to be 1/3 workshop, 2/3 seminar. That is, each week, we're spending at least an hour in our lab, where I'll be running a series of hands-on intros to a broad range of tools and platforms. The goal will be familiarity rather than mastery, of course, but I'm a big believer in the doing alongside the thinking.

One corollary of this is that I will be asking the students to work outside of class on their technology skills, and so I'll be requiring a little less reading than I normally might for a seminar. I'm pretty much decided that I'm not ordering books--my plans are to go with 3-4 chapters/articles per week.

And of course, the problem here is that a given week's topic could pretty much be the theme for an entire course, so I need to really distill rather than overwhelm. At the same time, I've got shelves and shelves of stuff I could use, not to mention all the stuff online. I'm still debating internally about whether it's best to shoot for a rough chronology of C&W or to focus on more recent developments for the most part.

Nothing to it but to do it, I suppose. Look for updates later today. Oh, and the collective wisdom part is this: what texts, perspectives, ideas do y'all think are indispensable for a course on C&W, one that's likely to be the only sustained exposure to the sub-d that these students will experience?

Backtastic

| | Comments (1)

Back to the SYR, back to the office, back to the grind.

The last couple of weeks, I've been sort of ignoring everything that's been piling up, and this week is time to pay the price. Do I promise to get this site back off the ground? Well, I fully intend to get back onto the blogging tip. But you can't break what you don't promise, so we'll see how it goes.

Expect a couple of posts in the next day or so, though.

Cautionary Graphics

| | Comments (1)

If you teach courses that involve information design, it can be really useful to have, and sometimes difficult to find, examples that are (a) actually published and (b) egregiously bad. There's a great instance of just such a negative example of info design over at Presentation Zen.

Karen-ival

| | Comments (2)

What, content?!

Yes, it's true. For a variety of reasons, my blog has been deep in summer slumber. But chatting with Derek about Karen Kopelson's recent piece in CCC, and the carnival thereupon, has functioned as the sharp stick, at least for the moment. Whether I'll ramp up the sleeping bear fully before the school year is still an open question.

I have a number of approaches to take to Kopelson's article, including a host of methodological concerns that seem to be the first line of inquiry I take with most of my academic reading nowadays. But I'm going to set them mostly aside for the time being; like Clancy, I'm happy to see the question of pedagogical imperative raised in explicit ways. Also, when Clancy writes, "It's not that I don't enjoy teaching or don't think it's important, but I came to the field another way," there's a healthy portion of that statement that applies to me as well. Where I differ, I suppose, is in that the teaching that I do that I find most fulfilling occurs in other places than the first-year composition classroom, and that's perhaps why I resent the "imperative" as much as I do at times. I think (and have said on occasion) that there are considerable problems in our field when it comes to graduate education. I think that, as students, instructors, colleagues, and professionals, we have allowed graduate instruction to remain mired in a model of education that plods happily along as though process never happened in our discipline. So, if you ask me, I'm still waiting for some of this so-called pedagogical imperative to take hold.

Now, that being said, I would raise one methodological complaint. And I raise it fully aware that it would be problematic in the context of Kopelson's article. There is indeed some value to knowing the extent to which lore about the dread "pedagogy chapter" circulates among graduate students and faculty. Potentially more valuable, it seems to me, and eminently possible, would be to match up these accounts against the dissertations actually generated both by the students of a given program, and those directed by the faculty who responded. Because honestly, the test of this imperative is less a matter of whether it circulates informally (because of course it does) and more a matter of whether or not it plays out across the dissertations in the field. Okay, that's all I'll say about method for the moment.

The other issue I want to raise, though, returns to the question of graduate education and the mentorship involved in any pedagogical interaction between writer and reader/director. One of the things that I learned early on, when I was muddling through my early years as an FYC instructor, was that "suggestions" coming from the instructor were very rarely interpreted as such. I learned instead to try and offer multiple choices in my feedback. Even now, I'm only sometimes better at it than others. But I like to think that it also helped me grow as a writer, someone able to take suggestions as such, think them through, and act on them as I see fit. What I'm getting at here, unfortunately, is that I think many of us forget this lesson when we enter the dissertation process. (And this is only one of the many things we forget, I'm afraid.) So it's not surprising to me that faculty might see the "pedagogical imperative" as more heuristic while their students perceive it as gospel. I've seen this pattern play out in all sorts of venues, with all sorts of students, in any number of contexts.

And this is not a matter of blaming the students, either. In many important ways, the dissertation should be about the coming-to-colleaguehood of graduate students, and to be sure, there are some faculty better at it than others. But it's a question with two answers--there are some faculty who will always make you feel like their student, and there are some students who will always treat you as faculty, even after a body's received the doctorate. Ideally, though, the dissertation is that final step into the profession as colleague instead of student, and the burden of that step is borne by everyone involved in the process. Or should be. From the students' perspective, this means an unfamiliar transition, one where they must learn to listen to faculty as colleagues rather than faculty. From the faculty perspective, we must be more cognizant of the fact that this is a transition, a process, and one where we must share some responsibility for it.

Personally, I try not to ask the "but what does this have to do with" question, because I recognize it ultimately for what it is, a dodge. It's a means of transitioning a conversation to pedagogy, when it would simply be more honest to announce "New topic! Tell me about your teaching!" I first got the question at my first CCCC in Cincy in 91, hated it then, and hate it still. It's one of those horoscopic questions for which everyone must have an answer, for which no one has a truly interesting answer, and about which most people don't honestly have much interest. It requires both a reduction of our work and a simplification of the classroom in order to answer, and the answer presumes a correspondence that doesn't really obtain for most people. It's lazy.

But I'm drifting far afield. That it exists as a pressure for our students I don't dispute. That it is asked far too often in interviews I don't question. That we will ever fully exorcize this ghost--we who are far too fond of speaking of "the discipline" as though it were real--I do doubt. But there are questions that we could be asking and answering that might render it a little less haunting:

-What percentage of dissertations in our field take the (FYC) classroom as the primary site of research? Has that percentage changed substantially in the past 5, 10, 15 years?
-Of those that do not, how many contain the obligatory pedagesture? Has that number changed?
-Is this pattern observable in other ways? For example, have topics shifted in particular journals?

And so on. It's not a critique of Kopelson to say that these questions might provocatively build upon her work here, because I appreciate the framing of these issues that she provides. Perhaps I am projecting, but some of the exhaustion I sense in her conclusion, exhaustion over the self-referentiality of our scholarship, comes from the fact that we do an awful lot of framing of our selves, to the occasional exclusion of actual research. This is a topic I'm worrying over in a current project, one close to my own heart as well. If the end result of this article (and even this discussion) is that someone takes up these questions, then I'll be grateful.

I'll probably need to return to some of these questions--my sense of textual pacing is a little rusty--but for the moment, color me finished.

Hall of Rain Game

| | Comments (1)

Under the umbrella

Meant to blog this a few days ago. On Monday, I went down with some folk to Cooperstown, to see the Cubs and Padres play in the annual Hall of Fame Game.

Unfortunately, we had to sit through a couple of brief hailstorms before the game was finally cancelled. The picture above came during hailstorm number two. I did get a few pictures, though, which I posted to Flickr for your enjoyment.

Kind of a bummer, as I'd been looking forward to seeing the Cubs, and possibly getting an autograph from Greg Maddux, who is my all-time favorite pitcher. And I'd been looking forward to it for a couple of months now. A 90-minute drive in soaking wet clothes and temps in the low 60s? Not looking forward to that so much. Ah well.

That is all.

Tagclouds are the new sexy

| | Comments (1)

Tagcloud for Area Cluster 106 (Information Technologies), CCCC 2007 (wordle)

Quiet round these parts, but I have a few bloggables I've been slow to post. Onesuch is the new tool Wordle, which whips together really attractive tagclouds. The above is a cloud of the keywords from the abstracts in area 106 from the 2007 CCCC.

Also of note is Krista's cloud of a dissertation chapter, which reminded me to post this...

That is all.

Blogging Conferential

| | Comments (9)

It's been a remarkably unconferential spring for me--I bailed on CCCC this year, am not going next year, and currently, RSA and C&W are happening without me, and doing just fine, I imagine. But over round Blogora way, Rosa asks, "who is livebloggin RSA in Seattle?" and the answer would appear to be no one. I've seen a couple of entries, and a handful of tweets, about C&W, but nothing steady. So I'm breaking prose silence to offer up a modest proposal, one I think I may have talked about before...

If I were hosting a conference, I think I'd see about raising money in order to have a bunch of folk blog the sessions. I know that there used to be something similar for CCCC, but I think that that was strictly a volunteer effort. So here's my proposal:

Offer 5 travel stipends to graduate students at $1000 apiece. To earn that money, they must commit to blogging at least one panel during the majority of sessions during the conference. (I can't be more specific, because it would depend greatly on the conference format, breaks between sessions, keynotes, etc.) For the sake of argument, let's say that that number is 10. So $100 per session.

In an ideal world, the organization would provide the laptops. That is coming closer and closer to becoming a reality, financially. My ultra set-up cost less than $300, and the prices on these things will only drop as Intel gets further into the game. But for the sake of argument, I'm going to assume that most would have their own or one they can borrow.

Also, lap desks. They don't need to be from Levenger or anything. You can get a good one at B&N for $30. It's worth it.

Also, a lounge/room set aside for them to store coats, bags, gear, laptops, with Wifi, cable hookups if they need, and bottles of water and bagels/muffins. Also, if they prefer to type up handwritten notes, they could do that here as well.

Someone from the organization would coordinate with them, so that all 5 aren't blogging the same panel during a given session, of course. But otherwise, they'd just be turned loose on the conference.

The upside? It'd be awfully nice for the majority of people in any organization who don't come to the conference, yes. But it would also provide a means of archiving what is now our #1 source of almost completely disposable scholarship. I've given some interesting papers now and then, and the only record of them outside of my hard drive is the paper title in the program. It would give all of us access to a largely untapped area of our disciplinary scholarship.

I'm not talking about posting the papers themselves, although I sometimes will do that for myself, so it wouldn't be an issue of a pre-print threatening those who want to publish longer versions later on. But a good blog summary of a panel would be enough to let researchers know if they'd like to follow up and email a presenter for a copy of the paper.

Or, imagine that you're putting together a panel on X for a future conference. It'd be nice to be able to do a search for folks working on that topic. Or to gather some ideas about possible folk for an edited collection. Or to get some idea about whose work you might want to follow up on for an article of your own about X.

Right now, the scholarship we do for conferences vanishes into the ether for the most part. Blogging the conference in a semi-systematic fashion would mitigate against that, and it would make all of us who don't attend every single conference feel a lot more connected. That wouldn't be a horrible thing, either.

Let's say that we have 1000 people in an organization, which is probably an overestimate for some and under for others. But given 1000 dues-paying members, it would take and extra $5 a year to pull this off, and the result would be access to a cumulative database of 150 presentations per conference (5 bloggers x 10 panels x 3 presenters/panel).

Finally, it would be a nice way to support our graduate students and it would be, I imagine, a really valuable introduction to the breadth of our discipline for those who participated. At conferences like RSA and C&W, the majority of the panels could be blogged. It would be a little more of a drop in the bucket at a conference like Cs, but that's the organization most capable of scaling this up beyond just 5 bloggers, too.

Seriously, I'd pay $5 or $10 more a year if a database from each year of the conference was the result. If someone could get on that for me...heh.

That is all.

Archives

Pages

  • images
Powered by Movable Type 4.1