I assign minimum page requirements to stick it to my "do-as-little-work-as-possible" students. They get back at me by making me read what they write.
No, really, though. My students always want to know how little they can get away with doing. (I say "my" as if it's unique to me. Everybody's students want that.) In most of my formal writing assignments, I tell them a minimum of 3 pages. I specify margins, acceptable font sizes, spacing requirements, everything. That's what my high school English teachers mostly did; that's what I do. I tell them that when they get to be crack journalism students, they will be able to write comprehensively about a topic in fewer pages, but for now, just do it.
Students go to extraordinary lengths to hit the page requirement, without actually doing any more writing. It's amazing. Instead of a punchy conclusion, the last line of the paper is occasionally a drawn-out, run-on monstrosity with more clauses than a sack full of catses. (I've been waiting years to write that joke.) I imagine that that's why the model shifted to the introduction--3-body-paragraph--conclusion model; that way nobody has to care what the page requirement is. (Weirdly, though, everyone still does. Evidently, this includes the people who assess the ACT writing section.)
Once I get an efficient system for turning papers in digitally (Google Docs, Moodle, I'm looking in your direction), I can use a word count system as a way of judging minimum lengths. But the point is that I hate that kind of nonsense. It's stupid game-of-school stuff. There's nothing magic about three pieces of paper with ink on them, especially if the third one has exactly seven words printed on it; there's nothing magic about 1500 words, especially if 400 of them are "very". It's just that most students stop thinking far too soon without some kind of minimum requirement. The minimum requirement doesn't seem to be any help, either.
Maybe in the future, when I get better at teaching and grading by rubrics, I'll be able to show students that a minimally good paper will probably take up 3 or more pages, but that I'm not grading by weight. In the meantime, I have 35 pounds of papers to grade.
Readers: How do you ensure that your students put an adequate amount of thinking into your writing assignments? I'm talking Tier-I, fully functional, basically good high school writers. Everybody knows that some students will never do that, and some will only do it when people sit next to them and say, "Get back to work" every 15 seconds. I don't mean them.
Showing posts with label thinking skills. Show all posts
Showing posts with label thinking skills. Show all posts
Monday, May 9, 2011
Sunday, November 21, 2010
To my students: Thinking vs. knowing
or,
The difference between when I ask you a question and when you ask me a question.
It's a common enough scenario in our class: I ask you a huge question, give you no guidance or background information, and demand that you analyze, choose and defend a position on it in three minutes. I imagine that this is frustrating for you sometimes, especially since my skills at communicating my goals are not great.
This happened on Friday, and instead of just answering the question, one of your classmates responded, and then said, "What do you think about this topic, Mr. Cosby?"
I didn't exactly deflect the question, but I didn't exactly answer it right away, either. I think I said something about not wanting to presume to know everything, to which somebody said, "Well, you expected us to know the answer."
It reminded me of a few days earlier, when I asked you about a camera angle in To Kill a Mockingbird. "Why put the camera there for this scene, and why not somewhere else?" One of your classmates asked, "Does this have a correct answer? I like things that have correct answers." My response to that was similar: There may well be a correct answer, the director made that decision for a reason. I can only guess at what it was. The better I am at the language of film, the more likely my guess is to be close to correct.
The common theme to these two scenarios, dear readers, and the theme that connects a thousand others just like them, is this: When I ask you a question like that, it's because I want you thinking about the answers. I want you to come up with what you think the best answer is, and I want you to defend it. When presented with new evidence, I want you either to explain how the new evidence fits into your position, or I want you to change your position to accommodate it. I do this because I think that this is the most reliable way for people to learn. There's something pretty Socratic about it, and I'm not sure how I feel about that, but there you go. That's pedagogy for you. I don't expect you to have the right answer every time, the first time. You often get the right answer, or at least a right answer, because you're smart. And even when you're off-base, you quickly come to a right answer. But for our purposes, that's sort of the cherry on the sundae. I want you to think in as many different ways as possible, and I want you--and this is the kicker--to be aware of your thinking as you do it.
When you ask me my own questions back, there's a different dynamic. Based on past experiences, you imagine that I have answers to all the questions I ask. Maybe you visualize a Teacher's Annotated Edition of To Kill a Mockingbird, which gives me questions to ask and themes to present. Such things exist, and I use them when my own thinking is unclear or incomplete, or honestly, when I'm in a hurry. So I feel like when you ask me a question, it's because you want to know the answer, and you want me to give it to you. Your motivations are your own--I like to think you're checking your own thinking process against that of a respected local authority. You may simply be tired of thinking. But the point is this: When you ask me a question, it's because you want the answer.
The problem with that is the nature of the questions I ask: "What are the qualities of leadership? What does a society owe its people, and what do leaders owe to unwilling members of a society? How do stories and leadership relate?" These questions have no one answer. My objective is not for you to know how to answer them, it's for you to know how to ask them.
So, just keep thinking. A lot of good will come of that, far beyond the limits of school.
The difference between when I ask you a question and when you ask me a question.
It's a common enough scenario in our class: I ask you a huge question, give you no guidance or background information, and demand that you analyze, choose and defend a position on it in three minutes. I imagine that this is frustrating for you sometimes, especially since my skills at communicating my goals are not great.
This happened on Friday, and instead of just answering the question, one of your classmates responded, and then said, "What do you think about this topic, Mr. Cosby?"
I didn't exactly deflect the question, but I didn't exactly answer it right away, either. I think I said something about not wanting to presume to know everything, to which somebody said, "Well, you expected us to know the answer."
It reminded me of a few days earlier, when I asked you about a camera angle in To Kill a Mockingbird. "Why put the camera there for this scene, and why not somewhere else?" One of your classmates asked, "Does this have a correct answer? I like things that have correct answers." My response to that was similar: There may well be a correct answer, the director made that decision for a reason. I can only guess at what it was. The better I am at the language of film, the more likely my guess is to be close to correct.
The common theme to these two scenarios, dear readers, and the theme that connects a thousand others just like them, is this: When I ask you a question like that, it's because I want you thinking about the answers. I want you to come up with what you think the best answer is, and I want you to defend it. When presented with new evidence, I want you either to explain how the new evidence fits into your position, or I want you to change your position to accommodate it. I do this because I think that this is the most reliable way for people to learn. There's something pretty Socratic about it, and I'm not sure how I feel about that, but there you go. That's pedagogy for you. I don't expect you to have the right answer every time, the first time. You often get the right answer, or at least a right answer, because you're smart. And even when you're off-base, you quickly come to a right answer. But for our purposes, that's sort of the cherry on the sundae. I want you to think in as many different ways as possible, and I want you--and this is the kicker--to be aware of your thinking as you do it.
When you ask me my own questions back, there's a different dynamic. Based on past experiences, you imagine that I have answers to all the questions I ask. Maybe you visualize a Teacher's Annotated Edition of To Kill a Mockingbird, which gives me questions to ask and themes to present. Such things exist, and I use them when my own thinking is unclear or incomplete, or honestly, when I'm in a hurry. So I feel like when you ask me a question, it's because you want to know the answer, and you want me to give it to you. Your motivations are your own--I like to think you're checking your own thinking process against that of a respected local authority. You may simply be tired of thinking. But the point is this: When you ask me a question, it's because you want the answer.
The problem with that is the nature of the questions I ask: "What are the qualities of leadership? What does a society owe its people, and what do leaders owe to unwilling members of a society? How do stories and leadership relate?" These questions have no one answer. My objective is not for you to know how to answer them, it's for you to know how to ask them.
So, just keep thinking. A lot of good will come of that, far beyond the limits of school.
Subscribe to:
Posts (Atom)
