<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Inkpunks &#187; Adam Israel</title>
	<atom:link href="http://www.inkpunks.com/author/adam/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.inkpunks.com</link>
	<description>We who sling ink</description>
	<lastBuildDate>Wed, 16 May 2012 17:07:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Flash Fiction Friday: Pacing</title>
		<link>http://www.inkpunks.com/2012/04/27/flash-fiction-friday-pacing/</link>
		<comments>http://www.inkpunks.com/2012/04/27/flash-fiction-friday-pacing/#comments</comments>
		<pubDate>Fri, 27 Apr 2012 19:03:32 +0000</pubDate>
		<dc:creator>Adam Israel</dc:creator>
				<category><![CDATA[Basics]]></category>
		<category><![CDATA[Writing]]></category>
		<category><![CDATA[flash fiction]]></category>

		<guid isPermaLink="false">http://www.inkpunks.com/?p=722</guid>
		<description><![CDATA[The best insight comes when you least expect it. I was in Toronto a couple weekends ago, at Ad Astra. I sat in a room on Sunday afternoon with twenty other writers, staring at a piece of flash fiction I wrote for their annual writing contest. I hadn’t won, and while I waited to talk [...]]]></description>
			<content:encoded><![CDATA[<p>The best insight comes when you least expect it. I was in Toronto a couple weekends ago, at <a href="http://www.ad-astra.org/">Ad Astra</a>. I sat in a room on Sunday afternoon with twenty other writers, staring at a piece of flash fiction I wrote for their annual writing contest. I hadn’t won, and while I waited to talk to the judges to get my critiques, I was re-reading my story to figure out what didn’t work. I used all the prompts, it was well-written, but something wasn’t quite right. It hit me a minute before my first critique: I blew the pacing.</p>
<p>Pacing is like cooking, in a way. The preparation and presentation of food affect the experience of the diner just like text informs the reader. Pace is the heart of performance.</p>
<p>If you’re preparing an <em>amuse-bouche</em> to serve your guests, you want to create a flavor that will unravel on the palate, tell a story, and leave them satisfied. A big idea within a small body of work. Flash fiction in a nutshell. One self-contained bite.</p>
<p>Scene breaks signal the end of service, a place for the reader to pause while we refill their wine and set the table for the next course. I was using them like I might in short fiction but instead the reader was forced to stop and spit out a bone from their <em>salmon tartare</em>.</p>
<p>In hindsight, it doesn’t surprise me that the judge who pointed out the pacing problem also works in theatre. I don’t usually think of writing as a performance art. We don’t write in front of a live audience, but the end result is still being performed in front of one.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inkpunks.com/2012/04/27/flash-fiction-friday-pacing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rules of writing: the auto-tune of literature</title>
		<link>http://www.inkpunks.com/2012/03/26/rules-of-writing-the-auto-tune-of-literature/</link>
		<comments>http://www.inkpunks.com/2012/03/26/rules-of-writing-the-auto-tune-of-literature/#comments</comments>
		<pubDate>Tue, 27 Mar 2012 01:15:40 +0000</pubDate>
		<dc:creator>Adam Israel</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://www.inkpunks.com/?p=693</guid>
		<description><![CDATA[No one can tell me how to be me. The same goes for being a writer. Yet, I can’t help myself. The internet is full of mostly well-intentioned advice on writing — forums, essays, lists, and opinionated rant — and I soak it up. Chuck Wendig’s blog, one of my current favorites, is full of fun [...]]]></description>
			<content:encoded><![CDATA[<p>No one can tell me how to be me. The same goes for being a writer. Yet, I can’t help myself. The internet is full of mostly well-intentioned advice on writing — forums, essays, lists, and opinionated rant — and I soak it up. <a href="http://terribleminds.com/ramble/blog/">Chuck Wendig’s blog</a>, one of my current favorites, is full of fun little lists of advice aimed at writers. It’s all too easy to choke on the stream when you’re drinking from a fire hose, though. I could spend my entire day reading other people’s take on rules and processes and neglect my own projects, if I didn&#8217;t put some filters in place.</p>
<p>Rules themselves aren’t necessarily bad. Some people are contrarians and make a point to avoid them but the truth is, rules are rules for a reason. These are things that have been done so poorly over time that someone arrived at a simple conclusion to fix a widespread problem and the publishing community said, “Yes, that.” As generalities go, they can be useful for filtering out a lot of noise.</p>
<p>I can’t tell you how many times I’ve heard someone say that “You have to know the rules before you can break them.” What’s that mean, exactly? Well, it’s part of the internalization process but that’s still vague.</p>
<p>I think about that in terms of the old lawn mower engine I used to tinker with when I was a teen. At first, I knew nothing about it other than where to put the gas. When it wouldn’t start, my dad explained the carburetor, about ignition, combustion, and airflow. He handed me a screwdriver and showed me how to wedge open the choke and get the engine started. I understood a rule; I could tell you why restricted airflow would prevent the lawn mower from starting and I could follow the rule and make it run it but I was far from being able to build my own engine.</p>
<p>Rules try to quantify problematic story traits into simplistic, cautionary terms. What they don’t always do is give us the context behind them. That’s left up to us to figure out. I know I’ve internalized something when I can tell it to someone else without stumbling over the explanation. I put together a shiny little flowchart that kind of breaks down my process:</p>
<p style="text-align: center;"><a href="http://www.inkpunks.com/wp-content/uploads/2012/03/Rules.jpg" rel="lightbox[693]" title="Processing the rules"><img class="size-full wp-image-694 aligncenter" title="Processing the rules" src="http://www.inkpunks.com/wp-content/uploads/2012/03/Rules.jpg" alt="" width="389" height="488" /></a></p>
<p>I try to take each piece of advice as if I’m chewing on a piece of salt the size of a jawbreaker, even if it comes from my childhood hero or my best friends. No one is trying to mislead me, but everyone approaches these problems from their own experiences. Rules that work for everyone, like absolute, are suspect at best.</p>
<p>The most famous (and infuriatingly vague) rule might be “Show, don’t tell.” What that really means, to me, is choosing which details you reveal to the reader, and how, carefully. I don’t need to spend a paragraph emphasizing the ticking of a clock, for example, if it doesn’t have any relevance to the story other than, perhaps, to set mood. It’s a balancing of importance.</p>
<p>“Write what you know” is another one that has always bothered me. I’ve never been an airship pirate, nor have I been a 1920’s superhero but that hasn’t stopped me from writing about them. So what does that really mean? What I do know — life experience. I’ve known anguish and heartbreak. I’ve seen people self-destruct through inaction and apathy, or rise to new heights through personal revelation. What I know is the life I’ve lived and ultimately story comes down to the people who populate it.</p>
<p>Every writer has leeway to interpret the rules their own way. How we write defines our voice. That variety is what makes literature exciting and worth reading. Can you imagine the horrible boringness if every writers voice were the same — if someone like <a href="http://www.catherynnemvalente.com/">Catherynne Valente</a> (whose written voice is <em>amazing</em>) were indistinguishable from any other writer? That would be a fucking criminal and should emphasis the importance of making these bits of wisdom your own.</p>
<p>Finding your voice <em>is </em>your internalization of the so-called rules. And when you’re done, <em>motherfucking</em> own those rules and write.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inkpunks.com/2012/03/26/rules-of-writing-the-auto-tune-of-literature/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Interview: Jay Lake</title>
		<link>http://www.inkpunks.com/2012/03/21/interview-jay-lake/</link>
		<comments>http://www.inkpunks.com/2012/03/21/interview-jay-lake/#comments</comments>
		<pubDate>Wed, 21 Mar 2012 15:10:34 +0000</pubDate>
		<dc:creator>Adam Israel</dc:creator>
				<category><![CDATA[Interview]]></category>

		<guid isPermaLink="false">http://www.inkpunks.com/?p=688</guid>
		<description><![CDATA[An October 2009 LiveJournal post about acceptances and rejections by Jay Lake led to an email exchange about his submission statistics. He graciously sent me a copy of his spreadsheet and I was going to compile some pretty, pretty graphs based on the data. I began a drastic life change (divorce) a week later and [...]]]></description>
			<content:encoded><![CDATA[<p>An October 2009 LiveJournal post about <a href="http://jaylake.livejournal.com/1939451.html">acceptances and rejections</a> by Jay Lake led to an email exchange about his submission statistics. He graciously sent me a copy of his spreadsheet and I was going to compile some pretty, pretty graphs based on the data. I began a drastic life change (divorce) a week later and that project never came to fruition.</p>
<p>Skip forward a few years. I’d been following a discussions on story revision, submission management and tracking on Codex and elsewhere. I’d gone through several iterations of my own submission spreadsheet, trying to find a process that worked for me. Then I remembered that past conversation with Jay. I still had that snapshot into his early short fiction career, circa 2000-2009, so I reconnected with him to see if he would be interested in discussing his early career in more detail.</p>
<hr />
<p><strong>I think most people have some goal for publication — pay rate, prestige, SFWA qualification, etc. What was your strategy for choosing where to send a story and how has that changed over the years?</strong></p>
<blockquote><p>When I first started publishing I was keenly interested in SFWA qualification, yet at the same time (ca. 2001/2002) the independent press was exploding. Print on Demand books had become financially and logistically practical, while Web based markets were first being taken seriously. So, frankly, I went for exposure in casting my net widely. I was submitting to top pay and prestige markets from the very beginning, but I was also producing sufficient inventory to keep stories out at various independent and one-time markets.</p>
<p>In the years since, I&#8217;ve shifted my primary writing focus to novels. At the same time, my cancer experiences of the past four years have robbed me of a considerable amount of writing time. Taking these two trends combined has significantly reduced the attention I&#8217;ve been able to pay to short fiction. My strategy these days is to respond to requests from markets I&#8217;m interested in supporting, while still also aiming for those top pay and prestige markets. Reduced inventory had caused me to pull in net, so to speak, but I&#8217;m still an enthusiastic supporter of independent presses.</p>
<p>Fundamentally, I&#8217;d like to be read. Whatever path it might be that gets me there.</p></blockquote>
<p><strong>Your submission history speaks to persistence. In one case, a story had been rejected twenty-two times before selling to Weird Tales. At what point do you give up trying to sell a story?</strong></p>
<blockquote><p>Usually I trunk a story when it has hit all the markets I think it was likely to be of interest to. Obviously this is a very subjective judgment on part. And I do have a pretty big trunk, so to speak. Every once in a great while I&#8217;ll pull out a retired story, rework it, and put it back on the market. So even those trunk stories aren&#8217;t necessarily in permanent retirement.</p></blockquote>
<p><strong>It doesn’t look like you often edit to a story once it’s gone into submission. What will prompt you to make revisions before sending something to the next market?</strong></p>
<blockquote><p>I usually try to read through a story before it goes out, just for a typo patrol. Every now and then I&#8217;m moved to pull a finished story and edit more heavily. In general, though, I&#8217;d almost always rather write a new one. Since writing isn&#8217;t a difficult exercise for me (other than the time issues mentioned above), this seems to work out fairly well.</p></blockquote>
<p><strong>As your career and writing progressed — pro sales, invitations to closed markets, award nominations and wins, etc. — do you have any qualms about submitting older stories that are not representative of your current work?</strong></p>
<blockquote><p>Not really. If I pull an old story out of the trunk and rework it, well, then hopefully I&#8217;m functioning within my present knowledge and mastery of the craft. I&#8217;ve always had pretty good ideas and a neat turn of phrase. The problems in those older stories are more along the lines of characterization, ending and so forth. That&#8217;s stuff I can fix if I want to take the time to do so. My voice is always evolving &#8212; if it ever stops doing so, that will be because something has gone wrong &#8212; but I&#8217;m proud of my earlier work as well.</p></blockquote>
<hr />
<p>Jay Lake lives in Portland, Oregon, where he works on numerous writing and editing projects. His 2012 books are <em>Kalimpura</em> from Tor Books, and <em>Love in the Time of Metal and Flesh</em> from Prime Books. His short fiction appears regularly in literary and genre markets worldwide. Jay is a past winner of the John W. Campbell Award for Best New Writer, and a multiple nominee for the Hugo and World Fantasy Awards. Jay can be reached through his blog at <a href="http://jlake.com/">jlake.com</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inkpunks.com/2012/03/21/interview-jay-lake/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Persistence of Recordkeeping</title>
		<link>http://www.inkpunks.com/2012/02/24/the-persistence-of-recordkeeping/</link>
		<comments>http://www.inkpunks.com/2012/02/24/the-persistence-of-recordkeeping/#comments</comments>
		<pubDate>Fri, 24 Feb 2012 16:20:07 +0000</pubDate>
		<dc:creator>Adam Israel</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://www.inkpunks.com/?p=650</guid>
		<description><![CDATA[I screwed up earlier this week. I submitted a story to a pro market, and verified its status the next morning. Imagine my dismay when I saw, in the list of previously rejected stories, the same one I’d just sent them. I did what needed to be done, promptly sending a withdrawal and apology to [...]]]></description>
			<content:encoded><![CDATA[<p>I screwed up earlier this week. I submitted a story to a pro market, and verified its status the next morning. Imagine my dismay when I saw, in the list of previously rejected stories, the same one I’d just sent them.</p>
<p>I did what needed to be done, promptly sending a withdrawal and apology to the editor. My next step was figuring out how I made the mistake in the first place, which led to writing this post.</p>
<p>I’m a pretty avid supporter and user of Duotrope. It’s the first place I go to look for markets and where I primarily track my submissions but, as it turns out, with some omissions. On top of that, I was using a mix of spreadsheets but those were entirely current, either.</p>
<p>Numbers (or Excel) worked well as an offline solution, but was getting cluttered. I decided to switch to Google Docs and create multiple spreadsheets — one per story — to track submissions. It was an interesting experiment, but only added to the confusion (not to mention a duplication of effort).</p>
<p>Disheartened, I started re-examining the problem. The spreadsheet(s) I had only tracked the most basic information: title, market, dates submitted and responded, status and comments. That’s not enough, though. I also keep a list of stories written and their status and was duplicating information between the two lists. There’s also tracking what rights were sold for acceptances, which I wasn’t tracking. Ugh.</p>
<p>With only a half dozen stories sold, reprints aren’t something I’m worrying about yet but I’ll need to be. I also need to know which rights I’ve sold — print vs. Electronic vs. Audio. A story sold once is a story that can be sold twice.</p>
<p>Databases, which I’m all too familiar with, seem like overkill. Any solution needs to be simple or I’m just going to get frustrated building it or using it. I know some people are happy using a simple document ala Word or a notebook (one page per story) but that lacks the ability to quickly search for specific information. Back to a spreadsheet I went.</p>
<p>Using one document to track them all, containing three spreadsheets:</p>
<ul>
<li>Index</li>
<li>History</li>
<li>Rights</li>
</ul>
<p>The index is just that, a list of relevant details (title, log line, genre, themes, status, and notes) of each story I’ve written. I’ve color coded the status so I can quickly see if it’s in need of revision, rewriting, ready for submission, etc.</p>
<p>History is where I’m tracking the lifecycle of a story, from draft to submission. In one glance, I can see where a story has been and where it’s at. If I decide to trunk a story, or bring on a collaborator, I know exactly when that took place.</p>
<p>Another benefit I’m finding is that an occasional comment from an editor might have been filed away and forgotten, with months between rejections. Seeing them together on one page with other responses, patterns start to emerge that might have seen me make revisions to one or two stories before sending them back out.</p>
<p>In Rights, I’m recording the title, market, and which rights I’ve sold, along with the effective dates, how much I’ve been paid, when I was paid, and when rights revert back. If, at some point in the future, an editor asks me if I have any reprints to sell them, it’s a simple matter of filtering by date. Also, when it comes time to do taxes and I’m wondering how much money I’ve made from writing, I have that recorded, too.</p>
<p>A sample spreadsheet, with totally fake data (although I kind of want to write  <em>The Bromantics</em>, now) is available <a href="https://docs.google.com/spreadsheet/ccc?key=0Agx3xVyVfvr1dDNKaEcxUmVpMXVCTnZMMEFGWXBBRWc">here</a>.</p>
<p>There is no perfect solution to this problem, I think, because it’s different for every person. Reading <a href="http://www.inkpunks.com/2012/02/15/guest-post-managing-your-schedule-as-a-busy-freelancer/">Jennifer Brozek’s guest post about managing her freelance schedule</a>, for example, gave me the idea to use color coding. It’s an adaptation of process, find what works and abandoning what doesn’t.</p>
<p>The more you write, the longer your inventory becomes and managing that isn’t going to become easier. I wish I’d done a better job of record keeping at the start, not just so I wasn’t spending hours trying to fix the mess I have now but so I had more accurate notes, like when I finished drafts or made revisions.</p>
<p>I’m curious what you’re using to track their submissions (non-fiction, short fiction, or novels), and how happy you are with that process. I’d love to hear your thoughts in the comments.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inkpunks.com/2012/02/24/the-persistence-of-recordkeeping/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>The Clarion Writers’ Workshop</title>
		<link>http://www.inkpunks.com/2012/01/23/the-clarion-writers-workshop/</link>
		<comments>http://www.inkpunks.com/2012/01/23/the-clarion-writers-workshop/#comments</comments>
		<pubDate>Mon, 23 Jan 2012 22:09:04 +0000</pubDate>
		<dc:creator>Adam Israel</dc:creator>
				<category><![CDATA[Workshops]]></category>

		<guid isPermaLink="false">http://www.inkpunks.com/?p=614</guid>
		<description><![CDATA[As best I can remember, my journey to Clarion began in 1989, with a classified ad in the the back of Asimov’s magazine. Fast forward through fifteen years or so of life and career. I’d retired from writing a tech column online to take some creative writing classes at my local community college and was [...]]]></description>
			<content:encoded><![CDATA[<p>As best I can remember, my journey to <a href="http://literature.ucsd.edu/affiliated-programs/clarion/index.html">Clarion</a> began in 1989, with a classified ad in the the back of Asimov’s magazine. Fast forward through fifteen years or so of life and career. I’d retired from writing a tech column online to take some creative writing classes at my local community college and was starting to pursue my dream of writing fiction.</p>
<p>The regulars on a tech forum I frequented ran a secret santa gift exchange. Maggie, the then-wife of the person who received my name, was also interested in writing, and sent me &#8220;<a href="http://smallbeerpress.com/books/2005/08/08/storyteller-writing-lessons-and-more-from-27-years-of-the-clarion-writers-workshop/">Storyteller: Writing Lessons and More from 27 Years of the Clarion Writers&#8217; Workshop</a>&#8221; by Kate Wilhelm. My interest in the workshop was rekindled; I applied in 2007 and again in 2010, when I was accepted.</p>
<p>Clarion is not without controversy. Ask a room full of writers if you should go to six-week workshop and you’re bound to get mixed opinions: go, don’t go, it’s the best experience in the world, it will ruin your life and you’ll never be able to write again. Sorting out who’s wrong and who’s right is complicated, especially when they’re all right.</p>
<p>I’m a bad traditional student. I don’t do well being lectured to and being assigned tedious homework. I floundered in high school and dropped out of college during my first semester. I taught myself most of what I know about software engineering. I read dozens of books about writing and, more importantly, written hundreds of thousands of words in practice. I studied the history and format of the workshop, and read both sides of the debate of its value. If I was going to apply, it was going to be a well-informed action.</p>
<p>There’s no question that going to Clarion is hard. Six weeks away from home cascades into questions of finance, career, and family.</p>
<p>I’d been in the process of preparing my paperwork for immigration to Canada when I was accepted to Clarion. Shortly after that, I was kicked out of Canada after a work trip to Detroit and separated from my wife. The six weeks at Clarion overlapped with that, which was a blessing and a curse. It was time I would probably still have been barred from home but I felt doubly guilty for the separation.</p>
<p>The workshop fee stopped me from applying more than once, but it’s a problem to be solved after you&#8217;re accepted (<a href="http://www.inkpunks.com/2011/09/16/dont-self-reject/">no rejecting yourself</a>). I didn’t have that kind of savings, especially while paying alimony and being underwater on a house I couldn’t sell. I received some scholarship money and I am eternally grateful to the donors who sponsor them. I lucked out with my taxes that year. Because of the alimony I’d been paying post-taxes, I received a larger than expected tax return.</p>
<p>Time away from work was the issue I was most scared of. I’m a bit of a workaholic. I’d skipped vacations for three years prior to my acceptance but my job at the time balked at giving the time to me, despite several months notice. I’d counted on the paid time off but ended up with a partial sabbatical and advance to cover the extra time off. I didn’t get final approval until the day before I left for the workshop. Because of the alimony obligation, I would have had to back out of Clarion and forfeit my workshop fee without that approval.</p>
<p>For all of that stress, the anxiety of separation and uncertainty over money and job, it was worth it for me. Clarion is an intense experience. It’s not just the hard work or spending six weeks with people who you’ve just met. You’re pushing yourself each and every day, being inspired by your classmates, making new friends, and discovering new things about yourself.</p>
<p>Clarion isn’t for everyone. You get from it what you give to it. You’ll work hard and you’ll play hard (I might hold the record for the only student to get a concussion). I think of it as tearing you apart to find your weaknesses and putting you back together again. You’re still you, but the way you look at the world has changed.</p>
<p>Did Clarion worked for me? Yes, because I made it work for me. I would have had the same successes without attending, but it would have taken me longer. A lot longer, maybe. Clarion was the leap of faith I need to take in myself and for that it was worth everything.</p>
<p>Clarion isn’t just a workshop; it’s a community within a community. Seventeen classmates, friends who shared the journey applying. And <a href="http://albionidaho.livejournal.com/">Maggie</a>, who so thoughtfully sent me the book that restarted my journey towards Clarion? She herself attended <a href="http://www.clarionwest.org/">Clarion West</a> in 2008. Thank you.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inkpunks.com/2012/01/23/the-clarion-writers-workshop/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Dropbox: A Primer for Writers</title>
		<link>http://www.inkpunks.com/2011/11/18/dropbox-a-primer-for-writers/</link>
		<comments>http://www.inkpunks.com/2011/11/18/dropbox-a-primer-for-writers/#comments</comments>
		<pubDate>Fri, 18 Nov 2011 16:36:34 +0000</pubDate>
		<dc:creator>Adam Israel</dc:creator>
				<category><![CDATA[Not-Writing]]></category>
		<category><![CDATA[dropbox]]></category>

		<guid isPermaLink="false">http://www.inkpunks.com/?p=530</guid>
		<description><![CDATA[Whether it’s because it’s November and NaNoWriMo or happenstance, I’ve heard a few tales of woe lately from writers whose hard drive crashed or, in one person’s case, had their laptop stolen. In each case, the writer did not have recent backups and lost what they were working on. My inner geek cringes to hear [...]]]></description>
			<content:encoded><![CDATA[<p>Whether it’s because it’s November and NaNoWriMo or happenstance, I’ve heard a few tales of woe lately from writers whose hard drive crashed or, in one person’s case, had their laptop stolen. In each case, the writer did not have recent backups and lost what they were working on. My inner geek cringes to hear things like this. Backing up should be pain-free, easy, and washing mashing safe. I thought I’d talk a little bit about my process.</p>
<p>Acts of theft aside, the loss of work is so nearly avoidable in this age. I was an early adopter of online file storage, dating back to the early 2000’s and a brief stint writing that kind of software for a company that no longer exists. I still lament the loss of one particular story, lost to the fickle platters of an angry electronic god and I don’t want to go through that again. That’s where Dropbox came into my life.</p>
<p>What is Dropbox? It’s not the most clear from their webpage without watching their video. Dropbox is, in a nutshell, a system for backing up and synchronizing files between your devices (PC, Mac, Linux, or Mobile) and the Cloud. The Cloud, in this instance, being Amazon’s S3 file storage service.</p>
<p><strong>How it works</strong></p>
<p>Every computer you install the desktop software in will place a “Dropbox” folder in your home directory. Inside that directory, I’ve organized all of the documents and files I want to keep backed up and synchronized. It looks a little bit like this:</p>
<ul>
<li>Clients</li>
<ul>
<li>Contracts</li>
<li>Proposals</li>
</ul>
<li>Documents</li>
<ul>
<li>Taxes</li>
<li>Receipts</li>
</ul>
<li>Public</li>
<li>Writing</li>
<ul>
<li>Contracts</li>
<li>Copyedited</li>
<li>Cover Letters</li>
<li>Critiques</li>
<li>Essays</li>
<li>Fiction &#8211; Short</li>
<li>Fiction &#8211; Long</li>
<li>For Critique</li>
<li>For Submission</li>
</ul>
</ul>
<p>That probably looks somewhat familiar. It should. The point is, the Dropbox folder shouldn’t look any different what you already have, except for its name. It took me a while to come up with a file structure that suited me and to remember to save things to it but that’s all. As long as you’re connected to the internet, you’re done. Dropbox will backup any new file you move or create under its folder, and synchronize any changes that you make.</p>
<p><strong>Privacy and Security</strong></p>
<p>As with any service that transfers and stores your data online, there are privacy and security concerns to consider. Dropbox got themselves into a middle of a fuss some months back thanks to some unclear changes to their <a href="http://www.dropbox.com/privacy">Privacy Policy</a>, which have since been revised for clarification.</p>
<p>The short, non-technical version is that they use same kind of security that your web browser uses to keep your secure when you’re checking bank balances or shopping online. Once in the Cloud, your files are not encrypted unless you encrypted them first, but they are three ways your files can be accessed by others. Two are if you’ve chosen to share them, either by putting the file in your Public folder *and* linked them to it or specifically invited them to share files. The third is by an employee of Dropbox, when they are legally required to do so.</p>
<p>There’s a privacy debate about whether or not Dropbox should encrypt by default and, indeed, there are competitors such as <a href="https://spideroak.com/">SpiderOak</a> that do, but their client software was not nearly as well-integrated the last I checked and, for that reason, not suitable for my needs. It comes down to a personal choice; I’m choosing convenience in this case.</p>
<p>There was a debacle in June 2011, where a programming change introduced <a href="http://www.wired.com/threatlevel/2011/06/dropbox/">a bug that left accounts accessible by any password</a> for four hours. An embarrassing mistake, unlikely to happen, and not enough by itself to find an alternative.</p>
<p><strong>Disaster Recover</strong></p>
<p>I primarily work from a Macbook Pro, but I have an older Mac Mini in my office that I primarily use for music. I installed Dropbox on that and linked it to my account. If I’m on the road and make changes, they are automatically synchronized at home. Dropbox already provides a way to restore files, through the desktop application and their website but this gives me an extra layer of redundancy.</p>
<p>Whether you use Scrivener like I do, Word, Open Office, yWriter, or whatever, things occasionally get bolloxed up. You can train yourself to hit save early and often or setup auto-save but no matter how many times do, sometimes the last save is the only one it takes to corrupt a document and make it unreadable.</p>
<p>Dropbox to the rescue. Every time you save, it records the changes. Viewing the previous versions will show you the history of that file and let you download the previous copy until you find one that worked.</p>
<p><strong>Other uses for Dropbox</strong></p>
<p>I haven’t used Dropbox to share files between users much, but I’d love to hear comments from anyone who has, and how its worked. I have used it with the iPhone and iPad client, in conjunction with the Plaintext application, to make quick changes or even revise (with an external keyboard).</p>
<p><strong>Getting Dropbox</strong></p>
<p>Dropbox has a free tier with 2GB of storage, which should be more than sufficient if you&#8217;re using it to store documents or small files, with increases in 250MB increments if you refer people to signup with them. A paid plan of course, is available, if you need more. I&#8217;ve been using the free tier for more than three years without having to consider upgrading. Download, install, and forget about it.</p>
<p>Get <a href="http://db.tt/b438YiSD">Dropbox</a> (using my referral link, so we both get 250MB bonus storage)<br />
Get <a href="http://www.dropbox.com/">Dropbox</a> (no referral link, but no bonus storage)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inkpunks.com/2011/11/18/dropbox-a-primer-for-writers/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Shifting Sand: The Art of Tending Goals</title>
		<link>http://www.inkpunks.com/2011/10/14/shifting-sand-the-art-of-tending-goals/</link>
		<comments>http://www.inkpunks.com/2011/10/14/shifting-sand-the-art-of-tending-goals/#comments</comments>
		<pubDate>Fri, 14 Oct 2011 14:53:56 +0000</pubDate>
		<dc:creator>Adam Israel</dc:creator>
				<category><![CDATA[Process]]></category>

		<guid isPermaLink="false">http://www.inkpunks.com/?p=488</guid>
		<description><![CDATA[Around the time I was fifteen, I wrote to Marion Zimmer Bradley for the guidelines to her magazine and I collected every copy of Asimov&#8217;s Magazine I could get my hands on. I didn&#8217;t really know what it meant to be a writer but I knew I wanted to be one and I had it [...]]]></description>
			<content:encoded><![CDATA[<p>Around the time I was fifteen, I wrote to Marion Zimmer Bradley for the guidelines to her magazine and I collected every copy of Asimov&#8217;s Magazine I could get my hands on. I didn&#8217;t really know what it meant to be a writer but I knew I wanted to be one and I had it in my head that it meant submitting and joining SFWA.</p>
<p>Writing, and more specifically, writing for publication, means cultivating a discipline that borders on obsession. Setting goals, reaching goals, and yes, failing, is part of that process. Think of it like minding a garden &#8212; too much attention and you&#8217;ll kill your crop but so will neglect. This harvest, though, isn&#8217;t something you can read about in the Farmers Almanac. You&#8217;re tending you &#8212; your motivations and productivity, compensating for whatever life is throwing in front of you at that given moment, in order to blossom.</p>
<p>The setting of goals is individual. Its what you hope to achieve, but should be something that you have direct control over, i.e., revising a story for submission versus a story being accepted for publication.</p>
<p>A lot of the advice you&#8217;ve heard repeated <em>ad nauseam</em> is sound: read, write, revise, submit. These should pretty much be mantra.</p>
<p>There&#8217;s also the voluntary bits, such as: slushing, proofreading, attending workshops and conventions, social networking, etc. These can improve your abilities as a writer, give you new insights into publishing, open up new career paths, such as editing or proofreading or publishing, and introduce you to many wonderful people.</p>
<p>These extracurricular activities come at a cost, both in terms of money and time. You should evaluate each according to how it applies to your goals. Voluntary work is an additive, like fertilizer. It should enhance your work or life in some way, not choke the life out of it.</p>
<p>Semi-related side note: I was listening to the podcast <a href="http://www.writingexcuses.com/2011/09/25/writing-excuses-6-17-writing-assistants/">Writing Excuses 6.17: Writing Assistants</a> last week and they mentioned Kevin J. Anderson, who probably needs no introduction. On his desk, he has a piece of paper with the word “no” written in large letters where he can see it whenever he looks up as a reminder not to take on too many projects. I think that’s a good reminder for all of us. The demands on our time get worse, not better, with success.</p>
<p>Set a goal and try. Accept that failure will happen and figure out why when it does. Sometimes a transitory event will kills the crop &#8212; the equivalent of a freak hailstorm. It&#8217;s okay. Repeat methods that fail due to outside influence but if it doesn&#8217;t feel right or isn&#8217;t working for you, try something else.</p>
<p>I&#8217;ve tried more than a few things that didn&#8217;t work for me. Points systems that lead to rewards. Withholding simple pleasures. None of them worked for long. I found lists to be effective but they needed to be short, specific, and updated frequently.</p>
<p>I put a cork board up over my desk a few months ago. Along with a few personal keepsakes, I keep a few things pinned up as reminder of what I’m working towards. First there’s the <a href="http://www.themarysue.com/things-we-saw-today-the-norse-crisis-flowchart/">Norse Crisis Flowchart</a>, because it’s always good to remember to blame Loki. I have a list of goals for the current month. A growing collection of index cards with inspirational quotes. Finally, I have a spreadsheet of SFWA markets with response times and notes about what they’re looking for and my experiences submitting to them, that I refer to when I build my submission plan for new stories.</p>
<p>My 15 year old self didn’t know what he was doing, but that’s the thing about goals; if they’re want them bad enough, you don’t give up on them. You keep chipping away, for years or decades, if necessary.</p>
<p>What are your techniques for goaltending? What has, or hasn’t, worked for you?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inkpunks.com/2011/10/14/shifting-sand-the-art-of-tending-goals/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Folding Socks w/Nick Mamatas</title>
		<link>http://www.inkpunks.com/2011/08/16/folding-socks-wnick-mamatas/</link>
		<comments>http://www.inkpunks.com/2011/08/16/folding-socks-wnick-mamatas/#comments</comments>
		<pubDate>Tue, 16 Aug 2011 20:06:04 +0000</pubDate>
		<dc:creator>Adam Israel</dc:creator>
				<category><![CDATA[Guest Post]]></category>
		<category><![CDATA[Process]]></category>

		<guid isPermaLink="false">http://www.inkpunks.com/?p=406</guid>
		<description><![CDATA[The Inkpunks have asked me to discuss my fiction-writing process, which struck me as an odd request. The process one uses to write fiction hardly matters as far as the end result goes. One may as well ask how writers fold their socks. Do they roll them up in balls, just lay them flat, fold [...]]]></description>
			<content:encoded><![CDATA[<p>The Inkpunks have asked me to discuss my fiction-writing process, which struck me as an odd request. The process one uses to write fiction hardly matters as far as the end result goes. One may as well ask how writers fold their socks. Do they roll them up in balls, just lay them flat, fold over once? Who cares? Whatever works, works. I was approached for this essay because of my how-to book <em><a href="http://www.apexbookcompany.com/collections/books/products/starve-better-surviving-the-endless-horror-of-the-writing-life-by-nick-mamatas">Starve Better</a></em>, which covers both short fiction and short non-fiction, and I said as much there. But, process. Okay.</p>
<p>My process is basically this: I spend a fair amount of time thinking about a story. I&#8217;m usually preoccupied with formal elements: should I write this in first person, past tense, have two storylines running at the same time, tell it all in flashback, etc.? When I figure out something formally interesting, I then come up with a first sentence. When I have that, I sit down and write the story.  I keep the Internet on for research purposes, which I perform on an as-needed basis. If I need to know something, I look it up on the spot. It&#8217;s impossible for me to leave something for later. Usually, I hit the &#8220;ending&#8221; and realize that there is more story to go, then finish it up with a final page or so. Then I look at who is still awake and on GChat and beg someone for a proofread. Not a critique. A proofread.</p>
<p>Then it&#8217;s done. I spend almost zero time revising, make no outlines, and don&#8217;t put a story aside for a few weeks to return to it later. That&#8217;s it. I generally finish a story in one sitting, though some more difficult stories take up a few evenings. Length is only a secondary factor—I&#8217;ve written novelettes in a day, but one 1800-word short story took me a week. For novels, I treat individual chapters as short stories. Sometimes, I might add a sentence or three after the fact, and indeed, often after a sale but before publication.</p>
<p>I don&#8217;t recommend this process for anyone, not even me. It&#8217;s not appropriate for the writing of lengthy novels, which many people wish to write. It&#8217;s a pretty exhausting process as well. Ever pull an all-nighter in college? It&#8217;s like that. After about a decade of practice, I&#8217;ve managed to make it work fairly efficiently. Occasionally, I&#8217;ll have a run of doing a story a week for three, or four, or six weeks. This year so far I&#8217;ve managed to produce stories, mostly on solicitation, for the anthologies <em>Demons, Long Island Noir, Future Lovecraft, Black Wings II, Shotguns vs Cthulhu</em>, <em>West Coast Crime Wave</em>, <em>The Mammoth Book of Steampunk</em> (a novelette), and something for a tie-in book the name of which I cannot yet reveal. I&#8217;ve also produced a number of essays.<em> </em>But I still don&#8217;t write very much. When I have lunch with a writer friend, he often says something like, &#8220;I have twenty-two stories out on submission.&#8221; I don&#8217;t think I&#8217;ve ever had more than three or four out at a time after I got past the days of universal rejection.</p>
<p>I developed my process for mercenary reasons. For a long time I supported myself by writing non-fiction—journalism, copywriting, and even term papers for college students with more money than brains. The price was right. Even small political journals will apologize for paying as little as twenty-five cents a word; in the world of short genre fiction that&#8217;s top-dollar. I often had multiple daily deadlines, so short stories had to be squeezed in. The sprawling novels beloved of the publishing industry were a scheduling impossibility. I also discounted the future by writing work I could sell relatively quickly, instead of spending years on a novel first. My stories still tend to be on the short side—2500 words is a sweet spot for me.</p>
<p>The secret for me is figuring out the structure first, then filling the frame with the information the story should actually contain. Back when I was editing <em>Clarkesworld</em>, the plurality of the stories I rejected had informational problems—elementary lapses of point of view, false suspense, tedious exposition, and the like. The formalist method not only precludes such errors, it lets the story tell itself. After all, there is an infinite amount of information that could be disseminated about any individual or circumstance, as the endless volumes on the life of Christ, or the influence of the French Revolution, or those ol&#8217; debbils the carbohydrates demonstrate. Form is like a cookie-cutter of any shape you like, used to slice a consumable bit of informational dough out from an infinite plane of the same.</p>
<p>Ultimately, the process is occult. Where do ideas come from? How do I know that the form I selected was correct? Honestly, I spend almost no time thinking about any of this. Hell, I&#8217;ve only recently realized that I write stories form-first. I&#8217;ve done it just eighty times or so in the last decade. (Essays are written differently. Novels are a variation just different enough to exclude.) Not too often, really. Writing fiction is like folding socks in that we all have our own way of doing it. Writing fiction is also like folding socks in that changing one&#8217;s method will not likely lead to cuter, or warmer, feet.</p>
<hr />
<p><a href="http://www.apexbookcompany.com/collections/books/products/starve-better-surviving-the-endless-horror-of-the-writing-life-by-nick-mamatas"><img title="Starve Better" src="http://cdn.shopify.com/s/files/1/0000/7796/products/Starve-Better-Front_medium.jpg?101471" alt="" width="155" height="240" align="right" /></a></p>
<p>Nick Mamatas is the author of three and a half novels, over seventy short stories, and hundreds of feature articles, and is also an editor and anthologist. His fiction has been nominated for the Bram Stoker and International Horror Guild awards and translated into German, Italian, and Greek; his editorial work with <em>Clarkesworld</em> earned the magazine World Fantasy and Hugo award nominations. Nick&#8217;s reportage, short stories, and essays have appeared in venues such as <em>Razor</em>, <em>Asimov&#8217;s Science Fiction</em>, <em>Silicon Alley Reporter</em>, the<em>Village Voice</em>, <em>The Smart Set</em>, <em>The Writer</em>, <em>Poets &#038; Writers</em> and anthologies including <em>Supernatural Noir</em> and <em>Lovecraft Unbound</em>. He teaches at Western Connecticut State University in the MFA program in Creative and Professional Writing, was a visiting writer at Lake Forest College and the University of California, Riverside&#8217;s Palm Desert Campus, and runs writing classes in the San Francisco Bay Area.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inkpunks.com/2011/08/16/folding-socks-wnick-mamatas/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>A thousand words</title>
		<link>http://www.inkpunks.com/2011/08/05/a-thousand-words/</link>
		<comments>http://www.inkpunks.com/2011/08/05/a-thousand-words/#comments</comments>
		<pubDate>Fri, 05 Aug 2011 20:26:33 +0000</pubDate>
		<dc:creator>Adam Israel</dc:creator>
				<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://www.inkpunks.com/?p=398</guid>
		<description><![CDATA[I had a conversation recently about world building, and if it was more effective to make up places stitched together from real ones, like Capital City or Metropolis, or to take an existing one and make subtle changes to fit the story. I argued that, when writing a story set in the modern world, that [...]]]></description>
			<content:encoded><![CDATA[<p>I had a conversation recently about world building, and if it was more effective to make up places stitched together from real ones, like Capital City or Metropolis, or to take an existing one and make subtle changes to fit the story. I argued that, when writing a story set in the modern world, that the background should be as real as any place and there wasn’t, by and large, a good reason to make one up just to avoid doing the research to get it right.</p>
<table border="0" align="right">
<tbody>
<tr>
<td><a href="http://www.flickr.com/photos/stonetable/79047058/in/photostream"><img src="http://farm1.static.flickr.com/36/79047058_6db9d0aa01_m.jpg" alt="" border="0" /></a></td>
</tr>
<tr>
<td>Cute &#8212; adorable, even, but limited.</td>
</tr>
</tbody>
</table>
<p>It reminded me of an early story I wrote that suffered from generic setting syndrome. Any background details that did existed were thrown there haphazardly and not in any real sense of historical place. I didn’t see a problem with it at the time — after all, it was the characters that mattered, right? Kind of.</p>
<p>Just shy of two years ago I attended a weekend photography workshop in Toronto. Prior to that, I’d been snapping pictures but not putting much thought into it. Point, zoom, and shoot. Much like that early story, the subject of my photographs filled almost the entire frame, leaving little else for the imagination.</p>
<p>Somewhere along the line, we discussed telling a story through a photograph along with concepts such as the <a href="http://en.wikipedia.org/wiki/Rule_of_thirds">rule of thirds</a> and <a href="http://en.wikipedia.org/wiki/Depth_of_field">depth of field</a>. Something clicked in my writer brain; the little gears whirred away in the background and churned away until it could put it in terms I could understand.</p>
<p>One of the most valuable lessons I’ve learned is that there’s a difference between telling a story and telling a story dramatically, and that tenet isn’t exclusive to writing. The words we choose to use to communicate direct how the reader sees our stories. It works the same way for artists and photographers.</p>
<table border="0" align="left">
<tbody>
<tr>
<td><a href="http://en.wikipedia.org/wiki/File:Rivertree_thirds_md.gif" rel="lightbox[398]" title="A thousand words"><img src="http://upload.wikimedia.org/wikipedia/commons/c/ce/Rivertree_thirds_md.gif" alt="" align="center" border="0" /></a></td>
</tr>
<tr>
<td>Animated image built from color and black &amp; white<br />
with grid source images, demonstrating the rule of thirds.</td>
</tr>
</tbody>
</table>
<p>Think of the <a href="http://en.wikipedia.org/wiki/Field_of_view">field</a> of view as you tell a story. What details to include? Which should you leave out? Well, the rule of thirds suggests dividing your work into nine equal parts by vertical and horizontal lines. Align your subject along the intersections to create more more dramatic image.</p>
<p>The thing that’s important to your story is in the foreground but the background — the things you include but leave slightly out of focus, contribute to a much broader experience. Below the cut are a few more photographs that may help illustrate the idea.</p>
<p><span id="more-398"></span></p>
<table border="0" align="center">
<tbody>
<tr>
<td><a href="http://www.flickr.com/photos/stonetable/44171179/in/set-966448/"><img src="http://farm1.static.flickr.com/30/44171179_be783c0c5c.jpg" alt="" align="center" border="0" /></a></td>
</tr>
</tbody>
</table>
<p>This photograph is zoomed in solely on it&#8217;s subject but still tells a story. It&#8217;s a building, obviously, but one with a story. It&#8217;s an urban storefront, possibly tied to a church &#8212; one with a lot of problems (4 shizzle).</p>
<table border="0" align="center">
<tbody>
<tr>
<td><a href="http://www.flickr.com/photos/stonetable/196549349/in/set-72157622335215988/"><img src="http://farm1.static.flickr.com/75/196549349_c1e7a86953.jpg" alt="" align="center" border="0" /></a></td>
</tr>
</tbody>
</table>
<p>The man wearing the purple hat looks a little bit like Pop-Eye. In the background we see a wall with some vegetation clinging to the side and a few people who are dressed differently than our focal point. He’s an entertainer at the Bristol Renaissance Faire, explaining to the audience that they have been divid into two cities — Sparta and Trojan — and he is their champion. They must cheer the loudest to prove that they are the best, or else he will have to save their honor by eating&#8230;mud. Long live the <a href="http://www.mudshow.com/index.htm">mud show</a>.</p>
<table border="0" align="center">
<tbody>
<tr>
<td><a href="http://www.flickr.com/photos/stonetable/196615463/in/set-72157622335215988/"><img src="http://farm1.static.flickr.com/72/196615463_0515e5f00a.jpg" alt="" align="center" border="0" /></a></td>
</tr>
</tbody>
</table>
<p>Aha! Here we have Guido of the <a href="http://www.theswordsmen.com/">Swordsman</a> (bold and stupid men, at your service). He&#8217;s on stage, caught in the act (but of what?) by his nemesis, Dirk.</p>
<table border="0" align="center">
<tbody>
<tr>
<td><a href="http://www.flickr.com/photos/stonetable/78998894/in/set-1691537/"><img src="http://farm1.static.flickr.com/42/78998894_23aa8f5096.jpg" alt="" align="center" border="0" /></a></td>
</tr>
</tbody>
</table>
<p>Just like a photograph, our words shouldn’t be focused solely on the subject of the story. Zoom out a little bit and give the reader a wider context — setting, side characters, motivations, etc. It&#8217;s through the noise in the background that a story emerges, and we see and interpret the world around us.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inkpunks.com/2011/08/05/a-thousand-words/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Know your markets</title>
		<link>http://www.inkpunks.com/2011/06/03/know-your-markets/</link>
		<comments>http://www.inkpunks.com/2011/06/03/know-your-markets/#comments</comments>
		<pubDate>Fri, 03 Jun 2011 20:59:28 +0000</pubDate>
		<dc:creator>Adam Israel</dc:creator>
				<category><![CDATA[Basics]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://www.inkpunks.com/?p=350</guid>
		<description><![CDATA[I occasionally overhear part of a conversation where someone mentions Duotrope and the other person admits that they’d never heard of it before before. What? I think to myself, How can you not know the holy grail of market research known as Duotrope? Then I remember that all knowledge is subjective and that, one day, [...]]]></description>
			<content:encoded><![CDATA[<p><!-- p.p1 {margin: 8.0px 0.0px 0.0px 0.0px; text-indent: 18.0px; font: 13.0px Optima} p.p2 {margin: 8.0px 0.0px 0.0px 0.0px; font: 13.0px Optima} p.p3 {margin: 8.0px 0.0px 0.0px 0.0px; font: 13.0px Optima; min-height: 15.0px} span.s1 {text-decoration: underline} -->I occasionally overhear part of a conversation where someone mentions Duotrope and the other person admits that they’d never heard of it before before. <em>What?</em> I think to myself, <em>How can you not know the holy grail of market research known as Duotrope? </em>Then I remember that all knowledge is subjective and that, one day, I didn’t know what it was, either.</p>
<p>Presumably, you know how to brush your teeth, comb your hair, and tie your shoes but you don’t really think about the acts themselves. You learn, you internalize, and then you <em>do</em> without conscious effort. The basics of writing are much the same way, from the act of forming a complete sentence to submitting a finished manuscript. The following advice is purposely simple, a primer for those just getting ready to submit.</p>
<p><span style="text-decoration: underline;">Goals</span></p>
<p>People usually dive right into the research and flail like a swimmer at high tide. It’s an approach I’ve used on more occasions than I’d like to admit but there is  better way. The first thing you should do is ask yourself a very important question: what is your goal?</p>
<p>We all write for different reasons; understanding yours will save you a lot of frustration later. Assuming you want other people to read your work, I look at three factors primarily.</p>
<p>What kind of exposure does the market have? If I can get more readership posting to my blog than if they published a story, they’re probably not the right kind of market for me. Figuring out what the readership numbers are is a dark art. There are ways to see gritty, probably inaccurate numbers on some website, but look at the website itself. Is it easy to read? If you google their name, do they show up? Do they have a Wikipedia page? Are other people talking about them? All fairly easy things to find within a minute.</p>
<blockquote><p>Money flows towards the writer — <a href="http://www.sff.net/people/yog/">Yog’s Law</a></p></blockquote>
<p>Secondly, what is their pay rate? This can be a sticky subject for some, and is very subjective based on your goals. Publishing is often a for-the-love effort by the editors and some markets only offer token payments, if that. If, however, they are a for-profit venture, have a shiny, professionally-developed website and are selling subscriptions, I would expect a semi-pro rate. Writers create content, and if that content is sold, writers deserved to be paid for their effort.</p>
<p>Some of the very best markets don’t pay at all, and that’s okay, too. You come to know who they are. Electric Velocipede. Lady Churchill&#8217;s Rosebud Wristlet. Sybil’s Garage. They pay little to nothing but are highly respected for the quality of their work and as such are read by fan and editor alike.</p>
<p>Breaking into a prestigious market is a perfectly valid goal. Take a look at the award-nominated and winning magazines and you’ll find a who’s who of markets that are high quality and well-respected. Selling a story to any one of them is a point of pride.</p>
<p><span style="text-decoration: underline;">Market research</span></p>
<p>Now that you have an idea of what you’d like to achieve, the real work begins: finding your markets. In days of old, you would have lugged out the doorstop known as the Writer’s Marketplace. Thankfully, we’ve come a long way, kid. Your search begins and ends at <a href="http://www.duotrope.com">Duotrope</a>. (<a href="http://Ralan.com">Ralan.com</a>, I should note, is genre specific and has good listings but doesn’t have any search functionality so I generally leave it for secondary research.)</p>
<p>With Duotrope, you can search for print or electronic markets, by pay rate, by genre, etc. Once you’ve narrowed down the results to fit your goal, I urge you to pay close attention to the details. You’ll find detailed response time reports so you can see what other Duotrope users are experiencing from their submissions. You can also see the average acceptance/rejection rate based on those numbers. The statistics are only so accurate, but when I see a market with a 65%+ acceptance rate, I know that they’re probably taking every legible submission not written in crayon and that’s doesn’t fit with my goals.</p>
<p>Even though I know my markets, I re-check their Duotrope listing and website from time to time, to see what’s changed. Editors move on, formats change, and markets close. You’ll also hear praise and damnation from fellow writers based on person experience. I keep a spreadsheet of markets that I’ve submitted to, make a note if I or someone I know has had a bad experience with them, and make a priority list, by story, of where I want to submit.</p>
<p><span style="text-decoration: underline;">Submitting</span></p>
<p>You’ve written your story, you’ve found your target markets, and now it’s time to submit. Follow the guidelines, ask questions if they aren’t clear (because sometimes they aren’t), and learn to love Standard Manuscript Format. William Shunn has written the definitive guide to <a href="http://www.shunn.net/format/story.html">Standard Manuscript Format</a>. My friend Kaolin, a geek of the highest order, also wrote a nifty tool to <a href="http://erif.org/manuscript/">automatically generate your final document</a>.</p>
<p><span style="text-decoration: underline;">Rejectomancy</span></p>
<p>Everyone will tell you that this way lies madness but it’s a case of do as I say, not as I do. That said, there are plenty of ways to scry your stories fate. Duotrope lists the expected and actual reported response times for any given market. What’s even better, if you sign up and track your submissions, they offer an RSS feed listing the recent responses of markets you have a pending submission at. This can be a useful reminder. You might find that your story has been waiting three times the current average response time. It might be too soon to query but it is a good reminder for checking your spam folder.</p>
<p>Most markets will list how long you should wait before querying. Even if others are receiving responses before you, resist the urge to query early unless something has obviously gone missing (your submission disappearing from the market’s status page, for example).</p>
<p><span style="text-decoration: underline;">Plays nice with others</span></p>
<p>The more you submit, the more likely it is that you’re going to interact with an editor. You’ll rack up a stack of rejections both form and personal, rewrite requests, and hopefully more than a few sales. You’ll develop a working relationship and reputation with these editors. Be professional. Communicate clearly. Above all, don’t be an asshole.</p>
<p><span style="text-decoration: underline;">Handling rejection</span></p>
<p>When your rejections wing their way home again, be prepared to resubmit. I allow for, at most, a 24 hour cooling off period before sending a submission back out on its way.</p>
<p>Log your rejections in your spreadsheet, in Duotrope’s submission tracker (because good statistics help us all), and/or in the <a href="http://community.livejournal.com/ra_log/">Rejection/Acceptance log</a>. Make a witty comment on Twitter or Facebook or behind the closed doors of your writer&#8217;s group. Keep the message positive. Don’t assail the market for rejecting you — editors will see and remember your name in a bad way.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inkpunks.com/2011/06/03/know-your-markets/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

