Showing posts with label style. Show all posts
Showing posts with label style. Show all posts

Friday, May 1, 2015

That Comfort in the Kitchen

Last Saturday I was in my kitchen, preparing lunch: beet wraps from this cookbook. (A version of the recipe using European measurement standards may be found here; translating it should not be difficult for American cooks and is worthwhile, if you don't want to buy the book. Which is a good and useful book, if, oh, just a little pretentious. Now, back to our story.) I've made the recipe a number of times before. It is not a small amount of trouble, because it has so many elements that must each be prepared individually - cook the quinoa, toast the walnuts, zest the orange, blitz the beets with the goat cheese (measuring all the while), grate the apple, slice the avocado. The resulting flavor combination is so unique, though, that I enjoy making it when I can manage to get all the ingredients together.

The prior week, I'd made a strange chilled borscht from this book, and I bought and boiled too many beets for the recipe. So I had some leftover cooked beets. I also had a whole package of unused herbed goat cheese from yet another recipe; I'd bought the right amount of bell peppers to roast, but twice as much goat cheese as I needed. This is how my kitchen often operates: I get the amounts wrong when I'm shopping, or I find when I'm on the point of making the dish that I should halve the recipe or we'll be eating weird borscht for weeks. This M.O. means that the following week I need to search my cookbooks or the internet for recipes that will use up last week's excesses. Never a dull evening.

I cannot read the caption on this and I badly want to

So I had leftover beets and leftover goat cheese, but they were in different proportions than the recipe called for. I also had herbed goat cheese instead of plain. Also also, I didn't have any walnuts, nor any raisins, so I was using pecans and just going without raisins. My common practice for cooking quinoa is to use half vegetable broth (or chicken broth, whatever's on hand) and half water to cook it in, because it makes the quinoa more flavorful. When the recommended cooking time is over, I turn off the heat, drape a doubled dishtowel over the pot, and put a lid on top. I let it sit for 10 to 15 minutes or until I need to serve. This is a trick I learned from a rice pilaf recipe years ago, and it keeps the quinoa from being either soggy or undercooked. The beet wrap recipe calls for cooking the quinoa in plain water with no after-steaming.

I was considering all these changes with amusement as I was grating the apple (half an apple, I've found, is plenty), and a lightbulb went on over my head so brightly that Matt noticed, from the living room, where he was occupied with something else. I stood perfectly still and let the light penetrate every brain cell it could, and then I noticed Matt noticing me.

"You okay, there?" he said.

"Yeah," I said. "I just figured something out."

"I can see that," he said.

Wednesday, April 22, 2015

Precision v. Grace, Classical v. Jazz (or The Great Oz Has Spoken)

Last week I sort of unintentionally reread some feedback a professor gave me about a year ago.
While this piece feels done, it’s felt done from the beginning, and done in a way that, as impressive as the writing is, feels like there’s a cap on, holding everything together deliberately and tightly. I know this is what most writers aspire to, at least for a while. And then there’s the next stage, which involves letting go of all that tight control to dig deeper, to burrow, to be surprised. I think I already said this, and if not, shame on me. But really, if you can write this well, Katharine, imagine how well you might write if you were really writing. And by that I mean working the language intransitively, not acting upon but acting – not writing about (the self), but writing (the self). You clearly have all the craft skills you need to stop thinking so clearly in meaning. 
This feedback confused me. Even after I achieved some distance and met with the professor, the way forward did not come clearer. (I still didn't understand it particularly well in rereading last week.) But I set it up in the back of my mind, kind of like a canvas backdrop, while I went on and wrote to the best of my ability.

I blogged last fall about how much despair ensued when another professor unknowingly echoed what the first one had said. The backdrop rippled a little, starting to appear more realistic and less like scenery, but I still didn't know what to do with it.

This blog post does not tidily conclude with me figuring it out.

Wednesday, December 17, 2014

English as Acrobat, or the Folly of TOCWTS

Several weeks back, a blogger that I really should have stopped reading by now asked in a post whether the correct styling was As and Bs or A's and B's. This question actually can't be answered, believe it or not, and within it lies an invaluable writing/editing lesson for a certain type of person. If you couldn't care less about punctuation mechanics, this post might run a little dull for you. (And, by the way, if you couldn't care less about punctuation mechanics, what are you doing reading this blog?)

In my view - those three words apply to the rest of this paragraph - apostrophes are only available as punctuation when substituting for other letters in contractions (would not --> wouldn't) or when indicating possession (Krycek's prosthesis). A's and B's is not a possessive construction, it's a plural construction, and apostrophes cannot be used correctly when pluralizing nouns. Even though styling it As and Bs can be a little confusing, because the first item in the list looks like a capitalized version of the word "as", it’s still the mechanically correct style. And anyway so much of English syntax and grammar depends upon context, upon user effort, and As and Bs will only be confusing for as long as it takes the reader to read through the next two words.

I was not the first commenter on the relevant blog post, and one of the earlier commenters laid down that it was definitely A's and B's. I commented and specifically said that I didn't want to get into an argument, but that in my view, apostrophes can't ever be used for possession, etc., basically a short version of the paragraph above. I noted that I had three years of experience as a copy editor. The prior commenter responded pretty rudely, saying that whoever was paying me to be an editor should be made aware that they were paying someone incompetent, and noted that she had many more years of experience editing than I did. I sort of went  ¯\_(ツ)_/¯ on it, and said that my company followed the Chicago style guide fairly closely but that we had our own house guide and that, of course, style guides vary. The commenter responded by quoting a passage from Chicago that kinda proved my point rather than hers, and then closed with something like "the vast majority of writers and editors would prefer A's and B's."

A Google Image search of "grammar Nazi" turns up all kinds of delightful stuff,
including things I feel really bad laughing at 

Like I said, I didn't want to get into it. Apostrophes are a sore point with me because they are so often misused out there in the non-grammar-devoted world, and this commenter was unpleasantly aggressive, and that combination meant ¯\_(ツ)_/¯ was the way to go. So I didn't respond a second time.

But I knew without a doubt that the commenter was invested in a phenomenon called The One Correct Way To Style. TOCWTS is something that I thought existed in the years before I was a copy editor, but I now know something that, if you are a picky, grouchy grammar fiend like me, take heed, weary one, because this will make your future life a thousand times easier: it does not exist.

There is no one correct way to do certain kinds of punctuation and styling in English. There just isn't. There are different styles, and which one is used in whatever it is you're reading depends on 1) the publication and 2) the context. That's all. No other big rule in the sky; the publication and the context. Some organizations use Chicago, some use AP, some use house rules. If you're the one writing, with no other answerable party, which one is used depends on your preference and potentially on your investment in the rhythm of a sentence. So the rude commenter was right, it's A's and B's, but so was I, it's As and Bs.

(dies laughing)

In this blog I use the Oxford or serial comma, meaning that in a list of three items, a comma appears before the last item in the list. Mulder, Scully, and Skinner. In quite a lot of style guides, the second comma, after "Scully", is not correct. For me, this is nuts, because it causes unnecessary confusion, but for the Washington Post, it's the law. I also would say (contrary to the style guide of the company where I worked for three years) Jesus's taxes or Texas's fertilizer, rather than Jesus' taxes or Texas' fertilizer. Not because one or the other is correct - neither is correct or incorrect (!!), it depends on the style guide - but because the apostrophe hanging out there looks weird to me on a non-plural noun, different than the friends' convictions or the creatures' fangs, for example. And I would always say As and Bs, because apostrophes matter a hell of a lot to me, but if I worked for a company or a client that insisted on A's and B's, I would cringe and correct for that. Because that's how it's correct in that context. No immutable TOCWTS exists for that phrase. It's all context.

There are rules of English punctuation and style that do not bend. The difference between it's and its is not negotiable. But English is a remarkable acrobat, flexible and strong and death-defying, and there is no one way to be an acrobat. Once I accepted this, the arguments I was willing to have about punctuation and grammar dropped to nearly zero. Because if there's no one correct way to do certain stylings, who's to say that I know the one correct way to use any of the rules I've always considered immutable?

From here, I could ramble awhile about poststructuralism, and how my whole worldview seems to be heading in that direction as I get older and learn more - truth dissociating itself from certainty, and vice versa, and things getting really malleable and interesting and me thinking that yeah, this is how life really is, lived in the liminal spaces between this rule and that reality - or I can give you a concrete example, hastily created in Paint, to sum up.



Neither one is wrong. They are both acceptable. It just depends on where, when, and how you are.