Pithy Writing Advice

I don’t hate all writing advice but I am a bit choosy, and I tire often of too much navel gazing in this area. Also, a little bit of advice goes a long way.

In that vein there are a couple of ideas about writing for “new” writers that have been floating across my mind recently. And I’ve stolen this all from various podcasts and essays and books, so while I’ve curated this collection, I am not responsible for its production.

  • You don’t have to write. There are more effective ways to make a living, there are more social things you could be doing with your time, so if your writing is making you miserable, then don’t do it. It’s ok.
  • We’re horrible judges of the comparative quality of our own work, particularly in the moment. What feels good and what feels bad when we’re writing something, isn’t always a very good indicator of quality.
  • Crap gets published all the time. Not submitting things for publication because you think it’s crap is probably an elaborate self-deceiving procrastination ruse.
  • Beginnings matter a lot, probably more than any other singular part. If nothing else, beginnings need to be punchy. You certainly don’t have more than a page in which to suck people in, in general, and beginnings which drag lead no where good.
  • Cleverness and ingenuity are not substitutes for emotional content.
  • Big projects are made manageable by subdividing them into smaller more manageable pieces.
  • One need not formally outline, or systematically do some sort of pre-writing, but sitting down in front of your computer or notebook with a blank page/window open without the experience of working through what you plan to write--even if it’s only in your head--you’re probably going to frustrate yourself.

un-creative writing

I have never, really, taken a creative writing class.

When I talk to people about writing, I think people always assume that I studied creative writing, or that the whole graduate school thing was about writing programs or some such.

And while I respect and a number of people who are involved in the discipline of “creative writing,” I am not terribly enticed either by the possibilities of the field as a dialogue, or by the utility of the training for myself.

This might be a personal short coming, as I have always (since I was a teenager) been pretty resistant to “formal writing education,” and it might be a genre thing (science fiction doesn’t fare terribly well in CW programs on the whole, often relegated to “children’s and popular literature” tracks, if not totally spurned.) In any case this was highlighted by an article I read last week that suggested, what I thought was an utterly flawed writing methodology.

The basic idea was that as a general practice, you rewrite everything, on the theory that you basically can never get something right the first time, no matter how much time and effort you spend on it, and that the second time you sit down with a piece that you’ve written, only then can you really get it right.

Now, the technicality is that she’s probably right on some level. Ground up rewrite’s shouldn’t be feared, and there are a lot of times when this can fix something that’s “stuck.” For example, I’m told that Tolkein sat down and wrote the Lord of the Rings, (the whole thing, not just specific books) until he got stuck. And then he started over from the beginning. The entire trilogy, every time he got stuck, until finally Frodo et al got to sail into the sunset. That might be extreme.

The problem is, I think, that we are incredibly inaccurate judges of our own work. This is why we have editors and readers, and that interaction is so valuable. So yeah, if someone says “this doesn’t work,” sure, rewrite rather than try and salvage, if that’s your speed. But as a rule? I’m suspicious of such unequivocal methodological imperatives.

I’ve heard Cory Doctorow say something to the effect of, “some days you write and it feels divinely inspired and the words just flow out, and other days it’s like pulling elephant teeth, but two weeks later, when you’re reading over the back you can’t tell the difference.” This is, I think why editors of all sorts are so valuable. And, since on the day-to-day level it’s probably crap shoot anyway, the key is to try and try often. If you think that first drafts are always to be thrown out, even after editing them as the article suggests you may do, then--time being finite--you write less, but I doubt that you write twice as well. And I am unabashedly of the mind that practicing productivity and developing good habits and experiences is more important than developing perfectionism. Your milage might vary.

And then it struck me--after the outrage passed--that this came from a writer. Someone who is professionally obligated to be invested more in the precession of words on the page than of the ideas that they represent.1 Which is, the core, I guess, of my personal unease with creative writing: I’m way more interested in studying the ideas, the people, the history of what I write about than the words on the page, again this arcs back to what ira said the way to get good at something is to do it, and do it often, and not always “getting it right.” And maybe if an academic program is the way to motivate you to write a lot, then that’s great2 but having a blog might achieve a similar goal.


  1. I’m exactly not making a case for sloppy prose--except maybe I am. My preference is strong characters, plot, and/or conceptual work over pretty, or even sharp language. Always. And I think people who are in the process of figuring out how they write and write best, are much more likely in need of figuring out how to do the conceptual work, not the mechanics, which comes with practice, and is, I’m convinced a numbers game, “the million words of crap,” and all that. If nothing else mandatory rewriting, confuses the conceptual development that I think grows from working with a lot of different ideas/stories; and the technical development that grows from attention, editing (rewriting), and time. ↩︎

  2. it’s also a route to a job that you wouldn’t necessarily be able to get otherwise, but that’s another story that I’m not interested in telling. ↩︎

Camp Report #4 (final)

I’m sorry for not posting when I got home or twittering from the road, but I seem to have survived the ordeal of the drive. I did the drive, which is about 520 miles, in almost exactly eight hours. Which means I averaged did the speed limit ;) In any case, I think that was pretty good. In any case, by the time I got home, I was in no shape to do anything except sleep and knit. So I didn’t get an entry posted yesterday.

I seem to have gotten unstuck in my knitting by the weekend. Latvian Dreaming has progressed into the gussets, and I expect to start the armholes by this weekend. I hope to post instructions for starting the armholes next week, and the neck shaping options somewhat after that. Also, pictures?

I bought some yarn at camp, mostly schoolhouse press' “Quebecois,” enough for two sweaters (in charcoal and navy), and most of the yarn needed for a handdyed and black pullover from Jocelyn’s Fiber Farm. Counting my handspun, I do believe that I have what might be known as a stash, at the moment.

I also must confess to having three sweaters in progress/need of finishing. I have the fingering weight grey sweater that I’ve been working on for years that needs a collar and sleeves (I knit the last saddle/strap at camp), I have the latvian sweater mentioned above, and I have this raglan yoke sweater that I started to knit at camp (but didn’t). And five sweaters worth of yarn stashed. I need to keep knitting.

I also got a lot of (friendly) encouragement to work on knitting designing at camp. While I’m wary of this, I’m not going to start another project until I get (more) settled in the routine of daily blogging and regular fiction production for `Critical Futures <http://criticalfutures.com>`_. I sort of thought that the next thing would be a podcast, but maybe it’ll be working up and publishing a couple of knitting patterns instead. In any case, I’m not going to add any new commitments before, say Labor day.

Other misc. thoughts:

  • I recommended John Scalzi Old Man’s War to someone at camp. I like when geek threads cross.
  • A friend from camp said that he (this narrows down the field of possibility a bit) enjoyed knitting the edging of shawls more than the shawl centers. Given that I feel exactly the opposite, I’m thinking about coming up with some sort of barter agreement. Just the thought of this makes me want to get back into lace knitting, and I have two shawls in progress, and a plan for a third one. We shall see.
  • I will be knitting more. This is a good thing. I have my mojo back.

That’s all that’s on my mind right now. The rest of the week’s posts won’t be as consistent as you’ve grown accustomed to, but there’ll be posts, and when things get settled everything will return to normal.

Camp Report 3

1. Franklin tried on my tychoish henry viii sweater.

  • I need to take such better pictures of my knitting.

2. I did pretty well in the contest, I got some hemp/wool yarn. The shawl I raffled off to support camp scholarships, did pretty well, and it went to Carol Anderson of Cottage Creations who is a great deal of fun. 3. There were great dirty jokes at the end of class. I think someone needs to introduce a skit night. 4. I’ve actually gotten some knitting done, and no longer feel so hopeless about my project and my knitting. So I think, I’m back. 5. I should expound upon this further in the coming weeks, but I’m still thinking about the various merits of knitting work and not knitting work. 6. I bought long inox knitting needles. There will be gansey knitting.

That’s all for now. I have a long drive tomorrow, so there might be something that jott will transcribe for me at the end of the day, but regular posting will resume after that.

Oh, and I have a lot of knitting to do between now and then.

Camp Report #2

I don’t have a lot to report.

I knit a lot, that was really good. The party promises to be great tonight.

I got my 1000 Knitters Project portrait taken today. I’m somewhere in the 900s, and I’m within 20 of people like Meg (and Cully!) Swansen, Medrith Glover, and Emily-freaking-Ocker. How cool is that.

I’m also going to be in the project as tycho garen, rather than my real name. That felt like a big decision, but meh.

I got yarn, including an order that I put in more than a year ago. So much cool stuff to knit, I swear. I’m probably in stock with yarn for the rest of the year. And a fun year it will be indeed.

I thought that I’d be more reflective, and I’m sorry that I didn’t get this out earlier. Anyway, back to the festivities.

Camp Report #1

Knitting camp. Where to start.

This is an analogy that will only make sense to the morris dancers in the audience, but it’s sort of like an ale, with more yarn and less dancing (of course) and much less singing. It’s the lack of singing that I find most disconcerting actually.

This is the session that has history, out of all the sessions of this camp. There are a few people who have been coming for 35 years, and many people who have been coming for way more than 20 years. And that history is something that’s really important to a lot of people, and it’s cool to see that and be a part of it.

I’ve been knitting on the latvian dreaming, mostly and I have two other projects lurking around that I will probably work on today. A lot of people come to camp and start new projects and I think that I’m unlikely to do that, because I need closure on my current projects and, I don’t have fully formed ideas of what I want to do next, anyway.

I’ve tried four times to write a paragraph here and I have too much flying through my head to make sense of that so here goes a list:

  • There are so many famous and amazing knitters here. I’m a little star struck, actually. And a couple of times had lengthy discussions with them before I realized that I was talking to someone who’s name I had recognized in a book. And then, somewhat after the fact I learned that cookie a was “camp newbie sitting across the table from me.” Sigh.
  • On top of all the other interesting discussions last night we had an interesting conversation about social dynamics on the internet and the knitternet.
  • At 9pm last night, I got a pot of hot water and had a caffeine party. It was good stuff. Unlike a Morris Dance Ale, it’s all over by midnight, which means it’s possible to get an at least passable sleep in, but I needed the extra kick to stay up for that. Because:
  • The drive was intense. Not bad, but long and I really pushed pretty hard. I’ll post about the podcasts and other listening materials I went through later…

Anyway I have so much to knit. I’m going to go take a shower and then go down and get started with the day.

Onward and Upward!

(ps. Just a program note/reminder: There’s a new critical futures story today. CF, is my daily (science fiction) story blog. I’ll blog over the weekend here, and cf will return, as usual on Monday.)

Of Email Filtering

Email is a beast. While I would say that I don’t--at the moment--get a huge amount of email, I get enough that if I didn’t have a system in place for dealing with the email, it would be completely useless. I’ve not written about it here, but I have spent some time over the past few weeks working out how to replace a good but faltering system with a much more robust set up. Here’s the story:

(Warning, this is really nerdy)

First off this kind of really robust email solution isn’t for everyone, and there are a couple of unique factors in my setup that require the extra effort of this system. First of all, I need something that works because I hate the phone. If someone wants to get a hold of me, I’d much rather they write an email than call. If I don’t respond to email, people might call, or if I’m feeling overwhelmed by email, I might tell them to call. Both should be avoided. There are also a score of other reasons: I moderate a pretty high volume listserv, I need to send email from several different addresses and names/identities, and I have some pretty specific filtering needs, not to mention the fact that I have a number of pretty old email addresses that require a really powerful spam filter. I’m going to cover both what I used to do, and what I do now.

I *used to*: Collect a number of different email addresses into one gmail account and then check that email with either POP3 or IMAP. Gmail with IMAP was and is a great thing. With it, I could do a lot of in gmail-filtering and then have all of that just show up in my mail program. The problem is that there aren’t really good offline imap clients. Things don’t sync right. Mail.app can’t efficiently cope with new mail that doesn’t arrive in the inbox. You have to screw around with mail.app to get the multiple email identities to work. Mail.app wasn’t incredibly stable (though it has, to be fair gotten more stable.) Also mail.app’s filtering doesn’t work splendidly with IMAP.

Having an email program that works consistently and effectively is the key to keeping it under control.

A lot of my problems with this set up could surely be solved by using POP rather than IMAP, but after a year or so with IMAP (and gmail) I feel like the combination of the back up and having this account be useable and web-accessible is really ideal. I promised a post here on backup, and while I also can’t get into this here, I’m through with having my own machine be the only copy of important emails.

So what to do?

  • Filter the hell out of my gmail account so that everything lands pretty much where it would need to so I can find it several months from now. Somewhere on this page is a list of all the funky boolean operators that gmail allows.

  • Forward email out in chunks (so the lists get forwarded to one place, all of my frequent blog-related correspondents to another, moderation) to different addresses on my web-server that include 15 character random strings).

  • This is actually a really sneaky way of passing gmail’s filtering downstream, and is otherwise a red hearing. I think however, that I could have probably eliminated the number of email addresses at play here by using “plus addresses” and eliminate the next, but it’s not a huge deal.

  • Funnel all these things the forwarded email to a holding email address that automatically deletes everything after a week. This is a short term backup, if I accidentally delete something or whatever.

  • Rather than use gmail’s built in forwarding, I made a filter that searches for another, longer random string in all the email. If it doesn’t find this (which I suspect it never will,) it forwards to my “home” email address. Again this isn’t a public email address.

    Time out, so what we have here. is gmail sorting forwarding two copies of each email to two different addresses, at once. All the email is sent to one address, and the second address depends on how gmail is filtering the email.

  • Set up procmail locally to filter based on the random character string from the second step.

  • Do some additional procmail filtering (which I think, as I figure it out, I’ll start to do more here, with and use geektool

  • Read messages with mutt, because it sucks less than anything else

  • Write messages with textmate

  • Send mail using msmtp

And that’s about it. The getting it setup was the really hard part now all I have to do is use it, and everything lands where it should. I think functionally this is pretty damn good. It might be preferable to get something that isn’t in situations when I don’t have my laptop with me oraccesable. I read something about using something like rsync to handle mail box delivery. Might git work as well? I’m not sure. But that’s another battle for another day.

Onward and Upward!

The Plan

Hey friends!

So I might have mentioned that I’m going to knitting camp at the end of the week. A long drive on Thursday leaving far to early in the morning. Followed by four whole days of intensive knitting, and then a drive back. As a result the blog schedule will be a bit--disrupted. Last year when I was at camp I posted a fair piece, and I suspect that I’ll want to opportunity to recount camp stories a bit as they happen.

At the same time, I probably won’t have the time to do my usual writing cram over the weekend to make sure that there are fun and interesting posts for you during the week. So here’s the deal:

  • There’ll be new stories posted every weekday for the next two weeks. This won’t change, fear not. - I’ll post new things here, through the weekend.
  • I’ll probably take a brief tychoish vacation for a couple of days next week, I think there’ll be three posts, but I’m not sure when they’ll hit yet. It’s a blog, after all. Don’t be worried.

Because I doubt that administrivia is what you all came here to read, I think I’ll pass along some links and thoughts and questions that you might enjoy.

  • The cats are still nibbling toes. This remains not cute, though they haven’t gotten this memo yet.
  • Though I’m only really interested in talking about electoral politics in the historical sense, or as a venue for placing friendly bets,1 but I’m not going to lie this is funny. “This is theinternet!” heh. Actually I’m more worried that someone has cracked Randall’s secret sauce
  • A git-wiki that really rocks. It’s still early on development, and it’s lacking some features that would make it useable for me at the moment, but I can totally see a place for such a thing for some future projects.
  • The ruby guys are totally awesome, and I like a lot of ruby projects, and I think that in some ways ruby is going to be the “next php,” even I have a soft spot in my heart2 for Python, but I said to chris the other day that “ruby is the visual basic of our generation.”
  • I’m thinking of starting to hard wrap columns in my text files, because it would make running diffs and file histories easier, grepping is easier, it makes the text more spatially consistent, it would make using vim easier, and so forth but I seem to really enjoy changing the window size a lot, and he is probably right, there’s very little practical value, and hitting ^Q for a vestige seems ill advised. That doesn’t mean I won’t try it, you read my post about my email after all.
  • I just finished reading “Star Surgeon podiobooks,” a delightfully quirky public domain science fiction novel by Alan E. Norse, and read by my friend Scott Farquhar of Promethesus Radio Theatre, which was delightful even if it wasn’t a fine example of tightly structured prose. Scott’s next book is “Black Star Passes” by John W. Campbell, which I intend to start while I’m driving to camp.

  1. I have, for months been trying to figure out what the bet is for the various party’s VP candidate. It’s a fun game, because its not an ideological discussion, but it’s almost always very historically grounded. It also calls attention to the deeply farcical nature of the entire performance. ↩︎

  2. and brain, as well, actually, because damned if I can really make it do anything--that’s not true, but it feels like it sometimes--but I do love the concept of and rationale for python. ↩︎