Showing posts with label knitting. Show all posts
Showing posts with label knitting. Show all posts

Wednesday, January 25, 2012

This Post Is Made from 100% Procrastination

For the first time I'm understanding the difference between wanting a vacation due to desiring a break from a job I don't like, and wanting a vacation due to a sort of tired burnout. Maybe this is naive of me, maybe people who like their jobs are saying DUH, but at this point I could really use a couple of days where I don't have to do any work. I enormously enjoy each category of the work I'm doing, all for different reasons, but I'd really love a breather. My body could use a respite from teaching, too. I've been subbing a lot in the last couple of weeks, and although more money is always good, I think I'm ready to drop back to my regular schedule of (now) 6 classes a week rather than, for example, this week's 8.

My first reader has gotten back to me about the Greenland book, and because he's very kind, he has allowed me to go back and forth with him at great length about the manuscript. Last night I composed the third in a series of e-mails to him in Microsoft Word before pasting it into the body of the reply; with his paragraphs and my responses it was about 5,300 words. I feel guilty asking him to talk about my work in such great detail, but he continues to insist that it's okay.

The actual substance of his feedback has been very surprising. He told me that I've written a bummer of a book, something which is okay with me but which I hadn't really connected the dots to realize. He said that it was actually interesting and not impossible to follow the language, and that he didn't find the setup too holey, issues I worried over endlessly. He noted that there are many more characters than a modern novel usually has, and I honestly hadn't really thought of that. I don't know if it's a flaw per se, but both he and Matt said they had a hard time following who was who, so I think a family tree in the back of the book is in order. Just, like, not a complete one, or some surprises will be lost.

While I'm pleased to see that I've still got enough of the book in my bones to talk to him about it in detail, I find that I have zero motivation to dive into re-editing it. I definitely need further perspectives - especially from women, especially from people who like reading novels more than this friend does - but there are even a few easy fixes my friend pointed out which I could implement easily enough now, and I haven't exactly jumped right on that. I could do it, it's not a confidence thing, but I'm totally not interested.

I think it's because I'm working on the horror book, and don't want to dilute my writing energy back to a book with such an enormously different group of characters. So perhaps, after all, it was a bad idea to jump right into the new book without being completely finished with the old book. Of course, at my current rate of work, I'll be finished with the horror book by my tentative deadline (April) and definitely by my drop-deadline (June), and will be able to take a break between the full closed-door draft and the first open-door draft to hunker down on the Greenland book. Plus, I won't know until June whether my Greenland book won grant money, and I can't really send it out for publisher approval until I find that out. So maybe it worked out better this way, rather than worse. I'm just worried that the feedback will kind of dim in its fresh usefulness in my mind, and I won't remember all the resolutions I had for making things better.

Last night I knitted myself a coaster for my desk, so I could get rid of an old coaster with bad memories (um...never mind) and I put on The Social Network to amuse me whilst working. I still stand in utter awe of that movie's script. It's like All About Eve; I could put it on a continuous loop for about 14 hours and listen to it and feel smarter and smarter all the time. Every time I see it, someone else's performance jumps out at me. This time, again, it was Andrew Garfield's. I wanted to steal his character out of that movie and run off with him to Mexico the first time I saw it, and I felt that way all over again this time.

This was the result, by the way:


Turned out a little lumpier than I expected, but I don't have any emotional turmoil attached to it, and it'll keep condensation from ruining my desk. Which is the point.

Tuesday, October 25, 2011

Test Swatches

I am, um, not having a good week. If I had a dog, it would get run over tomorrow.

A phrase in Stephen King's On Writing that I've been thinking about lot lately is "shoveling shit from a sitting position". In full context, he tells us to keep writing, because your perceptions of your work can be wrong, and you can be doing good work even if it feels like you're shoveling shit from a sitting position. When I sit at my laptop and work on my Greenland novel, that is exactly, precisely what it feels like I'm doing. As if I'm just moving manure around with weakening arms, unable to get up out of the muck. But I felt the same way about the last work I did on my horror novel, until finally work on it just sort of...petered out, because I was tired of the perceived smell. But when I went back and read it months later, like magic, it had turned into something not-so-bad. So the thing to do, just as Steve tells us, is to keep going.

I've also been thinking about knitting and writing. One of the things you must do when you sit down to knit a new project is knit a test swatch. It's a little square piece of knitting meant to test how many stitches per inch you knit with these needles and this yarn. Everybody knits a little differently, with a tension that is greater or lesser - tighter stitches or looser ones - and you may have to change needle sizes or even yarn to make sure that your project comes out all right per the pattern. If you don't knit a test swatch, you can't be sure that the number of stitches in the pattern will come out to the same yardage on your finished product, and you might wind up with a garment that's too big, too small, or simply won't come together at all.

The thing is, when you cast on to knit a test swatch, you walk into it feeling as if the time you spend knitting these stitches is going to be wasted. You know that these stitches are going to be unraveled. The swatch is only for testing your gauge, it doesn't go into the finished product, so when you're finished with enough stitches to give you a decent area for measurement, rrrrrrrrip go the stitches and you have to wind the yarn up and cast on all over again, this time for the actual project. Or you start over with yet another swatch, if you've changed needles, or you have to abandon the project altogether because the yarn or the available needles just won't work.

To me, test swatches are tragic, and I hate doing them. I don't, if I can avoid it - if the project isn't tricky or I can find the same yarn with which the pattern was designed. I know at least one knitter who loves them. She thinks of them like mini-projects, and she even keeps some test swatches and labels them so she knows what her gauge was with those needles on that yarn. But I just can't help seeing them as anything but wasted effort.


There's a lot about writing that can be viewed from this perspective. Ira Glass reminds us that in order to get through the gap we just have to do a lot of work, knit a lot of test swatches that never end up making it into the finished product. It's frustrating as all hell, to have done all of this work and gotten theoretically no usable work out of it, but the thing is -

If you don't knit your test swatches, your "real work" can't happen at all. (That insight deserved a new paragraph.) Without knowing what your tension actually is, what knitting on those needles on this day looks like, you will never know whether the finished product is going to work. All of the words that you write and cut, slicing valiantly through them with your Fictator sword, were there for a reason; they were there to reveal the jewel of writing that existed underneath, all along. The mountain still has to produce a giant block of marble in order for Michelangelo to carve a beautiful sculpture out of it. Was the mountain's effort wasted?

So I'm trying, really hard, to write backstory that might never see the light of day, exposition that I will keep in my laptop for my own reference and no one else's eyes, chapters that I know, even while writing them, really are manure and will inevitably be cut. It's all of a piece; it's all work that helps me to write a finished product. Even if, at the time, it feels like a total waste, it all adds up to something.