What do we teach?

Jaci Wells's picture

I'm teaching Business Writing this semester for the first time, so I'm in the PW mentoring class. This is the first time in a long time that I'm teaching a brand spanking-new class, and it's that way for many of the folks with me in mentoring. Teaching the new course and taking mentoring has led me to return to many of the same fundamental questions about teaching writing that I first had when I started. The one that comes up more than any other is, what exactly is the range of what we should be teaching in writing courses?

In my PW mentoring, there are two different schools of thought. One school believes that we shouldn't expect our students to do anything that we aren't willing to teach them. If we're going to assign them a PowerPoint presentation, in other words, we should be prepared and willing to teach them how to use PowerPoint. The second school of thought believes that we are there to teach rhetoric and rhetoric alone, and that it is the students' responsibility to learn the tools that will help them create the rhetoric they want to create. These tools are typically computer applications. A very vocal few in my mentoring class believe that it's perfectly acceptable to expect students to create documents using Publisher, Dreamweaver, Adobe, etc. without being prepared or willing to teach these applications or even spend class time answering basic questions about them.

I have always held the philosophy that, within reason, I don't hold my students responsible for things that I don't teach them in the class. It's always seemed unethical to me to expect them to know things I'm not going to teach. (Again, this is within reason--I think it's pretty acceptable now to expect students will know how to use Microsoft Word. But even with things that are second nature to most students, like Word and the Internet, I have helped students one-on-one.) I have always seen it as unacceptable and unethical to expect my students to make a website with Dreamweaver if I'm not willing to show them how to use it.

One of my PW mentors reminded me that this line of thinking, even though it feels more comfortable to me, has often worked to make English classes like composition and even business writing a dumping ground for everything that no one else has the time or the desire to teach. He explained that, when he taught high school, this was something he fought constantly. If we want to prevent English courses (he argues) from becoming this sort of dumping ground, we have to set up some strict boundaries as far as what we're willing to teach. I do tend to feel overwhelmed by the amount of material I could potentially cover in my Comp and PW courses, so any way to limit the amount I have to cover is appealing to me. I also like the idea (especially in the Business Writing course) of making students responsible for going off on their own and learning new things of their choosing, without me forcing them to. At the same time, though, putting this much responsibility on the students still seems a little off to me. I also worry that encouraging them to learn applications on their own that will allow them to create documents for my course focuses too much on the product, since the idea is that they should do--independently of me--whatever they need to do to produce.

This post is less of an argument than an exploration (or rambling). I'm curious--where do you guys stand on this?

Comments

pepper's picture

Learn it Your Damn Self, Kid!

As you know, basically every assignment in my 106 class is a multimedia project. Throughout the semester my students end up using Dreamweaver, PowerPoint, Photoshop, Flash, Windows Movie Maker, Front Page, and probably some others. Each of these programs gets one day of instruction on usage during a computer lab day. I state clearly in my syllabus that I expect them to spend considerable extra time on learning the programs outside of class, and I make this statement with no qualms. Three semesters in and I have not been let down yet. Oh sure, some pull off more "wowing" assignments than others, but this is true of any assignment. Most of the time, they pull off things with the programs that even I have absolutely no idea how to do (especially with movie maker). I feel that getting your hands dirty and jumping into the program is the best way to learn them. That's how I learned every single visual composition program I know. Before the end of last semester I said, "Hey self, I think you should learn Flash. Why not start today?" And my self replied, "Good idea, self. Let's jump to it." A few hours later I had the basics, and I learned more each time I used the program.

I can't speak for the students, but I've never recieved one complaint about my out-of-class, teach yourself expectations. I'd like to think they realize they're teaching themselves a potentially usefull skill, therefore the time committment doesn't feel so bad. It probably feels more useful than spending hours struggling over an essay that's destined to be read, graded, and thrown away. And overall, I find our students far more technically and visually savvy than we give them credit for. The thing to remember is who are students mainly are-- let's face it, a bit privilaged. Teaching at other places without the same access (sorry Nick, but it does all come back to access) would obviously pose more problems.

Jaci Wells's picture

Pepper, It's good to know

Pepper,

It's good to know that you've been successful pretty much telling students to learn the programs themselves. I've been doing more multimedia assignments the last couple of semesters than I did when I first started teaching, but I've kept these assignments low-risk and I haven't focused on them as much as the more traditional assignments that I also give. I've been thinking, though, that I'd like to include more multimedia projects, but I've been worried about how much time I'd then be required to spend on teaching the programs themselves. So, it's good to hear another teacher's perspective on it. I think sometimes that I'm pretty naive about what, exactly, students are able to do; I also think you're right in saying that our students are probably more technically savvy than we give them credit for.

Wells