Skip to main content

They’re Watching You: How the story began


They’re Watching You is a gay romance about two musicians, Ed and Aleck. Ed is out, and Aleck—who is much more successful—isn’t. This story is about the dynamics in their budding relationship, and also about some external issues they face.

Like a lot of my stories, They’re Watching You started with a real person. I saw an interview with a musician, and something about his character appealed to me. He was shy and didn’t like talking about himself—or anything really—and I found it so endearing that I ‘cast’ him into a story idea.
Or should I say, I had an idea for a story based loosely on my impressions of him. That story begins with the initial meeting between Ed and Aleck, and I knew that the story was primarily about how they met and whether they ended up together.
The character in the book is not the real person or even meant to be a portrayal of that person (which is why I’m not going to say who it is.) Instead, I sort of see it like they’re an actor I used in this story.

I can’t even remember where the idea for the starting point of the story—their first meeting—came from, but once that part was written, the next few chapters almost wrote themselves. The first chapter created the dynamic that drove the next three or four chapters; it was like I’d pushed a ball to the top of a hill, and now I was just watching it roll down.
Unfortunately, once I’d gotten them together, I didn’t know what happened next. Did Ed and Aleck stay together, or did it all fall apart?

For several months I left the story alone, and for much of that time, I thought that the ending would be Ed and Aleck would break up because Aleck didn’t want to be out. The final conclusion—I thought—would be that months later Aleck would be revealed to be in a relationship with another man, leaving Ed to wonder why it hadn’t worked out for them (how could Aleck decide to come out for this other guy, but not for Ed?)
I really didn’t like that ending, even though that was the one I had come up with in my outline, and I think because I didn’t like it I just sat on it. I didn’t want to write that ending.

And then I had an idea for a subplot, and by adding that subplot, I also had an explanation for why Ed and Aleck’s initial meeting had gone so badly wrong. It’s neat when you find something that not only provides an ending, but also fills in a piece of the story that you hadn’t finished.

Once I had those two parts—the beginning, and the subplot—the rest of the story pretty much seemed to just write itself.


Comments

Popular posts from this blog

Grammarly - Inconsistent punctuation fix bug

As I wrote in my previous post ( Grammarly - I think I like it ), I've been using Grammarly to proof my book. I'm still happy with it, but I did discover a problem it has with certain punctuation imported in a Word .docx file. One of Grammarly's features is a fix for 'Inconsistent punctuation.' It was upset that my files (which were .docx files exported from Adobe InDesign ) contained a mix of straight and curly apostrophe and quotation marks. I think the problem is that internally  InDesign fixes these issues in your original text on the fly, but if you export the text it sends out the original formatting rather than changing the punctuation. I figured that making this change in Grammarly was a good idea, but what I discovered is that after doing this, there were instances where single apostrophes and quotation marks were moved, particularly around a 'word' or if I had a single apostrophe next to quotation marks: "And then he shouted 'Fire!&#

Grammarly - I think I like it

I’d seen the ads for Grammarly, a tool that promised to help me “ Compose bold, clear*, mistake-free writing with Grammarly’s AI-powered writing assistant, ” but I was skeptical. Maybe I didn’t want to spend the $139.95 a year it costs (there is also a $29.95 a month option.) [* that sentence came from Grammarly’s website, and Grammarly suggested changing the word clear.] This week I finally tried the free version, just out of curiosity, and after using it I was intrigued enough to get the paid version, a nd though it’s only been a few days, I like it. I’ve been running my book through it, and while we have a lot of disagreements (primarily over Unclear Antecedents), it has found enough spelling errors I had missed, and grammar and punctuation mistakes, to make me feel that it's worth the price. Pros • It finds spelling mistakes and grammar issues that I missed using other tools, and with multiple proof-readings. • It’s easy to use, though performance c

Debugging Amazon Kindle Direct Publishing - Internal Error

I’ve been setting up my next book in Kindle Direct Publishing (KDP.) This is the second book I have published through KDP, and it’s a reasonably straightforward process.   I first uploaded a draft of the book and cover months ago to check that I had the formatting right. This is something I recommend doing; if your text layout goes into the trim area, or has some other problem, the upload will be rejected. You want to make sure your design is right before you finish the layout of your whole book.     Anyway, I just finished the manuscript and went to upload it and the updated cover. When I did, I got an Internal Error for both the cover and the book. That confused me, as I hadn't made significant changes to the formatting. I tried uploading the previous version of the text and cover—the ones that had uploaded successfully some months ago—and got errors on those too!     I tried some different things uploading different versions and managed at one point to get the original cover to