Student first chapters and outlines -- a great way to get a feel for what my students are going to be working on this year, though sometimes one will change horses midway through, but that's okay.
Trouble is that most of them have been together for a year already and know each other's novels intimately, whereas this is the first time I've seen them. It's more work for me, of course, but well worth the time and is always interesting to see where they're coming from. I've also had them talking about their novels and filling out a questionnaire, so hopefully I'll have a good handle for where they're coming from.
One of the worries that someone will always have is what if what they're writing isn't my thing. I'm a genre fiction writer, which their first year teacher wasn't, so the genre writers are always happy to discover that. (And it's a great balance to have.) But even so, there can be that persistent niggle. And really it doesn't matter. There will always be books that aren't quite my thing, but it doesn't mean I can't look at them objectively to see whether they're working, how well executed they are. I'm more interested in the craft than whether something rings my particular bells.
One of my pet peeves in workshopping is the workshopper who says they can't comment on something because it's not their genre. What a cop out. I was in a workshop once where someone had written a magic realism story and every workshopper except me and the workshop leader used that line. It was hardly fair to the poor writer who had made detailed comments on everyone else's stories even though they weren't in the same genre as what she was writing. Anyone can comment on craft, and, really, one of the great pleasures of teaching writing is the variety of projects we get to work with, so students shouldn't worry about such things but should rejoice in the fact that they're writing something only they can write.
Showing posts with label students. Show all posts
Showing posts with label students. Show all posts
07 March 2010
23 January 2010
Contemplating the holidays' end . . .
It's that funny thing when you work in teaching that half of me wants the holidays to go on forever (who doesn't, right?), and yet the other half is excited about starting new classes with new students, wants to see how many students we'll get at enrolment, who will be in my classes.
Our course is more hands-on between year's end and beginning because we do so much work on student selection. Oh, in some ways, I envy the courses that just look at TER (Tertiary Entrance Rank). This is the least of our concerns; we do consider TERs, but only as part of a much larger package. We also get a statement of why students want to do the course, a folio of work, which we have to read and appraise, we get them in for an interview, we get them to do writing on the day, which we read and appraise, and we give them a short grammar skills test, which we then have to mark. Only when we've done all of this can we make our selections. The extra work is worth it because it helps us weed out those who won't be able to cope with the course.
But back to the end of the holidays -- the thing I love best is not having to live my life by a timetable: not having to get kids off to school, not having to be at work early to make sure I get a car spot, the more relaxed atmosphere in the house (ie not having to nag kids about homework, which I know doesn't work, but I find I can't help myself), not having to work and think when it's stinking hot. I'm less social and more family orientated in the holidays, and we do so much more. This holidays the theme has been Avatar, which I'm sure you've noticed! Last year it was "Spooks" -- we watched the first six seasons, averaging two or three episodes a day. We also do a lot of swimming. The kids play computer games, and I write. And read. I have this funny relationship with reading because I love doing it -- and really I read all the time, but not in extended bursts like I do over the holidays -- and I know I need to read lots as a writer, but I feel guilty if I sit down to read a book. It must be my mother's voice in my ear, telling me to clean up, or the writer telling me I should be writing! But in the holidays there's time to do both. (Note, I didn't say all three. My mother's voice is still in my ear!)
19 February 2009
Launch of new short story collection
Sherryl and I have just been to the launch of Scribe's New Australian stories (ed. Aviva Tuffield), mainly because one of our past students, Demet Divaroven has a story in it. And isn't that a fantastic thing for a teacher: going to see your student successes!
Aviva spoke about the health of the short story, which is always a concern for short story writers. I have to admit that before I started writing seriously, I hardly ever read short stories. I've learnt, over time, to appreciate them -- and perhaps part of the problem for me, originally, was that most times when I'd encountered them it was in buying science fiction books that I thought were novels. I'd be all set, engrossed in a story, and then it would end. (Truth be told, many of these were probably novellas rather than short stories.) I'd always be so disappointed when they finished, and felt ripped off. I'd become emotionally engaged with these characters and was ready for the long haul, only there was none, and I do love the long haul! I thought I hated short stories. Really, I don't think I did -- what I hated was not having my expectations met. This is a concern for all writers, or should be. But that's for another post.
These days when I read short stories, my expectations are for a different type of experience. I love the short story form. Many believe they're easier to write than novels, but I don't think so. Shorter, yes. Don't take as long. But not easier.
They're often talked about as the training ground for a novel, and they really can be this. This is not to say that all novelists write short stories. They don't. Nor do they need to. Nor is it any kind of slight against the short story or implying that the short story is, in any way, inferior. It's not. It's just that the short story form, because it is shorter, can teach you a lot about structuring fiction. In the time that you write one 80,000 word novel, you can write many short stories, learning how to get in and get out of the story, how to show rising tension, a whole host of factors. This gives you time to improve, experience. To get that same amount of experience in structure, you'd need to write several novels. Many novels. That's going to take longer. So the short story is like a short cut to gaining useful writing experience.
One thing Aviva spoke about, which I'd never really thought about, was how the publishing of short stories has changed. In the past, new writers often began with a short story collection and then graduated to novels, whereas these days most short story writers need a successful novel or, better, a few successful novels published before they can get a short story collection published. I knew both of these things, but somehow I'd never quite juxtaposed the ideas and thought about that change. (And of course there are exceptions to this, particularly with small press publishers, but there are also publishing houses that never seem to touch the short story.)
These days, we're more likely to read our short stories in literary (or genre) magazines. The mass market magazines do publish a few, but some will only take these through agents. But if we all do want to see more short stories published then we have to let the publishers know this in the one way they really care about: book sales.
Labels:
book launch,
publication,
short stories,
structure,
students
17 April 2007
Becoming a student
Every few years every teacher should have to become a student again to see what life's like on the other side of the teacher's desk. At the moment, Sherryl, Susanna (another fellow teacher) and I have joined our students in a class learning how to use Dreamweaver.
Since the class began, I have swapped computers in the computer lab, and had previously downloaded some files onto that first computer because I didn't have my USB stick with me. So today I started by redownloading the files (that I was already supposed to have) onto my stick. Now my stick is quite old, so quite small by modern standards, and I hadn't realised it was full. So here I was trying to get files that wouldn't load, and meanwhile the teacher had moved on to something else. By the time I realised what my problem was, I was so far behind that I had almost no chance of catching up, and though I had been listening, the amount of information was such that I had no hope of remembering it. And I didn't.
As the class went on I felt I was really floundering, and though I did catch up in the end, with some help from Sherryl, the experience was a timely reminder of how students can struggle -- even those that we might expect to be coping or who might look like they're coping. There are lots of reasons students won't speak out about the troubles that they're having. I'm a fairly open person, and don't mind being honest about things like that. But not all students are. Sometimes they won't speak out for fear of looking silly, or because they're shy. (I used to be like that.) They might think asking questions will make them look like they're sucking up, or might piss off their peers.
I tell my students that there's no such thing as a stupid question in my class -- and I do welcome all questions. I had that lesson driven home to me when I was doing my science degree. I remember a student asking what I thought was a genuine question, and the teacher saying, "Oh, so we have one of those, do we?" And then going on to ridicule this guy for asking what she thought was a ridiculous question. My respect for her plummeted, and ultimately if you haven't got the respect of your students, you haven't got any chance of having a successful and rewarding class.
Since the class began, I have swapped computers in the computer lab, and had previously downloaded some files onto that first computer because I didn't have my USB stick with me. So today I started by redownloading the files (that I was already supposed to have) onto my stick. Now my stick is quite old, so quite small by modern standards, and I hadn't realised it was full. So here I was trying to get files that wouldn't load, and meanwhile the teacher had moved on to something else. By the time I realised what my problem was, I was so far behind that I had almost no chance of catching up, and though I had been listening, the amount of information was such that I had no hope of remembering it. And I didn't.
As the class went on I felt I was really floundering, and though I did catch up in the end, with some help from Sherryl, the experience was a timely reminder of how students can struggle -- even those that we might expect to be coping or who might look like they're coping. There are lots of reasons students won't speak out about the troubles that they're having. I'm a fairly open person, and don't mind being honest about things like that. But not all students are. Sometimes they won't speak out for fear of looking silly, or because they're shy. (I used to be like that.) They might think asking questions will make them look like they're sucking up, or might piss off their peers.
I tell my students that there's no such thing as a stupid question in my class -- and I do welcome all questions. I had that lesson driven home to me when I was doing my science degree. I remember a student asking what I thought was a genuine question, and the teacher saying, "Oh, so we have one of those, do we?" And then going on to ridicule this guy for asking what she thought was a ridiculous question. My respect for her plummeted, and ultimately if you haven't got the respect of your students, you haven't got any chance of having a successful and rewarding class.
Subscribe to:
Posts (Atom)
