Showing posts with label story. Show all posts
Showing posts with label story. Show all posts

Wednesday, May 02, 2018

On Writing 2: Ideas


On the 21st of January, 1990, I had some exciting news. I wrote at the time that it was 'quite exciting.' I'm sure I meant it was really exciting, and it was: a children's story I'd written had been accepted for a very popular New Zealand children's radio programme called Ears, which ran from 1988 to 1996. (Ears was the name of the programme; the story was called When Dad Went Fishing. You can read it here.)

Instead of encouraging me to go on and write more children's stories, I did one of those things writers do and got despondent. I'll never have another idea!we cry. I don't know why this happens; maybe it's a kind of let-down after something good has occurred. Here was what I wrote at the time: 

In regard to children's stories, I need piles of ideas to draw from so that I've got something to work on, and don't feel I have to dredge up something to make it work because I have nothing to back that one idea up. At present I feel really dry when it comes to trying to write something for the kids. I've tried lying in bed at night thinking of something: doesn't seem necessarily to be the most productive place. Last night, I had an idea about a house shift, and the little kid getting lost continually in the middle of it all, and lists of the things that the family were packing as the hours went by, and increasing numbers of people coming to help. But developing something like this is the problem: having the energy to do it. 

Of course it isn't having the 'energy' to do it, it's the getting on and doing it. Procrastination, which I've talked about a number of times on this blog and which I'm sure I'll talk about again more than once in future posts, is the thing that gets writers into such trouble. 

But let's not give procrastination more house room for the moment. Let's talk about ideas. We don't have to 'dredge up' ideas. We have to be aware of ideas that come unbidden, and note them down, even if at that stage they're barely formed. They will often lead to something later. 

Yesterday I came across one of my old music manuscript books in which there are scribblings galore, the beginnings of a number of songs and piano pieces. Some of these sketches (often no more than a couple of bars) sat in their poor naked state for some time before getting their moment of glory, and becoming the start of something big. Often the ideas had started out as nothing more than a bit of twiddling on the piano, or even flightier, a bit of a tune in my head. Seldom do these things stay in that twiddling or flighty stage, or course. They vanish if we don't seize them. 

We should never feel 'dry' about ideas. Trying to 'think up' ideas is a waste of time, especially in bed at night, where, if you actually did have an idea, you'd have to race out of bed, grab a pen and jot it down. In the dark. 

Courtesy of Danny Steaven
What is curious about the extract from my diary above is that in spite of my complaints I then go on to jot down an idea, one that even now I can see the possibilities of. Why didn't I pick up on that at the time? Who knows? 

The basic point is that ideas are everywhere, if we're prepared to keep our eyes and ears open. We
have to be aware that they won't come in a final state: they'll be like a moth or butterfly, barely able to be caught before they're gone. It's good to have a pen handy, or to jot down something on your mobile phone.

The thing not to do is say, Nah, that 'idea' isn't worth pursuing. Ideas are gifts from God - He leaves it up to us to develop them. 



Thursday, December 15, 2016

Spare me from 600-page books

I started off the year with a bit of a bang, aiming to read at least one classic this year. The Brothers Karamazov got the short straw, and while I found there some longish moments in it, when Dostoevsky seemed to go off on some tangent (and I don't mean the Father Zossima passages, which are excellent), I still finished it, because there are many wonderful stretches of writing in it. I don't know how many pages it is, because I read it on Kindle - the paperback version I'd had since I was a teenager was falling to bits, and I didn't think to check the number of pages before I threw it out. Anyway, the print was ridiculously small in that edition - for an older person.

I also read Dickens' Our Mutual Friend during the year. Another whopper, also with many byways included, a number of them tedious, and some of them downright silly. Of all the Dickens books I've read this has to be the one that balances some of his best writing with some of his worst. The satire is often superb (the nouveau riche people, for instance); on the other hand some of it hits you over the head with everything Dickens can find. The love story is all over the shop, as well. However, I still finished it, though there were some skimmed moments.

You can tolerate the length of classic novels because you know they were written for an age when reading was something that people did in the long evenings, an age when there was no TV, movies, radio, Internet. But when people produce 600 page novels these days, there had better be a darn good reason for it.

I do quite a bit of reviewing for our local paper, and I got not one but two 600-page novels to deal with recently. The first was The Nix by Nathan Hill. Honest reviewers have said that it's just too long in spite of its wit and satire. I understand it was originally over a 1000 pages. Thankfully that version wasn't published. But the version that was published tried my patience. I finished it, but only by skimming increasingly as I went along. Hill allows himself so many interruptions and authorial reflections and back stories and side stories and streams of consciousness and I don't know what, that the story, such as it is, almost gets swallowed up by all the malarky going on in the writing. There's no doubt the man can write, but perhaps next time he should commit to producing a couple of hundred pages that are really page-turning; just as a challenge, maybe,..

And then came Under a Pole Star, by Stef Penney, also at 600 pages. I got about 200 pages into this, a book that seemed to be about exploration in the Arctic, and seemed as though it was going to be interesting because of that. But for some reason Penney decided that we should have access to her main characters' sexual lives - at length. In the 200 pages I read, very little of this sexual information was relevant to the story; certainly not in the detail we were given. I'd no sooner skim a bit than they were at it again. The exploration seemed continually to be taking a back seat. I'm assuming her two main characters eventually got together at some point in the book. They didn't look as though they were going to remotely get there when I stopped reading, and handed the book back to the Book Editor.

I'm puzzled why publishers think that books have to be long these days. Even the lightweight romance I've just finished (again, for review) was heading up to 400 pages - at least there were fewer words on each page because there was a lot of dialogue. 300 to 350 pages is a good length for me, if the book isn't a classic that's been around since the 19th century. Obviously editors no longer do the job of cutting out swathes of unnecessary material.

I've just remembered that I also started to read, this year, the 571-page Here I am, by Jonathan Foer, and the 560-page Sport of Kings, by C E Morgan, and didn't finish either of them, for various reasons. How many trees are cut down to provide these tomes?

When I was doing a writing course back in the 80s I was asked to write a short story for an assignment (and it was a short one). And then, in the next assignment, was asked to cut it in half. I thought: impossible! But no, it's never impossible. You just have to be willing to let go of a lot of 'stuff' that really isn't as relevant as you first thought. And it teaches you to be concise as well.

I'm not saying that writers must reduce their novels down to the bare bones, Readers Digest-wise, but surely their editors could persuade them that maybe a 100-150 pages of their 600-page book might be cleared out of the way, so that real story could find its feet?







Friday, November 06, 2015

Begin with images

I don't often repeat posts from one of my blogs to another, but in this case this extract is not only apt for Christians, but also for writers in general. Alan Jacobs, in his book, The Narnian, a biography of C S Lewis as well as an overview of his books, shows how much effective a story is if we start from images rather than 'themes' or theories. 

"Everything began with images," he wrote: "a faun carrying an umbrella, a queen on a sledge, a magnificent lion.  At first there wasn't even anything Christian about them; that element pushed itself in of its own accord."  There was not, he says over and over again, an evangelistic plan in the making of Narnia, no apologetic scheme: "Some people seem to think that I began by asking myself how I could say something about Christianity to children; then fixed on the fairy tale as an instrument; then collected information about child-psychology and decided what age-group I'd write for; then drew up a list of basic Christian truths and hammered out "allegories" to embody them. This is pure moonshine. I couldn't write in that way at all."

Or perhaps he could have, but knows that it would have been a dreadful mistake, a giving over of his imaginative life to the "expository demon." What he has to do instead is trust the images that come into his mind - or, more accurately, trust that he is being formed as a Christian in such a way that the images that come to his mind are authentic ones, ones that lie at, or at least near, the centre of his soul. He can do this only if he rejects not only the market-driven questions of modern authors and publishers ("What do children want?") but even the more morally sound question of the Christian apologist ("What do children need?"): "It is better not to ask the questions at all.  Let the pictures tell you their own moral.  For the moral inherent in them will rise from whatever spiritual roots you have succeeded in striking during the whole course of your life."


This is a terrifying, or liberating, word: liberating in that one need not expose oneself to the sanctimonious drudgery of drawing up lists of Christian truths and hammering out allegories that will meet the desires or needs of children. But terrifying because as those images rise from your mind you discover what you are really made of: you discover whether you are one whose moral and aesthetic responses have been shaped by the Christian narrative or whether you remain a person "without a chest," lacking in true spiritual formation.  Trusting the images, you find out who you are.

Pages 243-4 The Narnian. 

Tuesday, June 09, 2015

How not to plot a story

I know that European filmmakers have long seen themselves as anti-story, anti-plot and the like, and sometimes this has produced some wonderful 'art' movies ('art' here meaning the film successfully does its own thing regardless of the rules of storytelling). More frequently it produces films that meander, that lose the plot at the very moment they should be maintaining the plot and that, as a result, lose their audiences.

Two such movies in the last week: one starring Michael Caine and Cl
émence Poésy in a film set in Paris. The other, also French, is about a girl who wanted to become a great pianist, was foiled, and then takes revenge. More on this later.

There will be spoilers...

The Michael Caine movie is called Mr Morgan's Last Love, though you may also find it listed simply as Last Love. It concerns an American philosophy professor, Matthew Morgan - Caine, with a varying American accent - whose wife died a couple of years ago. He still talks to her, and seems to have been deeply in love with her; in fact he was so in love with her that his two children, now adults, suffered from neglect. Apparently. He spends his days in a lonely state, refusing to learn even the most basic French, and hating any change to his routine.

Of course Pauline (Poésy) comes along. She's a young dance school teacher, and Matthew falls in love with her, but very quietly, almost trying to avoid saying what he's feeling. She accepts him as he is, just as a friend. When he accidentally (?) overdoses on his sleeping tablets and winds up in hospital, his two American children, Miles and Karen, turn up (Justin Kirk and Gillian Anderson - she has a very brief time in the film, regrettably). Miles is perpetually angry - he's the one who's felt most neglected by his father as a child - and furthermore, his own marriage has just gone down the tubes, though he has custody of his young son.

The usual argy bargy ensues, the children claiming that Pauline is a bimbo about to take away everything their father owns - which, of course, is rightfully theirs. (Poésy as a bimbo? Hardly.) So far, all fairly predictable. But then the writer/director, Sandra Nettleback, gets herself into a plot-hole, and never quite makes it out. Don't read further if you want to watch this movie. 

Miles, surprisingly, falls in love with Pauline. Yup. Which totally wipes out Pauline's integrity as a character. Miles and his dad have a reconciliation, which is good, but it's not good in terms of what's just happened. Matthew commits suicide. Sorry? (Incidentally, this film is billed as comedy and drama on IMDB.) This awful crunching of gears comes as a result of the thing being forced into a corner by the writer. Did she think that the story needed a bit of pepping up at the end? Did she write herself into a corner because she didn't know how the Matthew/Pauline relationship could work? Who knows. The movie got made, and it leaves an odd taste in the mouth.

Caine, incidentally, is very good, as are the two main women - Anderson strides all over the place and should have been given a lot more screen time. Perhaps it would have been better to have made her the main third character, instead of the dull and boring Miles. She would have dealt properly to Caine and Poésy's situation. She certainly livens up what is often a quite slow movie.

The other movie is The Page Turner. It's a tale of revenge, a perfectly acceptable genre, even if we do wind up on the side of the one doing the revenge.

The main character of The Page Turner (or La Tourneuse de Pages)  is Mélanie (played with a cold-eyed sweetness by Déborah François). As a child she goes in for an exam in order to enter some music academy. Rather remarkably (from a musician's point of view) she's playing a fairly straightforward piece, one that might get her through a grade in Trinity College exams, but probably wouldn't get her into an academy. She has five examiners. Yup, five. One of them is a famous concert pianist. Ariane - played by Catherine Frot - she begins with arrogance, but later has an increasingly bemused look about her, which may not be surprising, given what her character goes through. Ariane, in an extraordinary piece of plot nonsense, allows another parent into the room while Mélanie is playing, and signs an autograph. It puts Mélanie off. As one reviewer said, 'If something as little as that puts her off, she probably shouldn't be going to the academy anyway.'

Mélanie goes home, shuts up the piano, locks it and never plays again. Hmm. Flash forward a few years and she gets an intern's job in a law firm. Hang on! The lawyer in charge just happens to be the husband of Ariane. Does Mélanie know that when she applies for the job? It's not clear, but she then offers to look after the lawyer's son during the holidays - someone else couldn't do the job. Two coincidences in a row. Okay...passable.

Mélanie recognises Ariane; Ariane never, never, never during the course of the film recognises Mélanie. Nor does Mélanie ever tell her who she is. Consequently Ariane, from now on, presumably wonders why this cold-eyed young woman seems to be doing some very odd things.

Mélanie ingratiates herself into the household: she gets on with the young boy, who also plays piano. She not only offers to turn pages for Ariane at a concert that's coming up, she makes herself indispensable. Ariane has been the victim of a hit and run accident some time before, and is 'fragile' according to her husband. Fragile is putting it mildly. She can barely hold herself together. Furthermore, she starts touching Ariane in what can only be described as in an oddly inappropriate way. Yes, we know what the French are like, but this is a bit over the top. Ariane, at first confused, responds, although it's all low-key.

All goes well at the concert. Okay, you think - because there is a deal of suspense being set up - the next concert will be the one when she doesn't turn the page at the right moment, and laughs maniacally - as an old friend of mine used to say - at her employer's distress. But there isn't a next concert, What were the writers thinking?. Instead there's an audition for an American, presumably a promoter of some sort. No audience, but him, and the agent.

What does Mélanie do? As the audition is about to start she just wanders off somewhere, and can't be found. Ariane makes an absolute hash of playing (even though another page turner is brought in), and the American walks out in disgust. And not surprisingly either: Ariane's playing is ridiculously awful; no career pianist would make such a mess of things however fragile they were. Plainly the director thought if it wasn't obvious to a non-musical audience that Ariane was making mistakes, then the scene wouldn't work.

But the scene doesn't work because the Page Turner isn't there! Surely this was a scene in which Mélanie should have once again done her duty effectively, and built up the tension still further. Instead Ariane, by now somewhat besotted with her, just lets her off with a 'sorry.'  Good grief.  Ariane is super fragile, don't forget.

Where is the big climax in a concert hall full of people, with the will-she-won't-she-turn-the-page scene? The scene where Ariane is ruined for life? It could be done so simply: turning a page at the wrong moment (as anyone who's done it knows) can be seen as an accident. It doesn't have to be deliberate. There's the opportunity in the film for it to be seen as an accident by the concert audience, but deliberate by Mélanie, and yet this scene never happens. 

Instead, a couple of other things that have been set up, things that are secondary to the main revenge plot, work themselves out in the last scene, and Mélanie walks off into the sunrise. (She'd got up early that morning.) Ariane and her family are in a mess, but not one of them knows why this invaluable young girl has done what she's done. HUH?

Yes, I know we can become too used to a plot working out according to the normal lines. But an audience also needs to see logic and suspense building to a certain point - think The Man Who Knew Too Much with Doris Day and James Stewart, where no item of suspense is missing, and where even though the audience knows how it will work out, they\re still kept guessing till the last minute. Audience expectation is a great deal of what makes a suspense movie work. Denis Dercourt (again, a writer/director) builds up the tension well, with several suspicious scenes (the discussion of how to kill a chicken, the boy being nearly drowned but it being taken as a joke) but none of these come to anything. At the end we're left with a plot that picks up all the wrong pieces and leaves behind the vital ingredients.

Why am I making such a fuss? Because my co-writer and I are currently working on a very difficult story, the third children's book we've written in the last couple of years. All the bits of the plot have to fit neatly, or something else will fall apart. We know how difficult and frustrating it is to make a plot work, and yet at the end of the day it's very satisfying for the reader to see things click into place. What's the point of building up the suspense if you're going to let it all dissipate?

Dercourt has the directorial touch to have made a suspenseful movie that would build to a solid climax. Instead he lets himself down with an ill-plotted script. Peter Bradshaw in the Guardian called this film 'a treat for lovers of intelligent cinema.' Plainly I'm not intelligent enough.

Thursday, March 12, 2015

Not The Disenchanted Wizard

Back in November I got myself involved in the NaNoWriMo competition which requires you to write a 50,000 novel in a month. I wrote about doing this at the time, when I was still only some 38345 words ahead. I finished the 50,000 words, but some of them were the scruffiest words you can imagine...which is not surprising if you're trying to write a novel almost from scratch in a month.

I know some people can write quickly and confidently. Some claim that their first draft is the only draft, and usually only needs tidying up. (Stephen King claims this is the way he works: comes back to it after a couple of months and removes all the excess adjectives and adverbs.) Some have a gift for storytelling that just seems to pour out of them, and though those works may have some flaws, they carry the reader along all the same.

My certificate, though the
book's title has now changed
There were some good things in my story, some interesting and fantastical events, and I knew where I wanted to finish up...roughly. But when I'd finished the 50,000 words (which included a lot of notes about what I was writing, which is how I write anyway) I had a big hole between the first two-thirds and the last couple of chapters. In fact, though I tried to write those last chapters, they were awful, because I wasn't sure how the characters had actually got to that point.

So over the last month or so I've been working at the story again, first by going through it and making lots of notes (yup, that's how I work), and then trying to work out some of the problems, and then trying to figure out a structure and then discovering, over and over, that if I did such and such then I'd have to answer the question as to why such and such...if you get my drift.

A few days ago I tried working backwards from those last chapters to try and figure out how things got to that point. Copious notes ensued. Copious notes, and oodles of questions. I'm getting sick of my inner editor asking, But why...? like a nauseating two-year-old that someone's left on your doorstep and you have to look after for the afternoon. (Having been through the two-year-old questioning stage at least five times, it's not a period of life that I find quite so endearing as I once did...)

Anyway, today I feel as though I'm making progress. I'm now in the position of being able to go back to the beginning to sort out the structure again, this time with a lot of the reasons for things happening already in place, instead of being guessed at. Of course there are still questions (Be quiet you nauseating child!) but we're managing to work things out.

As I said in my last post this is a prequel to Grimhilda! the first book in this series of children's stories, and explains, amongst other things, how the Maps came to be the Maps, and who they are (something I thought I knew back in November - I was proved wrong and had to give the original couple their dismissal notices).

The big climax was to have taken place in a different country altogether to the rest of the story. I finally realised late last night that this was just adding to my burdens, and ditched the whole idea, along with copious notes and things copied off the Net. Much more straightforward for the storytelling to keep the thing in one city; it's the third city to appear in these books. The first two were unnamed, but this one has a name, though whether it'll actually appear in the book is another question.

Anyway, at this point I don't have a deadline for finishing the story, but I think once I start writing the next draft, I'll get an idea of how from publishing it'll be. As long as characters don't keep wanting to change their motivations and backstories and refusing to do what they're told.

Monday, January 26, 2015

Goodreads - one thing lacking

I've been involved with Goodreads.com for some time, but I've only really got into it properly in the last year. It seems to be a huge site in terms of people involved, and there's certainly a huge amount of interaction. Plus the Goodreads staff are very helpful and quick off the mark.

Only one thing is lacking, I feel. And that's a way of recording the books you didn't finish in a year. I made a category on my own page for books I'd given up on and ones I'd put aside for the moment, but since Goodreads continues to categorise them as books you're still reading it's a bit confusing.

I keep track separately of the books I read on a file on my computer - have been doing this for nearly a decade in a consistent fashion - and I make a note about the ones I didn't finish with some comments about why I didn't finish them. Sometimes you can get a good way through a book before you abandon it, so there's a degree of effort put into books you don't finally enjoy.

I got Mary Poppins out of the library a couple of days ago, but only got halfway through it before abandoning it. I'd never read this children's book, regarded as a classic, and my interest was piqued after seeing the movie Saving Mr Banks, which is about the making of Mary Poppins into a movie. In the movie, P L Travers (as she called herself - Travers was in fact her father's first name) argues forthrightly for the book to be made into the film she wants to see. It wasn't, but as my wife noted this morning, perhaps her arguing about so many details actually made it a much better film than either she or Disney could have imagined.

But the curious thing I found when reading the book was that the movie is actually a much better work. The book, disappointingly to me, is merely a series of episodes. There's little development of character, no plot, no reason why Mary Poppins comes into the Banks family's life with her random use of magic, and when I looked at the last chapter, nothing seemed to have moved forward.

Now plainly the book is written to be read to children of a fairly young age, and for them plot and characterization isn't quite such an essential. But Disney and co took all the disparate elements and made a movie that has a point, has a degree of plot (Mr Banks comes into his own far more than he does in the book, something that helped Travers deal with her own alcoholic father, it seems) and has much more fully-formed characters. Furthermore the movie is charming, a great musical and only marginally too long: the laughing sequence, where everyone has tea under the ceiling is too extended for me, personally. Julie Andrews is proper and prim, but brings a warmth to the character of Mary Poppins that the book's version definitely lacks. Michael and Jane (the best drawn characters in the book) are adorable, and Mr and Mrs Banks have plenty to do in the story instead of being merely 'parents' as they are in the book. Dick van Dyke's character barely appears in the book - he's only in one chapter. (Travers hated even the idea of van Dyke being in the movie, apparently.) Furthermore he isn't a chimney sweep, but his magical picnic with Mary is one of the highlights of the movie, with the animated penguins, which were supposedly one of the sorest points on Travers' side.

Saving Mr Banks may take Travers and Disney's relationship somewhat fancifully, but it does bring to light not only Travers' unhappy childhood, but also her miserable and self-centred adulthood. As the Wikipedia entry notes: According to her grandchildren, Travers "died loving no one and with no one loving her." A sad line to have in your obituary, particularly when you delighted so many readers for decades, and have managed to live to nearly a hundred. 




Sunday, January 26, 2014

Don't stop too soon

While looking through my Evernote clippings for references to guitars (and there were a distractingly large number of them) I came across this quote by recording artist, John Mayer (who may or may not use a good Telefunken M80 - I only discovered that a Telefunken M80 is a mic a few minutes ago).

“I can’t stress enough how important it is to write bad songs. There’s a lot of people who don’t want to finish songs because they don’t think they’re any good. Well they’re not good enough. Write it! I want you to write me the worst songs you could possible write me because you won’t write bad songs. You’re thinking they’re bad so you don’t have to finish it. That’s what I really think it is. Well it’s all right. Well, how do you know? It’s not done!”
The paragraph's a bit cluttered - it may have been taken down verbatim, of course - but it has a kind of truth in it. You can't write good songs unless you've written bad songs, and even bad songs have to be finished in order to prove for all time that they're too bad to be bothered further with. Over the Christmas/New Year period I wrote three or four, or maybe five songs. At least two of them breezed off the page without looking back and proved their worth from day one. The other three...? Well, they've got potential but they're not quite sorted yet. I could abandon them but that might mean that good material gets dumped because it isn't quite right yet.
Equally, when you write a scene for a play or a novel and say, 'That's so bad I can't even go further with it,' you may not have got to the nut of the thing.  Yup, you may be right about its badness, but more to the point, you'll do two things: you'll have decided on the badness of the scene before you've finished it, which may mean you won't discover something good that's still to come, and, you'll begin to tell yourself I'm not very good, so why should I bother? Once again the internal critic will have got you by the short and curlies and another possible writer may bite the dust.

I can remember trying to write a scene for the musical Grimhilda! We had a rough idea of what the scene had to do within the overall structure of the story, but the characters that were needed just weren't there. I sat and thought about it, and thought about it, and thought about it, and never quite got to starting to write it. (I can procrastinate like nobody's business.) Finally I took my co-writer's advice and just wrote, anything, something, just to get started. The scene took off, characters turned up, and we were away. I haven't gone back to look, but I doubt if that first draft is anything like what was eventually performed on stage. I know however that in the midst of the 'stuff' that the scene eventually came out of there will be some things that stayed, that were the true elements of that particular scene.

I've got a book amongst the innumerable books on writing that I possess by a guy called Peter Elbow. It's entitled, Writing without Teachers.  I don't think I've ever read more than the first chapter, but I keep the book because in that first chapter (or at least very early in the book) he makes the valuable point. When you don't know what to write, just start writing - anything, the most utter drivel on the face of the earth, stuff that you wouldn't let your mother see, stuff you wouldn't give the dog to eat. (This is my paraphrase; it's not what Mr Elbow actually says.)  And this is all you can do. Writing requires you to write. Of course there's thinking to be done, but sometimes that comes after you've started writing. I remember starting a story - I think there were about thirty pages - and realising that two or three vivid characters had turned up out of nowhere, and were determined to stay. Eventually, of course, they were changed and the story was changed and little of that original thirty pages survived, but the fire had been lit and was burning in that stretch of just writing.
Anne Lamott calls this kind of writing shitty first drafts. Yup, that's what they are, but out of the manure grows something that's beautiful and edible. Don't stop too soon.


Monday, December 30, 2013

Anne Tyler

It's a long time since I read The Accidental Tourist, by Anne Tyler - although I had some further dealings with it later when it was used in The Weekend Novelist by Robert Ray, as the basis for writing your own novel. Ray, I think, failed to get to grips with the actual structure of Tyler's novel, which wasn't, to my mind, nearly as straightforward as he made out.

You'd be hard pressed to pin down the way Tyler's books are structured, I think. In reading them you feel as though they just evolve, and that there's very little planning. But I suspect this isn't actually the case. However Tyler plans and writes her books, you always feel as though you're in the presence of someone who knows exactly what they're doing. The books may feel as though they have the randomness of life about them, but in fact they're much more carefully worked out than that.

I've read three of her books in the last couple of months - two this month, in fact. The Beginner's Goodbye, Noah's Compass (which doesn't appear to have a compass in it, though I may have missed it), and just finished yesterday, Back When We Were Grownups. All three have a main character who's having to find him or herself at a certain point in time, sometimes after a crisis, but not necessarily. There may or may not be a 'happy' ending, but there is generally a satisfactory one, though that may not be one that entirely satisfies the reader....even if it satisfies the character in the book. Things in Tyler's books don't always work out in ways that other writers might work them out.

Apart from this thematic use of a character who's lost their way and needs to find how to move forward, Tyler's books excel in detailing daily lives, making the mundane somehow luminous, bringing the ordinary into focus and showing that there's very little that's actually ordinary in this world. She also surrounds her main characters (heroes or heroines would hardly be appropriate for these people, though they do have a kind of heroism about them) with a wonderful array of family members, and occasionally with friends as well. Family is big in the Tyler world; they may not be likeable people always, but they're fully there. Back When We Were Grownups begins with a chaotic family picnic in which Tyler manages, somehow, to distinguish three stepdaughters and a daughter, their various husbands or partners, and their various children, and an aged uncle, and not lose the reader in the slightest. It helps that many of them are known by peculiar nicknames. Later on we have aunts, uncles, former lovers and husbands and more. There is a wonderful range of characters here.

It's intriguing, that as a woman writer, Tyler so often allows her female characters to be bitchy and sour, particularly those who are daughters (or stepdaughters) of the main character. These women seem to have a kind of dissatisfaction around their lives, in spite of the fact that they're well off, they have good children, and husbands who care about them.  Tyler never tells us what their problem is; she just allows these women (and they appear in all three of the books I've just read) to reveal themselves as self-centred even while they're supposedly caring about the main character.  It seems to be the women in the child-rearing generation who are most like this; the main characters sometimes have a sister or two who aren't quite so up themselves. One of those even marries the builder who rebuilds part of the main character's house in The Beginner's Goodbye.

And that's another thing: builders, electricians, plumbers and other tradesmen have real lives in these stories. Though the main characters are often a professional cut above these people, they connect with them, and often seem to be the people to whom the tradesmen will open up their lives. I think that's unusual in many modern novels, where tradesmen, if they appear, tend to be very much relegated to the periphery. 

Then there are the children: while the vast array of children in Back When We Were Grownups tend to morph a little when seen en masse, many of them have enough scenes on their own or with a sibling or cousin to give them their own presence in the story.  And there is often an isolated child who is difficult to coax out of his shell: Noah, in Noah's Compass, is one such, or Peter in Back When We Were Grownups, who turns out to be very intelligent, and not at all the problem that his stepmother makes him out to be - she's one of the selfish generation, of course.

I've got two more books by Tyler from the library at the moment; the librarian brought them up from the stack along with the one I'd asked for, and I thought I might as well have them all. I'll be interested to see how they compare to the four I've read.


Friday, September 06, 2013

Atonement

We watched the movie, Atonement, two or three years ago, but I'd never read the book.  I thought the movie was very well done, and its surprise ending came as quite a shock. Don't read this next bit if you haven't seen the movie or read the book: it'll spoil it. But it turns out that the book we've been reading is, to all intents and purposes, the creation of one of the characters within the story; at the end she not only reveals this but also tells us how she changed the events to make them more palatable to the reader, and also to atone for her behaviour as a 13-year-old, when she all but destroyed the lives of her sister and her sister's lover.

While we were in Auckland, I discovered the book of Atonement on our friend's shelf, and began to read it, bringing it home with me to finish.  Knowing how the story played out and how it ended perhaps spoiled it to a degree for me, but the book was still well worth reading. Ian McEwan writes so wonderfully throughout that you turn page after page even after the main story has ended - about two-thirds of the way through - and the three kind of follow-up episodes take place. Structurally, you might say that the first two-thirds of the book is strongly plotted and the other three sections are quite discursive, although the last section ties up some loose ends. The long sequence when Robbie is heading towards Dunkirk with two other soldiers is gripping only because of the detail; there's little forward movement, in a sense. Briony's story of being a probationer-nurse is equally enthralling, but again, until the very end, doesn't move things forward much, except to give us a hint that what we're reading may be not quite what we think it is.  Briony gets the last word, in the last section, where she reveals what the book has been about. By this time a number of the characters have died (either of old age, or accident) and the party for Briony's birthday includes the long-lost play that she wrote as a child, and which was to have been performed on the fateful day that takes up so much of the first part of the book.

The first part of the book is impressionistic, full of wonderful portrayed detail, superbly delineated characterisations, and much more. Yet in spite of its impressionistic feel, this is where the nitty-gritty of the novel takes place.  There is much more grit and graphic detail in section two and three, but in the end they don't seem to add much to the story, although they create a dark and fearsome world where people are dying horrible deaths as a result of the War.  It's interesting that though the Dunkirk sequence was given quite a bit of room in the movie, Briony's time as a trainee nurse was reduced considerably, and the last sequence, in which - as an old woman - she reveals what truly went on, is given only a few minutes of screen time, but more than enough to bring the movie to a satisfactory conclusion.  Dramatically, the movie makes a very good fist of the book.  Its only indulgence is the long tracking shot of the beach near Dunkirk, an extraordinary piece of filmmaking, but not actually relevant to the story.

I've never read any of McEwan before, and since this book is touted as his masterpiece, I'm not sure what I'd read else that wouldn't come across as a lesser book.  No doubt there are excellent things in his other books...time will tell.

Friday, July 26, 2013

Recent books

I've had a rash of finishing books in the last week or so; here's the list:
Orthodoxy – (re-read, on Kindle) – G K Chesterton – 18.7.13
The Unlikely Pilgrimage of Harold Fry - Rachel Joyce – 19.7.13
Into the Woods – John Yorke – 24.7.13
Being a Christian – Helmut Thielicke – 25.7.13
Leadership and Self-Deception (on Kindle)– Arbinger Institute – 26.7.13

As noted, I'd read Orthodoxy before, but basically I remembered almost nothing of it, so I guess it's several decades since I first worked my way through it.  It was nothing like I expected, except that being a book by Chesterton it was full of wonderful inventiveness, delightful arguments against godlessness, and marvellous debunking of people who were his contemporaries.  It makes you long for a 'Chesterton' for the 21st century.  Unfortunately, he was one of a kind.  I highlighted so much of the book on Kindle that Amazon couldn't cope and hasn't recorded many of the later ones.  At least my copy on the PC and the Kindle copy, and the iPad copy, all synched, show all of the highlightings.  I just can't access the unrecorded ones via ClippingsConverter, or Kindle online.

Here's just one longer example of Chesterton in full flight (and he's only just getting started at this point):

I do not see how this book can avoid being egotistical; and I do not quite see (to tell the truth) how it can avoid being dull. Dullness will, however, free me from the charge which I most lament; the charge of being flippant. Mere light sophistry is the thing that I happen to despise most of all things, and it is perhaps a wholesome fact that this is the thing of which I am generally accused. I know nothing so contemptible as a mere paradox; a mere ingenious defence of the indefensible. If it were true (as has been said) that Mr. Bernard Shaw lived upon paradox, then he ought to be a mere common millionaire; for a man of his mental activity could invent a sophistry every six minutes. It is as easy as lying; because it is lying. The truth is, of course, that Mr. Shaw is cruelly hampered by the fact that he cannot tell any lie unless he thinks it is the truth. I find myself under the same intolerable bondage. I never in my life said anything merely because I thought it funny; though, of course, I have had ordinary human vain-glory, and may have thought it funny because I had said it. It is one thing to describe an interview with a gorgon or a griffin, a creature who does not exist. It is another thing to discover that the rhinoceros does exist and then take pleasure in the fact that he looks as if he didn't. One searches for truth, but it may be that one pursues instinctively the more extraordinary truths.

And a much shorter one, what might be called a Chesterton one-liner:

Certain new theologians dispute original sin, which is the only part of Christian theology which can really be proved.


I've already written about Rachel Joyce's book in another post, so I won't elaborate further on it here. 

Into the Woods, which is subtitled a five act journey into story, has a blurb on the back from scriptwriter, Jimmy McGovern, along the lines of 'when I first saw this book I thought, not another book on scriptwriting.'  McGovern goes on to commend the book however, and overall, I would too.  I think its great feature is using examples from movies and TV shows we've all seen, though some of them it overuses (Thelma and Louise, in particular), and there is some other repetition which felt as though he'd run out of pertinent examples.  Yorke is good at insisting that the underlying structure (or the purposeful attempt to go against that structure) of virtually all stories has been around as long as good stories have; it's almost something we can't avoid if we want to make a good story.  Of course it's often used badly, and unimaginatively, but the essential structure also makes its presence felt in the best movies, TV and books.  If that structure is missing, or if the writer doesn't appear to be aware of it, the creation, in general, fails. Certainly the viewer or reader is aware that something is not quite right with the work. Yorke offers some argument against his own thesis, but manages still to say that even those who rail against the structure tend to use it unconsciously, and lays out the way in which they've done so: Being John Malkovich, for example, turns out to be 'properly' structured, even though its creator Charlie Kaufman claims it's not!

I picked up Helmut Thielicke's book earlier this year and have been reading it a chapter at a time when so inclined.  I don't know that it's his best book, by any means, but as always with Thielicke there's some good stuff in it.



Leadership and Self-Deception is a bit of a phenomenon, apparently.  I was alerted to it by a colleague who said that it could be useful for reading in relation to the pastoral supervision work I do.  Seemingly it's used in big and small companies around the world as a way of helping staff to work together for 'results' and good relationships rather than destroying each other.  But I found it's also useful in terms of thinking about my own relationships with other people, and I've been particularly reflecting on a work relationship I had a few years back that seemed to sour when it shouldn't have.  It gets to grips with blame, and self-justification.

It's written as 'fiction' though what that actually means is that the theory behind the 'getting out of the box' thesis is written out in dialogue form with three or four fairly cardboard characters instead of being presented as straight non-fiction.  The narrator comes across reasonably well as a 'person', but those teaching him are a bit bland in terms of personality.  Nevertheless, the material itself is of value, and, if taken on board, would certainly be of help within a family or a firm. It boils down, in essence, to do unto others as you would wish to them do unto you, and it's perhaps not surprising, when you go and investigate who the Arbinger Institute actually is, that the man who initiated the ideas in the book and its subsequent self-perpetuating life, C. Terry Warner, is a Mormon. His books in general, though listed as self-help, come out of a stream that uses Christian underpinnings to show people how to live (without necessarily having to become Christians).  

Monday, May 13, 2013

Little Red Riding Who?

It occurs to me that Little Red Riding Hood is an odd name to give anyone. In fact, it's not a name at all, it's a description, and worse, it's not a description of a person, but an article of clothing.  In which case, why, when we say Little Red Riding Hood, do we immediately think of some anonymous little girl rather than something to wear? How did she get to be called that?  Did her parents go in for the modern fad of oddball children's names?

Yet, in spite of being called after an article of clothing, there's a famous fairy-tale about her in which a wolf wants to eat the child, puts off eating her until he's eaten her grandmother as an appetiser, and then, just when everything seems to be going his way, is chopped open by some woodcutter - in front of the child's eyes.  Extraordinary.  Exceptionally Freudian.

How did a story with such an odd name come to be so popular?

We'd be unlikely to read - let alone buy - a children's book entitled Horseback Riding Pants.  Even though a book entitled Horseback Riding Pants might be about a little boy, the youngest of three brothers, who goes off to seek his fortune when his aged father marries a wicked stepmother. Even though Horseback's bigger brother might be called Long Riding Crop, and his oldest brother, Safe Riding Helmet.  But the name of the book is a real turn-off.  (The older brothers' names don't help much either.)  Horseback Riding Pants isn't likely to go whizzing off the shelf, or get downloaded by the hundred-fold from Kindle.

So why on earth is Little Red Riding Hood still popular after all these years?  There's even been a movie made about the story recently - admittedly a story which has taken the bare bones of the fairy-tale and turned it into something in the horror genre, with a werewolf, and a priest who can exorcise the man trapped inside the wolf's garb.  Try selling a movie entitled Horseback Riding Pants. I don't think it's going to happen somehow.

Friday, April 12, 2013

Watch the fingernails

It's a pretty sure bet you'll come out of Danny Boyle's latest movie trying to figure out all the twists and turns in its plots.  It's probably a good idea to give up, because I suspect the plot doesn't actually hold water too well. 

Trance starts off with telling us how a certain London art auctioneers manages its security - especially when it has a painting for sale that's likely to bring in more than 25 million (and that's pounds, I assume).  James McAvoy is the narrator at this point as well as being part and parcel of the set-up.  And then the set-up becomes the real thing, we go through the process for real, and the two main characters that we've met so far both turn out to be not quite what we were told.  McAvoy comes off very badly in the ensuing rough and tumble and winds up in hospital for weeks, with, among much else, his memory damaged.  The bit of his memory that's damaged holds the key to where the painting that was stolen went, and so off he goes to a hypnotherapist to find out where the painting is.  Except that none of this is quite as it seems, and by the end of the movie, everything we've seen is either in someone or other's mind, or is a lie, or is twisted.  Cassell is exposed as the villain of the piece very early on, and stays a villain throughout...except that he's not the real villain, and the hero isn't quite the real hero, and the hypnotherapist, while certainly a hypnotherapist, is also a good deal more.  Even the ending has some ambiguity about it. 

Critics of the movie have complained that the plot can't be explained properly, and that's right.  But this is a plot with not only an unreliable narrator (in the brief patches when he acts as one) but at least one other very unreliable storyteller, and a director who cheats at times.  Keep your wits about you, and keep an eye on the damaged fingernails. 

The direction is superb, of course, with a great deal of mirroring and reflecting of the actors, a lot of use of people on different sides of glass, or seemingly in touch when they're not.  If the story was even more unbelievable than it is, this would still be a very watchable film.  The cinematography is top notch as well (Anthony Dod Mantle also worked on Slumdog Millionaire), and the music is extremely unsettling - in the opening exposition, for example, the music is running with a different edge to what we're watching, and you're trying to think why this should be. 

It's not uncommon for audiences to have to keep up in modern movies - we're often given less information than we require and have to make assumptions - but Trance takes this to the extreme; like Inception, it leaves you guessing quite a bit of the time, even in its last stages. 

Tuesday, March 12, 2013

Adapting

After the production of Grimhilda! was over, I wrote the draft of a book version of the musical.  I thought this would be an easy task, but it turned out to be full of hooks that I kept getting stuck on.  On the stage, a dramatist doesn't have to explain everything: some of what isn't in the script will be filled in by the actor, or by the director - or even by the music.  Things are pared down in a stage script: the scenery is often the bare minimum, just enough to convey an idea of the place.  Time is loose; even though it pays to keep things within a certain specific period (such as a day, or a night, or two weeks), the actual chronological time can be stretched and tightened as the scriptwriter desires.  There's no clock on a stage (and if there is one, it's often a bit of a nuisance).  The background of the characters may be left quite skimpy - in the musical we didn't tell the audience what the parents did for a living, where Toby went to school, why the toys were as big as the 'real' adults, how Mr and Mrs Map could possibly be married when they were separated by a parchment (and why didn't they just rip it up?)  All these sorts of things are irrelevant on stage; the audience lives in the particular moment, and can ask itself questions afterwards, if it so desires. 

With a book, it's necessary to fill in all sorts of details for the reader, otherwise their imaginative landscape can seem very bare.  The reader may not pay attention to all this detail (I'm a terrible one for missing vital points by skim reading) but it needs to be there.  Even in modern novels, there has to be a sense of a real place, of real time, of people having real jobs and having to go to work, or a real neighbourhood in which they live, and much more.

In the musical we could start straight into the action by showing, quite briefly, that the parents didn't give their son much of their time.  In the book, it proved very difficult finding exactly how to start things, how much explaining to do before the action started, as it were, and perhaps most importantly, why these parents were so selfish.  And then having explained a great deal of that, it was a matter of taking unimportant bits of those details back out again.  It was all a bit like the conga: you put your detail in, you take your detail out, you put your detail in and you shuffle it about. 

I was reminded of all this by seeing an ad for a diamond engagement ring, because of course, part of the story of Grimhilda! concerns a diamond mine run by the villain of the piece.  What, on the stage, was a relatively small space in which the 'diamond mine' existed, and in which the dozen or so workers worked, couldn't be as small and as barely inhabited as that in the book.  I had to re-imagine the mine altogether: it had to be a much bigger place, and there needed to be a lot more people there (though I avoided adding in yet more names and personalities - in fact two of the women in the musical became one person in the book).  It had to be placed within towering mountains, and as soon as the mountains appeared (they're only mentioned in the musical), it became a matter of how tall they were, how impregnable, and so on.  Was there grass on the mountain sides?  Were the paths steep and slippery?

The worst business of all was dealing with the death of the other little boy in the story: Jackie Axelquist.  He's mentioned a number of times, and is a vital part of the plot, but how he died isn't discussed.  Unfortunately, you can't just say in a book that Jackie died.  There are no bones on the skeleton, and skeletons aren't very attractive to readers (unless it's a horror story).  You have to consider what details to include as to how Jackie died, and then you realise that this could be quite grim for the younger readers of your book.  Oh, what a task I set myself!  :)

I have a book on my shelves (yes, I still have some left after the big purge) called How to Adapt Anything into a Screenplay.  It's by Richard Krevolin.  It would be a useful book, no doubt, but it's remained one that I haven't really got my teeth into yet.  But more than a book about turning anything into a screenplay, what I need is a book called: How to adapt your own musical into a book.  If you know of such a piece, tell me about it.  I really, really need it.

Tuesday, January 22, 2013

Wodehouse - and deaths in books

I became a fan of P G Wodehouse's books when I was still in my teens, and have read most of the ones I have on my shelves.  I'd never read French Leave, and since it had been sitting on my shelves since I got it at a sale somewhere - it has Rental stamped inside the front cover in two places - and since I have marked it with a code that I used when I was still in the aforesaid teens, that sale must have occurred a long time ago.

I'd thought it was one of his later books, but the title page says it was published in 1955- Wikipedia, curiously, insists it came out in 1956 - which makes it about two-thirds of the way through his very large canon.   Because I thought it was one of his later books, I assumed that was why it seemed a bit weak in places.  The plotting is intricate, and yet there are some very loose ends (what does happen to the dossier Quibolle, for instance?).  The metaphors are superb in many places and unusually clichéd in others.  It has some slow patches, and some brilliant ones - and for some reason, at the end of chapter 11, we skip nine months, arrive in chapter 12 and discover that most of the cast have been ditched (no matter at what point they were still trying to unravel themselves from the plot) and everything has been sorted out for a very small number of the main actors.  Having expected a good deal of unravelling, it's surprising to find almost none.

It takes some time to figure out who the main two lovers are (they survive into chapter 12, at least), since a variety of other characters get plenty of room to show off their nonsense.  There's a typical Aunt - mostly known as Mrs Pegler, but also by two or three other names - but she's dismissed around chapter 10 after making her presence seriously felt throughout most of the story.  It's a puzzle how she suddenly loses all her fire.  There's the hero's father, a Frenchman with a ridiculous title (Marquis de Maufringneuse et Valerie-Moberanne), who was Mrs Pegler's husband at one point; his first appearance is a delight, in which he deals with the boredom of an office job, and he has several funny scenes.  There is the French policeman, a Commissaire, who is always behind the eight ball because he knows no English and refuses to learn any.  In fact, some of the best parts of the book include scenes in which two people are talking to each other in two different languages without either having much idea what the other is talking about.  But Wodehouse also manages to make the scenes in which people are speaking the same language amusing, especially those which include only French characters.  There are a bunch of other characters, some of whom (the young ones in particular) are virtually indistinguishable, even though they seem vital to the plot.   

Looking back on it, and having got over the shock of it seeming to end so suddenly, I'm more in favour of it than not.  There are much better Wodehouse books, but this one obviously pleases a vast number of his fans, so why should I knock it any further?

And talking of shock endings: the last scene of the 2012 Christmas special of Downton Abbey Iwhich we watched last night) came across to me as inconsiderately brutal.  Julian Fellowes, the writer, had already killed off a major character in the middle of the 2012 season.  Killing off yet another seemed arbitrary and only done for the sake of making people miserable.  Yes, it leaves lots of questions to be answered, which is no doubt part of the reason for doing what he did, but the death came out of nowhere, in the dramatic sense, and damaged what had been an otherwise interesting episode.

I find such deaths can put me right off a story: I remember reading A J Cronin's Hatter's Castle in which the young man who makes one of the main characters pregnant is killed in a train crash not long after.  I put the book down, unable to read any further.  He hadn't done anything to justify such a death.  In the second book of Philip Pullman's trilogy His Dark Materials, (The Subtle Knife) the boy has finally met his father, who's been missing up until now.  Towards the end of the book, the father is killed in what seemed to me at the time to be a quite off-hand fashion.  I almost stopped reading the trilogy at that point, so angered was I by what had happened.  I'm sure authors take the deaths of their characters seriously - there's usually a reason for what they do - but such seemingly random deaths can affect their readers in ways the authors never intended.  Perhaps I get too emotionally involved with characters, but I suspect I'm not the only one.  After all, stories are intended to affect our emotions.




Sunday, December 09, 2012

Misunderstood...

If I spoke the phrase, lifting magnets, to you, what would your first reaction be?  What would the phrase make you think of?

If you work in certain industries, you'd have no trouble identifying the true meaning of the expression, but if, like me, you don't work in such industries, then lifting magnets might easily make you think of going around lifting magnets, literally - say off the fridge, or from a school science lab, or from anywhere else you might find magnets just lying around.  Or it might mean, pinching them from a shop that sold them.

This is one of the joys of language, that what you hear or read isn't always what was meant by the writer.  It can be confusing, but usually the context will help to clarify.  However, when you get a phrase thrown at you out of nowhere, the lack of context allows your imagination to think of something that isn't the true meaning at all.

On the other hand, sometimes even the context doesn't help.  I've never forgotten how, when I was still a child (perhaps at Intermediate level, but a good reader) I came across a particular expression which was unknown to me in the opening chapter of a book. The author told us that the it had been snowing heavily outside, and his hero had decided to go out in the snow for some reason which I've now forgotten, but he wanted to do it secretively.  So he looked in on his parents, who were dead to the world, and then snuck out.  I was appalled.  He saw that his parents were dead, and yet he still went off as though nothing had happened!  I refused to read any more of the book.  If the author was so callous as to let his hero wander around in the snow on some adventure without being concerned that his parents were dead, then I didn't want to read the rest of the story.  I still have something of a recollection of the emotion I felt about this particular phrase that day. I can even visualise where I was in my house.

Most authors strive for clarity; some of them are better at it than others.  But no author can be expected to deal with every way in which his readers will misread his or her story