Book 3, 2.5 Chapters in, all AI-Augmented. My current process.

Previous to using Sudowrite, my process went something like this: Dictate chapter. While dictating, I might make use of MasterWriter, a personal database of books in DocFetcherPro, or various thesaurus and prose helper books if I got stuck. Come back the following day and edit chapter. This usually resulted in adding about a thousand words. My dictating tended to focus on minimal action and dialog to sketch out the full chapter beats. The following day I would add the nuance, humor, and descriptors, as well as tighten up the dialog. Post edited chapter to my beta readers and let them tear it apart. Come back in a few days and incorporate their suggestions or correct any typos they may have found. At the end, the whole book goes to an editor, natch. I am a very linear writer. I write one scene after another, one chapter after another, and I deal with each scene before going on to another one. It’s very rare that I go back into a finished scene or chapter to add anything other than red herrings or stronger indicators for the mystery if I think the reader may not have enough to play along and figure it out. This book, which is Magic’s a Hoot, is going something like this: I start most scenes by spinning up something from “Expand” in Sudowrite, which is experimental. (Expands a summary into a scene. This is useful if you know what happens in a scene, but are having trouble rendering concrete beats and details.) The AI is (as experimental features can be) hit or miss. I find the simpler the summary is, the better the AI tends to do. It does, though, get drunk and lose touch with reality at some point, and the whole thing turns into a word salad. At times, though, what it gives me is remarkably on point. I take from this what I can, and flesh it out. From here, I usually take small pieces and feed them back to sudowrite as I make it my own, and then run “Wormhole” on the smaller section. (Wormhole: Given a passage of text, Wormhole generates possibilities for what to write next.) Lather, rinse, and repeat step 2 until I get to the end of the chapter. I let the chapter rest a day and then come back and do my normal steps 2 through 4 with the exception that I may refer back to Sudowrite for “Describe”. (Highlight a word or phrase and Description will suggest a few ways to describe it. Description works best when highlighting a short phrase within a paragraph. But it can also work at the paragraph level if you want it to suggest descriptions for a broader set of objects in your scene.) I have given my first chapter to my beta readers. They did not seem to notice any difference in the writing style. They didn’t comment on anything being different, odd, clunky, weird, not funny anymore. Nada. I expected …

Continue reading…

Where the AI ethics began to get murky.

So, a few days ago I said this: Did I feel like a computer was writing my book? Not remotely. It wrote words, but they weren't MY words-my tone, my voice, my vocab, my cadence. It was like a menu, and I chose what I wanted. Then lobbed ketchup all over it to make it my own. — Leanne Leeds 🦉⭐🧙‍♀️ (@LeanneLLeeds) June 3, 2021 And I think I spoke too soon. I finished Owl’s Fair yesterday, and on a lark, I decided to play with Sudowrite. Could the AI, I wonder, actually write? What could it give me to start? Sudowrite has an experimental lab with the following directions. “Write a scene summary (less than 100 words) in the Editor, highlight it, and click the Expand button. A good summary succinctly describes the characters, setting, conflict, and how it resolves.” So I did. I delete the documents as I finish my scenes, but I provided it with something like “This scene is written in the first person from Astra’s perspective. Astra Arden, a witch, and Emma Sullivan, a police detective, are looking for a stolen necklace in a park. Astra finds it.” Or something equally as simple and benign. You can see a smidge of it below. I hit the button and let the AI do its thing. On the left is my initial cursory editing of the scene based on what the AI (right) gave me. It was far better than I suspected it would be, but it fell short of being able to literally map out a whole scene. So, I went at it a different way—I described the beats and exchanges in the scene and spun up sections. As I got what I wanted, I edited and placed edited sections into wormhole (which is not experimental and seems a bit less hit or miss) to spin up a bit more. Though halting at first, by the end of the afternoon, I had a full chapter of Magic’s a Hoot primarily utilizing this back and forth. The bones of it had been generated by the AI. Everything started with the AI. All of it. Like I said—it started out as an experiment. Just something to do on a Friday afternoon, just playing around with a new tool. And yet, reading it…it was a perfectly good chapter. I edited, shaded, changed…nothing seemed out of place. It’s like the AI provided an outline, a scaffolding to sculpt on, and I took it and carved and colored the nuance. But I will admit to you, I paused, stared, and felt vaguely unnerved by it. I never intended, when I got the tool, to use it in this manner. And yet I had, and I had a 3500-word head start on a book I needed to write. I’d also doubled my production—I write a chapter a day. Yesterday, I “wrote” two. (Ironically, my strength tends to be editing—it’s the part I find fun, where the colors and subtlety really get sussed …

Continue reading…

Initial Sudowrite Observational Tweets

Initially, I’d planned just to tweet about my AI-Augmented Author experience, but a few days in I was struggling with questions that needed far more than a tweet or two. Tweets started this off, though, so I wanted to put them here. Holy crap. @sudowrite is seriously impressive. "Nutmeg’s hair is red, but her bright green eyes show that she has more in common with creatures of the night than with day." Knew she was a pixie, picked up it was night. This is seriously cool. — Leanne Leeds 🦉⭐🧙‍♀️ (@LeanneLLeeds) June 2, 2021 Finishing up Book 2 and played around with #sudowrite last night. Chapter 17's ending got quite a bit better, I think. Definitely involves the human picking, choosing, and polishing up, but it also definitely gave me ideas on the scene I hadn't had. (Spoiler white out.) pic.twitter.com/bSkCOtnwuc — Leanne Leeds 🦉⭐🧙‍♀️ (@LeanneLLeeds) June 2, 2021 So, first dictation chapter (OSW:B2:CH18) with #sudowrite today, and used "Wormhole" 9 times, and "Describe" once. Tomorrow, I edit the chapter. I'm curious if I'll use it more or less during editing or creation. — Leanne Leeds 🦉⭐🧙‍♀️ (@LeanneLLeeds) June 2, 2021 #sudowrite wrote" "Meryl's voice flew like a flock of crows onto Amethyst's head and perched there, half a dozen or so, squawking and uttering a few warning caws." Not my style, but man, I want to use this so bad. — Leanne Leeds 🦉⭐🧙‍♀️ (@LeanneLLeeds) June 3, 2021 Lest you think all I do is sing #sudowrite praises, there are some times where I look at what comes out and wonder if the robot brain's been nipping at the brandy a bit too much. pic.twitter.com/S5dFfuaFA0 — Leanne Leeds 🦉⭐🧙‍♀️ (@LeanneLLeeds) June 3, 2021 Ok, D2 with #sudowrite. Edited Chapter 18, and used Expand 1 time, Wormhole 2 times, and Describe 6 times. Am starting to get a feel for how to get the best results from it. Some things I give more text to, some less. Will write up some observations later. — Leanne Leeds 🦉⭐🧙‍♀️ (@LeanneLLeeds) June 3, 2021 Ok, a few thoughts on my first day with #sudowrite. (A thread.) It was very easy to use while dictating, but I'm used to having two monitors (three, actually, but don't judge me.) I did not write in it, just cut and pasted sections into the app and used whichever button I wanted. — Leanne Leeds 🦉⭐🧙‍♀️ (@LeanneLLeeds) June 3, 2021

Deciding to try Sudowrite

When I write, I utilize two monitors. One is maximized with Scrivener, and the other monitor is my reference monitor. I keep a Calibre library open with writing reference books at the ready like the fabulous ones from https://writershelpingwriters.net/. I also have a copy of DocFetcher Pro that’s indexed the text of a few thousand books I’ve read over the years (thank you, Gutenberg Library & my husband, who never complained how much of our budget went to books) so I can quickly look at examples of how other writers turned a phrase I am stuck on. I’ve just always made copious use of reference materials to try and negate my own ticks, get me unstuck, and polish up my story. Recently, I read The Computers Are Getting Better at Writing by Stephen Marche in the New Yorker, and practically salivated. I wanted that tool. Oh, man, I wanted it—so I applied for the beta and heard…nothing. So I followed the developers and tweeted and heard…nothing. One developer asked for first lines to get AI-created poems, I tossed one out on Twitter and got my poem…but no beta invite. I kid you not. I was a bit miffed. Yeah, okay, I have only a few hundred Twitter followers, but I’m a full-time book writer! Sure, I’m pushing fifty and way out of the “cool LA writer” comfort zone the devs seem to be in, and, sure, cozies aren’t cutting-edge literary masterpieces, but…but… come on!  I was on the verge of writing a heartfelt letter explaining why I would make a GREAT beta tester: Originally, I was in tech, so I’m old, but I’m a little techie. A little. I used to have developers report to me, and they didn’t burn me in effigy because I was a jerk. I know agile is a process and not just a noun. I’ve even used Jira! Did I mention developers from my old job actually still speak to me? No? But on the day I was to write the letter begging, Wordloops hosted a presentation, and everyone who attended would get beta access. Finally. I was in. I’m writing this the day after I got in when my enthusiasm is still high. There’s been very, very little written about authors using this technology—whether that’s because no one is, or no one is willing to admit it? I have no idea. Frankly, I’m not that precious about my own writing that I’m embarrassed to share credit with Skynet. I’m perfectly willing to admit that while the story itself is mine, I utilize whatever legitimate, ethical tools I can to goose productivity, get unstuck, and to move forward. One book every two months is not the easiest thing in the world. So, I’ll be documenting the process on Twitter/posting observations. First, because I barely use my Twitter for anything. Second, because I suspect a lot of people may not want to openly talk about it and someone besides the developer should. Finally, because I’m curious to see …

Continue reading…