Comments on: On Editing: Vision http://www.kimwerker.com/2008/06/15/on-editing-vision/ Think. Create. Write. Fri, 27 Jan 2012 20:36:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: » On Editing: Q & A on Vision http://www.kimwerker.com/2008/06/15/on-editing-vision/comment-page-1/#comment-3277 » On Editing: Q & A on Vision Tue, 24 Jun 2008 00:04:45 +0000 http://www.kimwerker.com/?p=164#comment-3277 [...] trying unsuccessfully to get good work done to answer some questions that came up in response to my first post on editing. Then I’ll feel all articulate and like I got something done, and will therefore certainly [...] [...] trying unsuccessfully to get good work done to answer some questions that came up in response to my first post on editing. Then I’ll feel all articulate and like I got something done, and will therefore certainly [...]

]]> By: Shannon http://www.kimwerker.com/2008/06/15/on-editing-vision/comment-page-1/#comment-3275 Shannon Sun, 22 Jun 2008 21:01:07 +0000 http://www.kimwerker.com/?p=164#comment-3275 Keep it up with this series, Kim! ;) = you know why. As someone whose opinion I very much respect on such things, it's great to hear a little more about your process. After all, there is no such thing as Editor School. (Funny, isn't it? Writing programs are a dime a dozen but editing always seems to be a learn-on-the-job thing). Keep it up with this series, Kim! ;) = you know why. As someone whose opinion I very much respect on such things, it’s great to hear a little more about your process. After all, there is no such thing as Editor School. (Funny, isn’t it? Writing programs are a dime a dozen but editing always seems to be a learn-on-the-job thing).

]]> By: Shannon http://www.kimwerker.com/2008/06/15/on-editing-vision/comment-page-1/#comment-7440 Shannon Sun, 22 Jun 2008 21:01:00 +0000 http://www.kimwerker.com/?p=164#comment-7440 Keep it up with this series, Kim! ;) = you know why. As someone whose opinion I very much respect on such things, it's great to hear a little more about your process. After all, there is no such thing as Editor School. (Funny, isn't it? Writing programs are a dime a dozen but editing always seems to be a learn-on-the-job thing). Keep it up with this series, Kim! ;) = you know why. As someone whose opinion I very much respect on such things, it’s great to hear a little more about your process. After all, there is no such thing as Editor School. (Funny, isn’t it? Writing programs are a dime a dozen but editing always seems to be a learn-on-the-job thing).

]]> By: Doris http://www.kimwerker.com/2008/06/15/on-editing-vision/comment-page-1/#comment-3263 Doris Fri, 20 Jun 2008 00:04:42 +0000 http://www.kimwerker.com/?p=164#comment-3263 This is so cool. We designers often talk about the design submission process amongst ourselves. Do your ears burn periodically, Kim? :-) How enlightening to read about this from a respected editor's POV. I have been on the receiving end of Kim's editorial scruitiny and I know that it pays to be flexible. She is not dictatorial, but neither does she cave in if it's an issue about which she feels strongly. You learn to pick your battles, LOL. Editorial points I've lost: Not being allowed to use common euphemisms for large breasts, like "boobage" or "big girlfriends", in a technical article on shaping crochet (hey, Kim, how many times did you have to beat me upside the head with your admonitions to keep the article dry and authoritative? Ultimately Kim was right); having to use yarn shades not of my choosing (those were also good calls on Kim's part, as my color sense sucks!). Editorial points I've won: I recently submitted a skirt design that Kim liked but asked if the style could be redone as a wrap instead of a pull-on. There was also some concern that the skirt looked too long. Once I explained that the stitch pattern had to be worked in joined rounds and could not be reconfigured to go back and forth, she understood immediately and accepted the original design. And once I showed her the skirt on a real person instead of a dressmakers dummy, Kim found the length to be perfect. As a designer I appreciate all I've learned from working with Kim and Interweave. When it's so clear that everyone wants the same thing -- the most brilliant issue of Interweave Crochet ever -- then it becomes a no-brainer to just check your ego at the door and do what needs to be done. This is so cool. We designers often talk about the design submission process amongst ourselves. Do your ears burn periodically, Kim? :-) How enlightening to read about this from a respected editor’s POV. I have been on the receiving end of Kim’s editorial scruitiny and I know that it pays to be flexible. She is not dictatorial, but neither does she cave in if it’s an issue about which she feels strongly. You learn to pick your battles, LOL.

Editorial points I’ve lost: Not being allowed to use common euphemisms for large breasts, like “boobage” or “big girlfriends”, in a technical article on shaping crochet (hey, Kim, how many times did you have to beat me upside the head with your admonitions to keep the article dry and authoritative? Ultimately Kim was right); having to use yarn shades not of my choosing (those were also good calls on Kim’s part, as my color sense sucks!).

Editorial points I’ve won: I recently submitted a skirt design that Kim liked but asked if the style could be redone as a wrap instead of a pull-on. There was also some concern that the skirt looked too long. Once I explained that the stitch pattern had to be worked in joined rounds and could not be reconfigured to go back and forth, she understood immediately and accepted the original design. And once I showed her the skirt on a real person instead of a dressmakers dummy, Kim found the length to be perfect.

As a designer I appreciate all I’ve learned from working with Kim and Interweave. When it’s so clear that everyone wants the same thing — the most brilliant issue of Interweave Crochet ever — then it becomes a no-brainer to just check your ego at the door and do what needs to be done.

]]> By: Doris http://www.kimwerker.com/2008/06/15/on-editing-vision/comment-page-1/#comment-7442 Doris Fri, 20 Jun 2008 00:04:00 +0000 http://www.kimwerker.com/?p=164#comment-7442 This is so cool. We designers often talk about the design submission process amongst ourselves. Do your ears burn periodically, Kim? :-) How enlightening to read about this from a respected editor's POV. I have been on the receiving end of Kim's editorial scruitiny and I know that it pays to be flexible. She is not dictatorial, but neither does she cave in if it's an issue about which she feels strongly. You learn to pick your battles, LOL. Editorial points I've lost: Not being allowed to use common euphemisms for large breasts, like "boobage" or "big girlfriends", in a technical article on shaping crochet (hey, Kim, how many times did you have to beat me upside the head with your admonitions to keep the article dry and authoritative? Ultimately Kim was right); having to use yarn shades not of my choosing (those were also good calls on Kim's part, as my color sense sucks!). Editorial points I've won: I recently submitted a skirt design that Kim liked but asked if the style could be redone as a wrap instead of a pull-on. There was also some concern that the skirt looked too long. Once I explained that the stitch pattern had to be worked in joined rounds and could not be reconfigured to go back and forth, she understood immediately and accepted the original design. And once I showed her the skirt on a real person instead of a dressmakers dummy, Kim found the length to be perfect. As a designer I appreciate all I've learned from working with Kim and Interweave. When it's so clear that everyone wants the same thing -- the most brilliant issue of Interweave Crochet ever -- then it becomes a no-brainer to just check your ego at the door and do what needs to be done. This is so cool. We designers often talk about the design submission process amongst ourselves. Do your ears burn periodically, Kim? :-) How enlightening to read about this from a respected editor’s POV. I have been on the receiving end of Kim’s editorial scruitiny and I know that it pays to be flexible. She is not dictatorial, but neither does she cave in if it’s an issue about which she feels strongly. You learn to pick your battles, LOL.

Editorial points I’ve lost: Not being allowed to use common euphemisms for large breasts, like “boobage” or “big girlfriends”, in a technical article on shaping crochet (hey, Kim, how many times did you have to beat me upside the head with your admonitions to keep the article dry and authoritative? Ultimately Kim was right); having to use yarn shades not of my choosing (those were also good calls on Kim’s part, as my color sense sucks!).

Editorial points I’ve won: I recently submitted a skirt design that Kim liked but asked if the style could be redone as a wrap instead of a pull-on. There was also some concern that the skirt looked too long. Once I explained that the stitch pattern had to be worked in joined rounds and could not be reconfigured to go back and forth, she understood immediately and accepted the original design. And once I showed her the skirt on a real person instead of a dressmakers dummy, Kim found the length to be perfect.

As a designer I appreciate all I’ve learned from working with Kim and Interweave. When it’s so clear that everyone wants the same thing — the most brilliant issue of Interweave Crochet ever — then it becomes a no-brainer to just check your ego at the door and do what needs to be done.

]]> By: Donna http://www.kimwerker.com/2008/06/15/on-editing-vision/comment-page-1/#comment-3262 Donna Thu, 19 Jun 2008 19:41:17 +0000 http://www.kimwerker.com/?p=164#comment-3262 I'm glad you wrote about this and I look forward to reading more. Also, my curiosity was piqued when you mentioned Scalzi's book and I saw how hard they are to come by. I managed to snag a copy online for the list price (not easy to do!) on Sunday after reading your post. I’m glad you wrote about this and I look forward to reading more. Also, my curiosity was piqued when you mentioned Scalzi’s book and I saw how hard they are to come by. I managed to snag a copy online for the list price (not easy to do!) on Sunday after reading your post.

]]> By: yarntomato http://www.kimwerker.com/2008/06/15/on-editing-vision/comment-page-1/#comment-7444 yarntomato Thu, 19 Jun 2008 19:41:00 +0000 http://www.kimwerker.com/?p=164#comment-7444 I'm glad you wrote about this and I look forward to reading more. Also, my curiosity was piqued when you mentioned Scalzi's book and I saw how hard they are to come by. I managed to snag a copy online for the list price (not easy to do!) on Sunday after reading your post. I’m glad you wrote about this and I look forward to reading more. Also, my curiosity was piqued when you mentioned Scalzi’s book and I saw how hard they are to come by. I managed to snag a copy online for the list price (not easy to do!) on Sunday after reading your post.

]]> By: Kim http://www.kimwerker.com/2008/06/15/on-editing-vision/comment-page-1/#comment-3253 Kim Mon, 16 Jun 2008 20:27:23 +0000 http://www.kimwerker.com/?p=164#comment-3253 @<a href="#comment-3252" rel="nofollow">penny</a>: I don't really worry about that line at all. There are two circumstances under which I'll ask a designer about changing something: 1) If I think an aspect of the design isn't working; 2) If I'd like to explore the possibility of changing an aspect of a design (either to fit a theme, or because the submission sparked an idea I'd like to explore, etc.). Note that it's not uncommon for either of these circumstances to arise. Also note that I always <strong>ask</strong>. Sometimes my ideas are bad, and I appreciate it when a designer tells me so. @penny: I don’t really worry about that line at all. There are two circumstances under which I’ll ask a designer about changing something: 1) If I think an aspect of the design isn’t working; 2) If I’d like to explore the possibility of changing an aspect of a design (either to fit a theme, or because the submission sparked an idea I’d like to explore, etc.). Note that it’s not uncommon for either of these circumstances to arise. Also note that I always ask. Sometimes my ideas are bad, and I appreciate it when a designer tells me so.

]]> By: Kim Werker http://www.kimwerker.com/2008/06/15/on-editing-vision/comment-page-1/#comment-7443 Kim Werker Mon, 16 Jun 2008 20:27:00 +0000 http://www.kimwerker.com/?p=164#comment-7443 @<a href="#comment-3252" rel="nofollow">penny</a>: I don't really worry about that line at all. There are two circumstances under which I'll ask a designer about changing something: 1) If I think an aspect of the design isn't working; 2) If I'd like to explore the possibility of changing an aspect of a design (either to fit a theme, or because the submission sparked an idea I'd like to explore, etc.). Note that it's not uncommon for either of these circumstances to arise. Also note that I always <strong>ask</strong>. Sometimes my ideas are bad, and I appreciate it when a designer tells me so. @penny: I don’t really worry about that line at all. There are two circumstances under which I’ll ask a designer about changing something: 1) If I think an aspect of the design isn’t working; 2) If I’d like to explore the possibility of changing an aspect of a design (either to fit a theme, or because the submission sparked an idea I’d like to explore, etc.). Note that it’s not uncommon for either of these circumstances to arise. Also note that I always ask. Sometimes my ideas are bad, and I appreciate it when a designer tells me so.

]]> By: penny http://www.kimwerker.com/2008/06/15/on-editing-vision/comment-page-1/#comment-3252 penny Mon, 16 Jun 2008 19:53:15 +0000 http://www.kimwerker.com/?p=164#comment-3252 @kim: yes... like a different button hole or hmm.. i don't crochet often from patterns so it's hard to think up examples and i'm not creative enough to design so it's a different world to me. i guess how do you try not to cross the between line between designer feature and bug. er. uhm.. does that clarify at all? @kim: yes… like a different button hole or hmm.. i don’t crochet often from patterns so it’s hard to think up examples and i’m not creative enough to design so it’s a different world to me. i guess how do you try not to cross the between line between designer feature and bug. er. uhm.. does that clarify at all?

]]>