Skip to main content

Online Feedback in Writing Courses

How do I respond to student writing using online technologies?

I tend to make extensive use of Microsoft Word's "track changes" and "reviewing" modes. The real challenge for me as an instructor is to not make every edit for a student.

My primary concern, and research seems to support this, is that students have been inculcated with the notion that you make the suggested corrections, no more or no less, and that is what constitutes "revising" a paper. Online, this habit becomes even easier... cut-and-paste or simply "accept change" and the revising is "done" in the view of many students.

When I first started student teaching, in the late 1980s, I fell into the trap of making too many comments on papers. Now, I try to minimize how often I correct mistakes students need to discover. I also do not make as many suggestions as I did years ago.

Online tools have made editing and leaving short comments much easier. For all the dangers of relying too much on helpful "hints" from Word or the Mac's built-in dictionary, I think students do benefit from technology when writing. I love moving paragraphs with "drag-and-drop" simplicity.

When writing is done online in threaded discussions, I encourage students to respond only to the ideas and the rhetorical arguments they read in the posts. Sometimes, they cannot resist correcting an obvious grammar or spelling error, which is okay, but I want them to reply to something more than the surface mechanics of a text.

I moderate occasionally online, usually more in the first weeks and less as the class progresses. I'm still trying to find the right balance of involvement to encourage longer and more thoughtful online responses to peer texts.

Blackboard's online system includes an option of interactive editing and comments. I wish the Web/Vista platform included a similar "markup mode" to help students. I like the "Post-it Note" style of the comments in Word and Pages a lot. Students read the comments and know that I am an engaged reader. I think they need to know the words are being taken seriously.

Honestly, I don't think I could switch to an all-paper process for giving feedback to students. I can type a full-page critique of a paper, using color coding to indicate where a paper was weakest and where it was strongest. I love the visual cues, both for my own use and for students' use.

I put important thoughts in bold type and I will use colors, too. I want students to remember my feedback!

One risk of online editing is that students might come to expect the "spreadsheet" style checklists of "points possible" found in Web/Vista. While having a rubric can help students, I also need some flexibility as a teacher. Students will argue for grade points based on a rubric, instead of focussing on the overall quality of a text. I think this is a serious problem with rubrics, which online systems seem to enforce without the flexibility I want as a teacher.

Comments

Popular posts from this blog

MarsEdit and Blogging

MarsEdit (Photo credit: Wikipedia ) Mailing posts to blogs, a practice I adopted in 2005, allows a blogger like me to store copies of draft posts within email. If Blogger , WordPress, or the blogging platform of the moment crashes or for some other reason eats my posts, at least I have the original drafts of most entries. I find having such a nicely organized archive convenient — much easier than remembering to archive posts from Blogger or WordPress to my computer. With this post, I am testing MarsEdit from Red Sweater Software based on recent reviews, including an overview on 9to5Mac . Composing posts an email offers a fast way to prepare draft blogs, but the email does not always work well if you want to include basic formatting, images, and links to online resources. Submitting to Blogger via Apple Mail often produced complex HTML with unnecessary font and paragraph formatting styles. Problems with rich text led me to convert blog entries to plaintext in Apple Mail

Learning to Program

Late last night I installed the update to Apple's OS X programming tool suite, Xcode 4. This summer, in my "free" time I intend to work my way through my old copy of Teach Yourself C and the several Objective-C books I own. While I do play with various languages and tools, from AppleScript to PHP, I've never managed to master Objective-C — which is something I want to do. As I've written several times, knowing simple coding techniques is a practical skill and one that helps learn problem solving strategies. Even my use of AppleScript and Visual Basic for Applications (VBA) on a regular basis helps remind me to tackle problems in distinct steps, with clear objectives from step to step. There are many free programming tools that students should be encouraged to try. On OS X, the first two tools I suggest to non-technical students are Automator and AppleScript. These tools allow you to automate tasks on OS X, similar to the batch files of DOS or the macros of Wor

Learning to Code: Comments Count

I like comments in computer programming source code. I've never been the programmer to claim, "My code doesn't need comments." Maybe it is because I've always worked on so many projects that I need comments  to remind me what I was thinking when I entered the source code into the text editor. Most programmers end up in a similar situation. They look at a function and wonder, "Why did I do it this way?" Tangent : I also like comments in my "human" writing projects. One of the sad consequences of moving to digital media is that we might lose all the little marginalia authors and editors leave on manuscript drafts. That thought, the desire to preserve my notes, is worthy of its own blog post — so watch for a post on writing software and notes. Here are my rules for comments: Source code files should begin with identifying comments and an update log. Functions, subroutines, and blocks of code should have at least one descriptive comment.