The Ending Should Oppose the Beginning

In episode 44 of Scriptnotes (transcript), John August and Craig Mazin talked about how the ending of a movie should relate to the beginning. One thing Mazin said made this clear:

… if you’re writing and you don’t know how the movie ends, you’re writing the wrong beginning. Because to me, the whole point of the beginning is to be somehow poetically opposite the end. That’s the point. If you don’t know what you’re opposing here, I’m not really sure how you know what you’re supposed to be writing at all.

In my post about The James Bond Opening to a software demo, I recommended starting with something exciting about how another customer is getting value. This should be short and sweet and gets the prospect to lean forward.

But next, talk about the problems the prospect is having right now, which you learned about in discovery. Remind them of this as you start their story—the one you are about to tell, which will take them from their life now to a new life after they buy your software. By the end of the demo they should be convinced to take the next step.

If you want to learn how to tell stories like this, I recommend learning how screenwriters do it. Scriptnotes is a great place to do that. They know how to tell a story where a protagonist makes a decision that inevitably leads them to a changed life. This is like the story you want your prospect to feel they are in.

Write While True Episode 30: Finding Nouns and Verbs

Every book on writing tells you to avoid adverbs (and even adjectives). I find that hard to do in first drafts, but I do try to remove them in edits. You can tell that I haven’t done enough editing if you see that I “really like” something or that a new programming language is “pretty good”.

Season 3

Books

Sweep Editing

Transcript

Sweep Edit for Adverbs

I use Joanna Wiebe’s technique of editing in sweeps, which means that I edit written work in multiple 2-pass sweeps that each address one problem. In each first pass, I highlight the text that I should fix in this sweep, and then I do a second pass to fix them. This is in contrast to fixing different problems in a single read-through of the work.

For example, right after I finish a first draft of a blog post, I do a sweep edit to make the piece about one specific message to one kind of audience. I highlight anything that isn’t part of that message, and then I go through those parts and either remove them or make sure they are short enough to not distract the reader. While I am doing this, I am not fixing grammar or tone because I will do that later—each sweep is focussed.

After reading Writing Down the Bones, I finally have a better way to make my writing use fewer adverbs and adjectives. I have always tried to find and remove adverbs, but now I also find better nouns and verbs for the sentence I just edited. This lets me gorge on as many adverbs and adjectives as I want in the first draft, because I can trust myself to fix them later.

The extra adjectives and adverbs actually help me. They are a wordy description of the better noun and verb for that sentence. I can use Goldberg’s noun and verb game or a thesaurus to find them.

I’ll be elaborating on this in tomorrow’s episode of the Write While True podcast.

Writing Down the Bones is a Playable Book

After I wrote yesterday’s review of Writing Down the Bones by Natalie Goldberg, I went to my copies of The Golden Book on Writing [amazon affiliate link] and The Elements of Style [amazon affiliate link] to find out what they had to say about verbs.

As expected, they also recommend that you avoid adverbs and pick out more specific verbs. I’ve heard this advice many times and all it has resulted in is that I remove most “very”, “really” and “pretty” intensifiers before I publish. I don’t take the second step, which should have been to find better nouns and verbs. This leaves my sentences imprecise and boring. The advice failed me because it didn’t come with any instructions. They just dropped a few examples and figured you’d get the idea.

Natalie Goldberg uses one sentence to say that you should use better verbs and then spends the next few pages showing you exactly how to do that. She gives you an exercise that will train you to think up more precise verbs. More importantly, it’s kind of fun. Like a game.

It’s play.

Review: Writing Down the Bones

My memories of reading Writing Down the Bones [amazon affiliate link] will always be tied to the beach. I read the book over several mornings on the Gulf Coast of Sarasota. It was early enough in the morning to beat the Florida-in-August heat, but late enough to let the truck rake the sand at the shoreline. I walked to the edge of the water, put my chair in the sand with my back to the sunrise, and settled in to read the wisdom of Natalie Goldberg. When I had about 50 pages left and didn’t have enough time to go out, I put my AirPods in and played some ocean sounds while I finished it.

Writing Down the Bones is a book about writing. It’s also a book about meditation. And, like many writing books, it’s a memoir. The three themes are intertwined in short, practical chapters that will get you writing.

It was written around the same time as Julia Cameron’s The Artist’s Way, more than 30 years ago. Like Cameron, Goldberg recommends that you “practice” writing. Her timed writing exercise is a lot like Cameron’s morning pages, and since Cameron wrote a foreword for this book, I’ve imagined them as lifelong friends and cross-influencers.

The main difference in their daily practice is that Goldberg recommends that the writing be directed. Like Goldberg, I have come to the conclusion that I should try to guide my pages a little more. She has a chapter with some suggested prompts. My favorite is to start with “I remember” and then just write what comes to mind. Whenever you get stuck, just repeat “I remember” and start again. I have used this idea often since I read it.

Goldberg uses the name “writing practice” for her timed writing exercise to evoke the “practice” of meditation. She draws comparisons between writing and meditation throughout the book. A through line of work is her accepting her guru’s attempts to convince her that writing was meditation. She is a much more serious practitioner than I am, but I have meditated regularly for more than five years, so these comparisons made sense to me. I consider my morning pages a kind-of meditation.

Another chapter, “The Action of a Sentence,” is a practical way to find good verbs. First she lists 10 random nouns. Then, she picks a vocation (in this case a Chef) and lists all the verb associated with it (chop, mince, slice, cut, taste, etc). Then she matches a noun, a verb and completes the thought. As a poet, these serendipitous combinations might go right into her work. For me, just expanding the list of verbs in my mind makes it possible to avoid adverbs and make verbs exert themselves to describe the scene.

I reread books like this every so often, so I am sure I’ll read it again in a few years. But, right now, I’m going through the book again and trying to figure out how I will keep it fresh in my mind as I continue to write. I was too enthralled to take good notes the first time.

Perhaps it’s a book I just need to consult more often. Pulling it off the shelf when I need a boost. Or maybe it will be my perennial beach read—with me when the waves remind me to flip through it again.

The James Bond Opening

I am building software to help onboard sales team new hires by helping them get to demo proficiency fast (if you are interested, here’s a 3 minute video of the DemoWizard).

One of the things we help our clients with is writing a compelling opening. My partner, Brian, calls this a “James Bond” opening. I’m not a salesperson, but I gave a ton of demos at Droplets and Atalasoft (both made developer tools)—I wish Brian had told me this back then, because I love this kind of opening.

Here’s how I try to explain it:

The beginning of a James Bond movie is actually the end of the previous (unmade) movie. We don’t know anything about the back-story of that movie, but now we get to watch the most exciting 10 minutes of it until it ends. Then, we start the next movie—the one we came to see. We know that at some point we’ll see an ending that topped the one we just saw, so we lean forward in anticipation.

For you, the opening is your best customer success story, but just the end. That customer already have a completely set up system, and they are already getting value from it. Start your demo by showing the part of the software that delivers that value and share their results (with permission of course).

Now that you have their attention, you can start your prospect’s story and help them understand how they will get from where they are now to an ending like the one they just saw.

Typing Out Art

I already wrote about how my typing teacher, Mrs. Cohen, was a genius for telling us (in 1983) that we needed to learn how to type to work with computers. Another thing she did was have us make pictures by typing. She’d read out of a book with instructions: “10 spaces”, “2 semi colons”, “30 periods”, “4 dollar signs”, etc, etc. It would take the whole class and then we’d get a picture of JFK.

This came to mind yesterday after I started a new meetup group for Sarasota Software Developers, and I had to come up with a banner image for the page. I was just going to use a photo of a sunrise with some palm trees, which definitely reads as “Sarasota”, but I also wanted it have some element of “Software Developer” in it. I was going to composite something together, but then I thought that someone must have made some kind of ASCII art generator. I was right.

I tried a bunch, and this one is the best: https://www.ascii-art-generator.org

Here’s what I made with it:

Green on black ASCII Art of palm trees at Benderson in Sarasota

It would have taken forever to type it out.

Don’t do Nothing and Be the Change You Seek

When I worked at Atlassian, we had five company values. The one that is most applicable to me outside of Atlassian is “Be the change you seek”. Even at Atlassian, in our slack, I probably reacted with our custom “Be the change” emoji annoyingly often. But, it wasn’t ironically—I loved that we (as a company and team) embraced the changes that people went out of their way to try to make. Co-CEO Scott Farquhar often started company Town Halls by telling new hires that they were hired to change Atlassian.

Before we were acquired, at Trello, we had a similar value we called “Don’t do Nothing”. It’s not exactly the same. “Be the change you seek” says that you should work hard to fix broken things you care about. “Don’t Do Nothing” was asking you to take a proportionate action to the problem, but not “nothing”—this could just be reporting it.

They both functioned in the same way with regards to who was responsible for improving the company—you were.

Write While True Episode 29: Loose Sentences

Last week, I spoke about something very fundamental—how to write complex sentences, and I’m going to continue along in that theme for what I’m now calling season three, drawing lessons from some of what I consider the greatest books about writing, and picking out ideas related to using words, sentences, and paragraphs. These are things that I’ve found that I need to work on, and I hope that that can help you too.

Transcript

Congratulations Rich Hickey

Rich Hickey, creator of Clojure, has announced his retirement from commercial software development. It looks like he’ll be still active in clojure development, but as an independent developer.

I met Rich in the 90’s when I took his Advanced C++ continuing education course at NYU. I was running a C development team, and we were adopting C++, so a few of us took the class. The most memorable part was the last few sessions where he described a GUI object-oriented design built around a dynamic object system (ala Self or Javascript) using his functor library.

The next 15 years of my career were dominated by C++ where my code was heavily influenced by what I learned in this class.

In 2007, when I saw his presentation at the NYC Lisp group, I reached out to see if he wanted to present to the Western MA Developer Group. Since Clojure was still relatively new, he was willing to come to present to us.

We had about 30-40 people there. One of our members, Chas Emerick, hosted the event. He went on to be a prolific contributor to the clojure ecosystem and co-author of O’Reilly’s Clojure Programming [amazon affiliate link] book.

I helped promote the event by writing my 20 Days of Clojure series. For the time, that was a lot of clojure content.

He came in March 2008 and blew the doors off with an elegant, concurrency-safe ant simulation:

Here is my original write-up of the meeting.

I still keep in touch with many of the developers that were there that day and we still talk about it. I can see the influence in their work.

The most important clojure code I wrote was the code I used to apply to FogCreek/Trello. They gated their application with a programming question, and I answered it in clojure because it looked like I would need something like a BigInteger in my answer, and clojure makes that easy. I also knew that the FogCreek/Trello team liked functional programming.

We might not all have adopted clojure (we opted for F# at Atalasoft and one of our engineers went on to become a Microsoft F# MVP), but our career trajectories were changed by that day when Rich opened our minds to what was possible with modern functional programming.

Thank you Rich and congratulations.