Current read: Victory Faust, by Gabriel Schechter

This is arguably the best baseball book you’ve probably never heard of.

My copy was a holiday gift from Mr. Schechter himself. I met him at a mutual friend’s birthday party, one mainly focused on baseball enthusiasts, and he was handing out copies. I’m glad he was.

In 1911, a farm guy from Marion, Kansas (one county over from the one where my parents grew up) was supposedly told by a fiction fortune teller that if he went to Manhattan (New York’s, not ours), he would become a successful baseball player and meet the woman of his dreams. Charles Victor Faust was not, shall we say, richly endowed with any better critical thinking skills than he was a pitching arm, a batting eye, or a sense of baserunning. He hared off to New York City to thrust himself upon John McGraw’s New York Giants, a team that had come close to glory in recent years but never quite made it.

Faust made enough of a pest of himself to gain admission to the Giants’ clubhouse, if not the roster. He proceeded to entertain, lighten the mood, and make a fool of himself daily. He was the only one not in on the joke. Baseball players being a superstitious lot, the fact that New York tended to win with Faust in attendance got their attention. They took the correlation seriously enough for McGraw to keep Faust around the dugout, entertaining fans with his warmups, absorbing the heckles and pranks of the players. At least, when he wasn’t doing vaudeville or sulking because McGraw wouldn’t give him a contract.

The pride of Marion even got to appear in a couple of late-season games. He hardly lit the diamond on fire, but he has stat lines on Baseball-Reference.com and I don’t. The Giants won the pennant, but fell to the Athletics in the Series. Faust had worn out his welcome and migrated west, giving up on his delusions of big league pitching grandeur but not on a generally delusional nature. This was before Portland and Seattle had come to embrace their quirkiness, and he spent time in asylums in Oregon then Washington. He died of TB in Western State Hospital at Steilacoom, WA, where it seems the original numeric grave marker has in recent years received augmentation from a plaque mentioning him by name. About time.

Schechter tells all this far more effectively than I have summarized it.  His lengthy research shows in the detail he has uncovered about a ballplayer who was otherwise somewhat of an obscure caricature of a ballplayer. He offers just enough personal comment to be witty, but never to slant the narrative. If you like offbeat baseball history, this book is a yes. If you appreciate quality writing, another yes. If you respect deep research, three-for-three.

Secondary market copies go for $20-30 at this writing. I looked for a way to buy them direct from Schechter (who surely has a stockpile given that he brought some as gifts) and did not find one, but affordable copies are available.

New release: the Entrepreneur’s Survival Guide, by Randy Hayes

This volume is now available to purchase. At one point or another, I performed in most of the editing modes, but mainly developmental.

Randy and I go back forty years, to when he was a year ahead of me in college. He was always an unconventional thinker, a stand-up guy, and while quite bright, leveraged his natural intellect by seeking out people who knew things he did not. He was never for five seconds of his life at risk of becoming one of those stupid-smart people who get so caught up in all their knowingness that they resist learning unless it comes from approved directions. (Most people with that mentality get Ph.Ds and become professors. Academia is the only place that will put up with that crap because it’s common enough.) Randy is the kind of guy who, if he wanted to learn to skate backward, might just go to the rink and find some kids who were doing that, and ask whether they would teach him. And they would, because he’s very amiable that way.

He won’t tell you the juicy details, but as a businessperson Randy has enjoyed enormous success in some very difficult environments, notably investing. When he brought me this book idea, therefore, I was very glad to be working on it because I have many of the entrepreneurial wrong tendencies and bad habits that the book describes. I have taken guidance from him in ways that I see manifested in his book, and they are very helpful. For example, for five years now I have been carving out an hour a week to do CEO things, which I define as management and planning activities that are not doing the actual hourly paid work that is my main business focus. It has helped me to stay focused, to review a business plan, to recognize my weaknesses. Randy is an authority on this stuff.

Want a sample of the most notable principle of Randy’s that guides me? Very simple. Offer solutions rather than services. Think about what I do. Many editors think that their work is to change people’s use of the English language. No; that’s the car, not the journey. People come to editors because we are industry pros whom they expect to know things we can share with them. Editing a book ms is not the end goal; the end goal is the best possible book or other ms consistent with the author’s objectives. Editing is just one of the ways we can help make that happen.

I knew this intuitively, but I really knew it when Randy codified it. Take websites. No one just wants a website if for commercial purposes. People want websites in order to share information, answer common questions, describe offerings, allow viewers to inquire further, and generally present the best possible marketing and informational face to the world. The website just happens to be an efficient means to those ends. The web designer who believes that her job is to push HTML and scripts around has missed her real job and needs to remember why people hire her. So in this context, I offer clients the best possible guidance (including editing support) to help them achieve their writing objectives. It is wonderful when people want to become better writers, but sometimes a writer just wants it out the door and doesn’t want to learn.

Think that’s lunacy? One of my more recent clients was a nonagenarian with a bucket list book, a wonderful man who was a marvel to work with. My directive was to get the ms from draft to publishable, staying as true as possible to the au’s intent and experiences. I was approached, I believe, because evidence indicated that I understood this. He passed on, sadly, a year after the publication. He never made back his money and did not give a rip if he did. He saw his book in print, looking professional and with the benefits of experienced handling, and had that joy while he could revel in it. Mission accomplished all around, with the helpful intercession and interpretation of one of the best in the business, Maggi Kirkbride (who does not happen to work on fiction, thus the approach to me).

Yeah. Randy has that kind of impact. As I worked through his ms, I saw numerous areas where I could improve, and other areas where I already had good practices but it helped to see them codified and reinforced. This is why his book is such a gift for entrepreneurs.

When the original ms came to me, it needed a fair bit of polish and consideration. Randy began our relationship with as many bad writing habits as the typical college graduate, but the difference is that he has declared war on them and worked to eradicate them. The work has been successful. My task was to take the mistakes (comma splices, excessive adverbs, hyperdependency on parens and em dashes) out of Randy without taking the Randy out of Randy. His basic style is informal, friendly, and approachable. For the most part, anyone at the GED level or higher can understand all of it.

We batted it back and forth. Oh, how we batted it back and forth. Randy’s always coachable, and is one of those clients who wants to know why. Why do we do it this way? What’s wrong with doing it that way? The best clients, and the ones who get the most out of what they pay me, are always the ones who ask me why I did things. Sometimes they will present alternatives and ask me why those options aren’t a better method. Well, sometimes they are. Editing isn’t sitting like the statue at the Lincoln Memorial, a giant gazing down upon the masses. Editing is making written material the best it can become. If my client has a better idea than me, that’s excellent because in the ideal world it would be the author’s creativity that would formulate solutions. So I would toss something out there, and he’d often accept it or come up with a different way of incorporating it. I did the appropriate thing: beam with pride and keep marking.

The last major step was the dignified execution of a Faulknerian darling. Randy wanted to incorporate a marketing presentation that had been very popular. Why it was popular was obvious enough to me, but it also duplicated a lot of information. When I mused about that, the fact that he was readily open to the idea told me that he’d had that same thought. Protip: When your client accepts a fairly radical change idea with surprising readiness, it’s probably because they have already been wondering about it. I left the decision to him with a recommend that he fold it in. He folded it in. With that, the book’s last major hitch was handled. He’d even bent a little bit on one of our longtime factual disagreements; an amiable difference, to be sure, but he did provide enough context that a reader couldn’t just poke a hole in it as presented. Excellent; that was all I’d wanted.

What authors should know is that some of what we do involves review protection. The editing mind looks at what the au did and comes up with the most caustic comment a reviewer might offer (and we have the capacity, if we wish, to be much meaner than most reviewers; we just should not often want to be) if that were stetted. That editing mind then figures out what changes would render the possibility of such review comments unjust; someone might still say it, but importantly, they would be incorrect and probably wouldn’t even think of it because most people at least have a process for not making up crap.

This was a lot of what I did for Randy. I foresaw the spots where readers and reviewers might start to think he didn’t know as much as he purported to (which would be wrong on their part). I got him to make enough changes that those weak spots were no longer present.

The remainder is one of the most important books any entrepreneur could read. As an entrepreneur myself, I can just about assure even seasoned pros that they’ll find new ideas.  Randy is a good guide as well as a good guy, and he will give your fair value.

Editorial Maverick: why did that book get brutal reviews?

If you’ve been reading here very long, you know by now how stupid it is for a book reviewer to snip: “Well, obviously she should fire her editor,” or “Duh. Clearly she didn’t hire an editor.” The reviewer cannot possibly know how much editorial guidance might have existed and been disregarded, nor what sort of editing might have been sought or employed. When you read that review, just mentally mark that reviewer down as not knowing what he’s talking about.

If that reviewer understood anything about the different editing modes, about the way the relationship goes, or had at least some basic insight beyond ‘me no like book,’ they’d show it.

Here is the takeaway in context: All those truly awful self-published books you’ve seen, been cajoled into trying, bought at SF con dealer rooms, ended up with at used bookstores, came up on searches and looked cool enough to try, then turned out unreadable? Many of their authors considered an editor, then talked themselves out of it with:

  • Oh, no. No, no, no. I am not paying $1000 for you to mess with my baby! (So you’ll raise the baby, but you won’t get it medical care. Okay.)
  • Sorry, but I like my original better than your sample edit. (That, or you got a serious shock when you saw all that “red ink” and decided you need someone who “believed in your work,” that is to say, didn’t know how much help it really needed.)
  • This would damage my unique style. (Yes. Your hyperdependence on passive voice, your head-hopping, and your grammatical incontinence could be considered a ‘unique style.’ And if you are fond of all that, I wish you the best.)
  • I can find someone on Sixerr or Sevenerr or whatever who’ll do it for half that. Can you match? (Can? Yes. Will I? Zero chance, and I’ll probably decline the project at any price after that. Anyone shopping purely on price is not my target market.)

You get the idea. It’s all about money, fear, ego, or some combination of these. My rejoinders (internal to my own mind, not articulated) might seem blunt, but do remember that blunt is part of the benefit. If they don’t want that, I get it, and I accept. We can both move on.

The reality is that most people put weeks, months, or years into a book from which they hope to make money, yet rarely choose the full benefits of professional feedback.

Most such books are lost in the sea of mediocrity. They didn’t have to be.

Editorial Maverick: forgetting how not to know

It’s a problem in some non-fiction, but it’s endemic in fiction. It is worse in semi-autobiographical fiction, because the au “experienced” the events and “saw” the places and people. The same effect occurs when the au has been working on the story (in mind, on paper, on computer, wherever) for a very long time. They “know” all of it so well that they can’t get back to where the reader will be: knowing none of it until told.

While it’d be great if authors learned how to overcome this, most will never make the effort. As long as they are working on details they lived, or might as well have lived given how long they’ve been crafting the story, they will “know.” The best way I can think of to un-know is what I call the readercam: the focus position of the reader’s view. Decide where the readercam is on this scene, and think about how much of it must be described to help your mom understand it over the phone. I can tell them to do that until I’m winded, though, and few ever will.

And that’s okay, because it does make my role essential. As long as I have offered my best professional guidance toward a better outcome, if the client declines it (as in “nah, I’d rather just let you catch that kind of thing”), that’s okay too. And I’m not just saying that because it means I have paid work to do. Another reason is that such worries can get in the way of creative flow. Let’s ask the question. Which would you rather have written?

  • A brilliant story with piles of mechanical flaws, perspective issues, and grammatical errors?
  • A dull story executed to scholarly perfection?

Yeah. And that’s why I don’t get too worked up because someone tore through cranking out the ms in a creative whirlwind: I represent the stabilizing, logistics-handling, dull repairperson who cleans up after the party. I only get worked up if the story is dull, stupid, etc. I can fix most of the bad habits and problems that come from the first, especially if the client realizes the situation (I’ll help; oh, how I will help) and embraces editing as a liberating force for creativity. The second will still be a dull story unless there are major changes that make it no longer the au’s original story.

And at that point, editing is not the issue.

Editorial maverick: phases of writing growth…and lazy habits

I’ve observed three distinct phases of writing growth/evolution.

The first phase is what I’d expect from a high school sophomore who does not plan to graduate with distinction; mostly intelligible, but with enough basic problems that fixing bad habits are a ways off. It mixes up to/two/too, can’t get the possessive apostrophe right, and doesn’t know what it’s doing with punctuation. It sometimes believes that more exclamation points are more impactful!!!!!!!!!!!!!!!!!!!!!!!! At other times, it believes in no punctuation, nor even para breaks.

It’s awful, but it will suffice in life for basic needs. For many people perhaps that’s satisfactory. (Maybe they’re brilliant at plumbing. Great. You hire me to write important stuff for you, and I’ll hire you to do plumby stuff. All good.) That might seem heretical, but becoming a quality writer is not easy for most people, and until people come to me insisting that the first tier is acceptable for professional published writing, we have no quarrel.

The second phase writes clearly enough, but its lazy habits keep it stuck in the middle. It overuses adverbs. It does not understand what’s wrong with comma splices. It loves italic emphasis, ellipses, em dashes, passive voice, and various other common writing weaknesses. It ranges too far afield, too often, from the straightforward declarative sentence. Most first-time novelists arrive in this stage, and many never exit it before they self-publish.

The third phase has learned to avoid the second’s failings. Up to this point, editing can only partly be about content because there are many mechanics to address. The term “cognitive load” comes into play, because one is pouring on so many other teaching points that some clients could become overwhelmed with second-phase and third-phase feedback. In this stage, the writer can write well, and our focus is on the fine points: pacing, clarity, word choices, flow, and so on.

For those seeking to exit the second, here are things to fix and how to fix them:

Question every non-dialogue adverb, with the goal of choosing a better verb. People told you to burn your thesaurus; this is why you disobeyed.

A comma splice occurs when the comma divides a sentence into parts that could stand alone, it looks like this. Unlike most parts of speech, which have their roles and places and jobs, this is an error pure and simple.

Permit yourself one non-dialogue italic emphasis per 25,000 words.

Permit yourself one non-dialogue ellipsis per 20,000 words.

Permit yourself one or two em dash constructions per chapter. And begrudge.

Launch a frontal and flank attack on non-dialogue passive voice. Attempt to recast every last instance. Surrender only when there is no other option, such as there is no definable subject to assign.

As hinted earlier, dialogue is different. Rules for dialogue and internal monologue (thoughts) are looser because people think and speak otherwise than they write. That doesn’t meant that all the rules are suspended, but it does mean more patience for italics, ellipses, and so on. You have heard the breezy boast “I write like I talk,” as if that’s something to be glad about, but you might not have heard my rejoinder: “Too bad, because people don’t read the way they listen.” Broken Dolly Syndrome ensues. And yet, as with everything but those damn comma splices, there’s a time and a place. Dialogue and IM, treated as spoken, can be more “write like I talk” because they are talking in some form. Of course, one really means “write like your characters talk,” but people get the idea.

When I get a manuscript, I must figure out how much of phases one and two remain in play. Phase one writers rarely end up hiring me, because my report says that their writing needs a lot of work, and they either don’t want to do that work or didn’t want/expect that answer. Phase two writers are likelier to hire me, especially if I can show them how to get to phase three (I can). Phase three writers are the toughest and most rewarding, because they ask questions. Lots of questions. They want to know why. I must not tell a phase three writer to do anything unless I’m ready with the reasoning, because odds are they will ask me for it.

This is good. This is how I grow in my own work.

Editorial maverick: carts and horses

Some of you know I’m doing part-time office work that entails a lot of technical editing. I like it: It’s an excellent company high up in its field, treating staff well and producing work of which one can be proud. Half the staff have advanced degrees. For me, it’s a little steadier income without cutting into my freelancing work.

While they were excited to bring a pro on board, I think some aspects of the change took them by surprise. For one thing, I think they expected me to rip their writing apart a lot more comprehensively; for another, pretty sure they expected some debates about industry usages. The best handling of those situations brings with it some lessons specific to tech editing but also germane to other editorial work.

We come across it all the time: this idea that editors are the people who go in and dismantle your writing with ruthless precision. There are times for that…but not when one is already dealing with capable and very coachable writers. If one of my colleagues’ writing were weak, I wouldn’t hesitate to fix anything that needed it, but even our subcontractors write fairly well. My work as an editor is not to criticize or correct; those are just aspects of progress toward the goal. My work as an editor is to help the content become the very best it can be. If that means critique and correction, we do those. If that meant burning a photograph of a lemur over a purple candle flame at midnight while chanting in Old Slavonic, I’d be doing so. In this case, the best way to improve the content is to offer minor corrections with sound explanations. These are people of science and reason who expect me to know more than them about English, and to help them become more proficient. If a para needs a complete recast, I’m glad to do so, but more often the need relates to subtler acts such as changing phrasal order for clarity and flow.

I haven’t said a word about style guides: AP, Chicago, etc. That’s because I understand that these are not bibles unless the management says they are (and ours sensibly does not). Style guides are like military regulations: They are for the guidance of command, not as straitjackets to it. The idea of writing something in a way that fails to communicate, but conforms to the hallowed style guide, is idiocy. Our management knows this, as do our writers. So the writers will ask me: “What is the rule here?” If there is one that sensibly governs, I’ll tell them; in many cases the area is grey, often straddling the gap between popular imagination of the rule and its strict letter. Join an editors’ group online and you can see posts daily bleating for help with some arcane point of style guide nitpickery they’ve been agonizing over for hours. Okay, if it’s a mandated usage, very well…but if you’re an editor, isn’t it your job to make the damn decision? Whose, if not yours? People look to us as informed guides to quality writing. Someone’s saying they’re afraid to guide? This is like a professional taxi driver afraid to trust/deviate from a map or a navigation system. Decide, and use the comments to explain the decision. And if the style guide isn’t even mandated, there’s even less pressure to conform. Do something intelligent in furtherance of the original goal, and help your people understand why you felt that was so. If you can be a professional editor, you have the writing skills to persuade and explain.

The other side that surprised my colleagues was that I take a very relaxed attitude toward industry usages, even where the common presentation strictly speaking violates some basic guideline. Should it be “small diameter poles” or “small-diameter poles”? Objectively, the latter; but the industry usage most often omits the hyphen, and we are communicating with industry members. It’d be idiotic to die in a drainage ditch over a hyphen. I’m the industry newcomer and this is tech editing. It is my job to drink from the industry firehose and learn language specific to expected usages. We should be consistent and clear; we should sound informed and intelligent; we should convey the views of highly expert people with professional voicing and presentation. If that means we don’t write this item name in what I consider the obvious way, because one of our people learned in school that there was a specific reason not to do so, I can either joust with my colleague (and his MBA plus thirty years of experience) or I can accept that he’s using sound logic based in educated thought. I should worry far more about helping my people sound their brilliant best than about imposing a foolish consistency.

That’s why tech editing is an unglamorous but very necessary field. A percentage of editors simply can’t operate without some form of Scriptural guide, and will inevitably find themselves asked to make decisions for which there is no clear direction cited in Chicago, and concerning which they thus won’t be able to convince the subject matter expert without that biblical backup. And yet so many technical specialists, unlike my colleagues, just can’t write worth a damn. They starve for editorial support–not from style guide literalists, but from colleagues who make them better and help them grow.

If I were starting as an editor right now, I would still set up a blog/website and I’d still take jobs involving manuscript fiction and non-fiction, but I know what my marketing would be. I’d imagine the industries I understood best and I’d start sending pitches to firms in those industries. I would invite them all to reach out to me with a page of text and whatever context they considered germane, and let me have a crack it it. I’d send back the samples in prompt fashion and see what happened. A good outcome would be a cost estimate query for a full report/manual/other doc, because then they’d be asking themselves whether this were affordable (and could they bill it out?). The secret of technical editing is that your client can usually bill their client for your work. If they find this to their best advantage, they’ll probably start sending you rush jobs with urgent needs (because they procrastinate or get swamped). Do them no matter how late you have to stay up. They’ll come to consider you part of the support system and they won’t want to deal with anyone else once they are comfortable with you. Nice work–you now have a client. Treat them right. Their greatest hours of need are your greatest moments of potential and value.

Editorial Maverick: the unlamented death of lolling

I refer, of course, to the unlamented abbreviation “lol.” I have a politically incorrect term for its addicts, one I will decline to share in a public presentation.

At first it was just a fun thing. Someone would private message something funny, and it was shorthand for saying that one was laughing aloud. All right. And then the cancerous node metastasized.

Soon it became the stand-in for a comma or even a period:

  • j: hi there
  • person: hello lol
  • j: how goes?
  • p: not so good lol
  • j: what’s wrong?
  • p: oh lol my car broke down on teh freeway lol and i had to have it toad lol now were getting evicted lol not sure what were gonna do lol maybe its time to get on the pole lol
  • how is this funny? doesn’t sound very amusing
  • i know rite lol

At that point I had to start controlling myself. Not only was it used when nothing was funny, but it made writing all but unreadable. I just stopped encouraging extensive conversations where I’d have to shovel through a lot of lolling. Now, I don’t worry about spelling errors, grammar, even case when typing in texts and private messages. Some people seem to imagine that editors spend every waking moment finding fault with their friends’ writing. If we did that, two things would happen. One, we’d be exhausted–too tired to do our work after all that free editing. Two, the problem would solve itself because no one would talk to us. All I care about is being able to make sense of the person I’m talking with. When something gets in the way of that, it also is exhausting.

But lolling seems to be in long-term care and about ready for hospice, and this would seem a perfect time for vocabulary assisted suicide. We don’t need this. We have emojis and other little face images that might not technically be emojis, but grouping them all under that term is convenient. The end of lolling seems at hand.

I won’t be attending the funeral, but neither will I grieve.

Editorial Maverick: don’t format it

One key aspect of transforming a manuscript (ms) into a book is formatting, sometimes called typesetting (I’m sure the term will be with us long after the last ink-stained hands have fallen still and cold). This is how it goes from Word format to something you can print as a book. It can mean inserting photos, cute drop caps (the extra large letter to begin a chapter), graphics for segment breaks (say, a cattle brand for a book on ranching life), and all that other prettying up. A basic version can be had by self-publishing through CreateSpace or something like it; if you want it fancier, you hire a formatter or figure it out yourself. Formatters are generally expert in Word and understand how the conversion tools work, knowledge only a few people need.

Whatever you do, please do not book-format your ms as you go.

For one thing, writers do not automatically know how to use Word’s features correctly. I say Word because I don’t work on G-word docs; I’d sooner work on a plain text file (which I’ll bring into Word anyway so I can use change tracking and commenting). If the ms is in G-word, well, I’ll work on it when it’s sent to me as a .docx file. What it means is that people wanting to line things up, make them all nice, will impose all sorts of oddness on the ms. Not knowing how to indent, they’ll just use tabs, or worse yet, hit the space bar five times. Not knowing how to insert a hard page break, they’ll just bang hard returns (the Enter key) until they’re at the top of the next page. These are problems because the editing process shoves everything around. It is almost certain to mess them up; lines might be inserted, margins changed, and so on.

The little graphics and other cutesiness (which I call it at this stage, because it belongs in the formatting stage; here it’s just clutter) are as bad. They make editing harder. If that isn’t enough to discourage novice authors, let’s try money. Anything that makes editing harder also makes it more expensive. So here’s the core of it: Why would you put in extra work that you will certainly pay to have undone, and on top of that, have to do it all again later? This does not make sense.

Here’s the proper order of Good Actions. First, write. If you’re going to indent paras, indent them using Word’s Indent feature; if you’re going to break pages at chapter end, just use Word’s hard page break (Ctrl-Enter). To break chapters into segments, just stick in a simple placeholder, for example three asterisks separated by spaces. Whatever you do, focus on writing, not cosmetics. Get the text as good as you can make it. Self-edit until it wrenches your soul…then let your editor go to work. You can use italics at this point, but don’t make typeface changes. Use something straightforward, typically Times Roman or Calibri or Arial. Left margin justified, right margin ragged. Leave placeholder markers for graphics to go in later, if you’re going to put in charts or photos or whatnot.

Many seem to feel that the decision whether to single space, one-and-a-half space, or double space is a Momentous Choice. Nah, not here. Your editor can undo it in five seconds, as long as it takes to Select All and go into the Line Spacing. What I usually do is edit with single spaces or 1.5, but what matters is what I use if I do a print review. I might edit it in single, then review and red-pen a copy in double. Costs me a little more in paper and ms heft, gives me more room for editing marks and insertions. At the end, I can convert it back to the way the au sent it to me.

If you’re going to try for traditional publishing, also called trad-pub (, then I don’t really understand the logic, but I will support you as you) then prepare to send queries and submissions to people who might or might not show an interest. If that’s the plan, then either follow the publisher’s submission specs or go with the industry standards.

If you are going it alone, then we’re probably still doing this together. When you have finalized the content, by whatever handing back and forth of the football you and your editor have determined should occur, then it’s time for formatting. Formatting creates galleys–probably final images of what will be published if the proofreading doesn’t find any errors. Any formatting mistakes, typos, alignment issues, and so on can be caught and fixed at this point.

Here’s another reason for this. The hardest part, for most people, is just getting it all down on e-paper. For some people it takes a decade or even two. However long it takes, the last thing you want to do as you attempt to express your thoughts or tell your story is to run around making little cutenesses. It makes the writing harder, and if there’s one thing writers don’t need it is to make writing harder.

Have you ever had someone look at you and tell you that you just unraveled months of frustration that drove them to sleepless nights, vodka, and feelings of deep inadequacy and hopelessness? People whose work is to help people get that experience. It is a special one.

If what you write has flaws and you can’t figure them out, That’s Why You Have An Editor. Step back fifteen yards from scrimmage and punt. Tell your editor the parts you don’t like, where you’d like special attention and input. Sure, you can self-edit, and in most cases you should do some of that before you send it off to a pro. But if your self-editing is bogging you down, your work is harder than it needs to be. The reason you have an editor is to help you get the text into suitable syntax, flowing well, reading consistently, and making sense. Get those benefits. Let your editor help. Get what you’re paying for.

Believe me, your editor wants it that way.

Editorial Maverick: tech editing

My world is a diverse one, with wide variety between different styles as well as modes. By modes I refer to developmental, substantive, line, and other forms of editing. By styles I refer to the subject matter: fiction (with many divisions), non-fiction (same), screen editing (don’t look at me), and technical editing among others. Only some of the knowledge carries over from one style to another. One of my favorite people, the awesome and capable Maggi Kirkbride, edits only non-fiction. I know academic editors, self-help editors, and so on. I have acquired a skillset in technical editing.

Since tech editing involves reviewing and changing subject matter experts’ work (we call those SMEs to show that we’re in the club), the first thing that happens is that one drinks from the knowledge firehose. If one has little knowledge in a given field, the question is how one works into a level of competence. Much looking up of terms, asking of questions, and hesitation before barging ahead with changes. In this style, any reference that sounds odd could in fact be an industry term loaded with meaning. After a time, one gets a sense for these. I have tech edited roleplaying game rulebooks, engineering documents, and forest products analyses. In all cases, while I had some fundamental understanding going in (longtime RPGer; father was an engineer and I was a computer nerd; father was later a forester and I worked summers in a mill), there remained much to learn. Most tech editing work requires at least a good grounding in Word document formatting, unlike say fiction in which one can get by with saying “I’m the language jockey; formatting is up to someone else.”

How it’s different from, for example, travel editing:

You are less concerned with preserving style than with conforming the ms to a style guide. Most organizations have specific looks, styles, colors, and branding terminology they like to see. You mostly do not, for example, have to explain to sixtysomethings why they can’t use two spaces after a period just because Mrs. Blunthead taught them to type that way in the 1960s. Either the person in charge says one space is required, or mandates two, and either way, the tech editor can make a case but rarely gets to be the decider.

Your content is vertical in that it pertains to some particular field of study: agriculture, marketing, engineering, software. This requires you to drink from the proverbial firehose in order to absorb enough terminology and technical detail that you do not need to ask questions SMEs will find dumb and annoying. So if you’re editing timber industry documents and the term “board feet (Scribner)” means nothing to you, you must change that–your level of understanding, that is, not the meaning.

Rush jobs are very much the norm. People who write manuals, papers, analyses, and so forth usually take more time then they expected. Where is the shortfall made up? On the computer of the person with the red pen. What this means is that you will not always be able to make this a work of sweet perfection, and you must make sure the au (as we refer to the author when she’s not looking) knows this and has reasonable expectations. It will sometimes boil down to: “Look. You have given me three hours and there are eighty pages here, with captions, footnotes, graphics, and so on. That’s not long enough to do it right, but I will give you the best three hours I’ve got.” If the au doesn’t like that, then she needs to get it to you sooner.

There’s a lot of opportunity and retention. Tech editing clients are less concerned with price (they are typically billing the work to a client) and more with excellence and alacrity. Think about it. Suppose you run a demolition consulting firm. Companies commission you to tell them the best way to blow up stuff with the least impact on the surrounding area, best recovery/disposal outlook, and so on. You know secrets and they fuel your business. Your work product is the report and its supporting data. You can make it good, but you find an editor who can make it “wow”–and will, at need, make your report her priority. You love the new level of professionalism in the impression your product makes. You do not want to lose that editor. You do not want to try your luck with a new one, see how well they learn your business terms, or go without. You’re going to make sure you pay your editor. The cost is tiny relative to the benefit. You would be a ninny to do without that editor, or her equivalent, once you’ve had a taste of the good stuff.

What kind of editor can be a tech editor? I find it’s mostly the same properties as make a good editor of other material, but with an emphasis on adapting. Eloquence is less important than communication flow. You aren’t asking whether readers will like this story arc; you’re asking who your audience is and how to help your au convey information as concisely and professionally as can be done. You can’t go on anti-adverb and anti-passive voice crusades because technical writing often creates situations where the surgery is worse than the injury, if you will. Your reader will be in one of two categories: She either knows what makes good English (rare), or she does not (the norm). If the former, she will see that you could not recast those passives because there was no non-cumbersome way to come up with a subject to perform the action. If the latter, she just knows it reads real smooth and the au gets props for clear information delivery. You win either way.

It’s a useful skill to build, because some types of non-fiction mss involve tech editing skills. Textbook editing is a perfect example, its vertical market being very specific to a discipline and audience type. There will be descriptive paras to check for common writing flaws, but there will also be examples to check; sidenotes to review; ever the question of clarity. Will our audience understand the au here? The au engages you because she thinks you can make her book better. You adapt your work to what will serve that end.

Editorial Maverick: action scenes

Why are action scenes so hard to write?

It might not seem that way when you see the material in published form, but it is quite probable that most of what you’re seeing was once an action salad. I doubt that any two editors help fix such situations in the same way.

Far as I can tell, the most common problem with action scenes is over-familiarity on the author’s part. Think of this: You have been working on a fiction novel for five years. Within the first quarter of the ms, there is a complicated fight scene that starts two new story arcs. You have played this scene out in your mind two dozen times as you have gone over and over your ms. You know what “happened.” You have known it so long you can no longer imagine not knowing it.

Your reader doesn’t know any of it until you tell her. How big was the room? Your first gut response might be: “Uhhhh…big enough for the action.” You probably wouldn’t go with that answer, but it is probably the truest one. Your reader has to be told that, especially if the space constrains the action. She must be told everything that is pertinent–but not too much, because…

The next most common problem is over-description. Too much detail: The living room had old-school 1960s tongue-and-groove paneling with a ceiling fan, a brown leather sofa, two leather recliners, a fireplace, and two lamps on end tables. Could any of those details possibly help your reader through the action? Possibly the fireplace, especially if someone grabs the poker. The fan? Sure, if it constrains the action. The other furniture? Minimally, if it too constrains the action. The sofa’s upholstering probably doesn’t affect the outcome; the fact of a sofa might. Does every stroke and feint and hit matter? No, and trying to include all of them makes excruciating reading. This is overcorrection, and it is much easier to fix than omitted essential details. We can always whittle it down to the basics, a few short descriptive strokes that are just enough to help our reader through fast-paced suspense and action.

She likes that, and we want her to have it. Let’s not forget to think of her. She bought the book! Bless her with a mighty blessing! We begin by thinking of her as wonderful, a customer we very much wish to satisfy. We don’t want her bogged down in detail or confused by events. We want to help her. If she puts the book down in frustration, we lose.

There is a third problem: unrealistic action. Take for example a combat situation involving multiple troop movements and weapon types. Some authors have actually been part of troop movements in battle; most haven’t and are glad of it. Fine. How do we sort this all out so it comes out reading plausible?

When in doubt, I make a miniature wargame. I rough out a map, sketch in some basic rules, and borrow counters (small square cardboard pieces from my wargame library). I designate who is what and how many, decide which side initiates the action, and start walking through the battle. Some are easier. If it’s WWII, for example, my old Avalon Hill Squad Leader game is my friend because I won’t even have to make up rules or use my imagination regarding what the counters represent. I’ve drawn a scene on graph paper and used pennies and nickels for the opposing sides, with different dates to designate that this is Joe, this is Lakeisha, this is José; these others are the thugs, and the 1969 nickel is the one with the pistol; everyone else on that side has a switchblade. Anyone who has ever played role-playing games is well equipped to sketch out a game of an encounter and walk the characters through it. Anyone who has not probably knows someone who has.

Yes, they’re hard to write. They are also hard to edit, but the editing is easier than the guidance. The hardest part is conveying to someone whose brain contains indelible footage of “how it happened” which parts are implausible, which are incomprehensible, and which are illogical (a polite way of saying the character isn’t dumb enough to do what the author has them doing). I came up with another tactic, which I call the readercam.

Put your reader in the room, invisible and non-corporeal; Nothing can interact with her, and she stands in the corner with a ringside view. Now put a video camera on her shoulder and see the action through it. What’s visible through the readercam? Of that which is visible, describe what is germane. Use the readercam to define her perspective and field of vision. When need be, change the camera’s aim. This does not mean adding exhaustive detail of a new wall, for example, but it might mean that new obstacles come into play. If they were already described, those bits of description now pay their way. You see the principle, which is that you focus on what affects the action and you don’t move the vantage without some good reason.

And yet you don’t want to over-describe for one more reason: You will be taking your reader’s fun away. She doesn’t want you to tell her every little detail; she wants to tell the story as her mind sees it. How she does that is purely her choice and business, and you’re there to help her but not do it for her. Your work is not to tell her every detail. It is to give her enough roughed-in information to let her mind animate the action in a plausible and exciting way. This is why authors often won’t clarify the way character names should be pronounced. The pronunciation  likely won’t change events; why not let your reader say it however she likes? Is it LEGG-oh-lass or le-GO-less in Tolkien? Who gives a rip? How the reader pronounces the author’s names is none of the author’s business.

The author has more pressing business, such as writing a decent action scene. If you’re the reader, and you just read a banging action scene that had you in suspense while making you want more, more, more, that scene probably didn’t spring into its current form on first draft. Unless done by an author with a natural intuitive gift, it probably didn’t gel on the fourth or fifth. And the long the ms took, the farther away from novelty went the author’s mind. In time, he forgot not knowing.

If he had a competent editor, of course, that got fixed.

Blogging freelance editing, writing, and life in general. You can also Like my Facebook page for more frequent updates: J.K. Kelley, Editor.