Skip to main content

Why you should write really bad scenes

Most writing guides focus on writing good scenes, getting the conflict and tension in there. A bit of detail to add colour and location, good dialogue. I'm going to put forward the argument for bad scenes - the stuff that gets cut.

The problem with focusing on good scenes and top copy is the moment you write a dull scene, you have a good idea that it should be cut, so you cut. And you start again, which leads to frustration and the feeling that you're getting nowhere. I certainly feel that way. And then I read an article by a YA author who said she had to write nearly half a million words to get one particular novel right. If an average YA novel is 70,000 words then that's 430,000 words not needed.

Does that mean they could be avoided?

Well, it got me thinking to how I wrote Clash and Arabesque. Clash actually started as a very different book, something called Get Even, Get Girl, Get Lost, and the story of Kyle and Alex was really just the opening of the book. It wasn't until I came to rewriting the entire novel that I realised Alex was really interesting and the rest of the book paled compared to those first few scenes. Two thirds were cut right there. About 40,000 words, and nothing of that was reused or reworked. It wasn't particularly bad, just nowhere near as strong.

So I began rewriting to develop those first scenes further. The majority of that first chunk was either rewritten or ditched. I think only two scenes of the original draft survived, and both were developed further and rewritten several times over. It was months before I had enough scenes to take a step back and be able to work on the plot.

I couldn't have planned Clash, and I couldn't have written it straight off. It was a mish-mash of good and bad scenes that were eventually hammered into shape.

Yesterday I wrote a scene for my current project (I'm going to call it Daniel's Daughter from now on, just as a working title so I can refer back to it), As a scene, it's okay. It was fun to write. It's got conflict and tension, it fires off questions for the reader and ends on a cliffhanger. But now that it's written I can't help thinking, 'What if...?' and approach the opening a different way. Over the past year or so, this has stumped me again and again and made me rethink, replan and start over. It's that fear of taking a wrong path that has held me back. It's that fear of writing bad scenes - or at least, unnecessary scenes - that holds back development of new ideas. The result of this is a book with lots of good scenes, but not a lot of development - no depth. I've written some clangers over the past few years!

So maybe writing those bad scenes has its place. I know that yesterday's scene probably won't make the final cut, and today's scene might not either. But I do think that writing them is the springboard to the good stuff.

So for now, the scenes stay, and Daniel's Daughter moves a step forward.


Comments

Popular posts from this blog

Writing on a Chromebook

I've been playing with a budget Chromebook for the past few months and have to say, a Chromebook is a pretty good choice for writing. I'm using an Acer CB314-1H which cost me a whopping £79 (thanks to a £100 cashback deal). It has a bright, crystal clear FHD screen, a fantastic keyboard (much better than my HP laptop) and it is super lightweight. As far as the keyboard goes, on first impressions, it seems that the keyboard has no delete key or CAPS lock, but both are available with help from the ALT key. It also seems that there is no way to turn the Trackpad off. This takes about ten seconds on Google to enable debug shortcuts, but to be honest, even with the option available, I rarely use. I catch my laptop trackpad all of the time, but hardly ever on the Chromebook. The next thing to consider is software. There's Google docs. You can waste time searching the internet for alternatives, but this means enabling Linux and playing about and it's really not worth it. I man...

Rock Music, Stage Diving and a Fire Crew - It's the Clash Launch Party

Thursday 3rd March was one of the craziest nights of my life. Rather than launch the book in a shop or library, I booked a theatre and got local teen rock band, Hell's Marauders , to play. There were a few surprises during the night. The first was the cake Paula had made, with the full clash cover printed on the icing. The second was the fire engine in the car park.The third was being dragged up on stage to sing Anarchy in the UK with the band. I think I might be the first author to do a stage dive at a launch party. The fire crew were there thanks to Nev. Nev gave me some help on a few technical details in the novel. He was on call on Thursday night but wanted to come along, so he turned up in a fire engine with the whole crew. Catnip editor Non Pratt got up to do a truly wonderful introduction, then I jumped up, grabbed the mike and screamed out, "HELLO FATFIELD!" - proper rockstar style! I calmed down enough to do a short talk about YA fiction and a read...

Writing Challenge Day 3 - Back to Scrivener

Sorry Scrivener, all is forgiven. I've actually been using LibreOffice for about a month because I was using for a different project over the holiday period, and generally, everything was fine. But then today, right in the middle of a sprint, it started acting a little weird. I tried to undo a few things only to see it replace chunks of text with error messages. Then it crashed completely. Thing is, this document is less than 5,000 words. That's not a lot for a word processor to handle. And while it autorecovered the file, it's still one too many crashes for me.  Going to back to Scrivener, I suddenly remembered the Session Target tool. This makes life so much easier, as I can see, as I type, my progress. In LibreOffice I'd have to paste the word count into the spreadsheet I'd made.  Project targets window It also displays as a line bar at the top of the project with the Manuscript Target at the top, above the chapter title, and the Session Target below, so there...