Codes that Changed the World: Fortran

Before Fortran there was no poetry in programming

The BBC are doing a a very interesting radio series on programming languages called Codes that Changed the World, starting with this one on Fortran.

I learned Fortran 77 at university as part of my maths degree. What most sticks in my memory are the dreadful videos we were made to watch featuring a male programmer trying to explain concepts to his dumb girlfriend. That we found the videos offensive goes without saying. I (and many others) stopped going to the lectures and taught ourselves using the text book.

What really puzzled me was why they showed the videos in the first place. Even the lecturer used to apologise for them, saying they were dreadfully old fashioned, but they can’t have been that old. I went to university in 1984. Now, when did Fortran 77 come out, I wonder?

Story Behind the Book Volume 4

Volume 4 of the “Story Behind the Book” series of charity anthologies, edited by Kristijan Meic and Ivana Steiner is out now.  It features a brief essay by me about the story behind Dream London.

As always, all proceeds go to Epilepsy Action, UK registered charity, so spread the word

Similarly to previous instalments, the cover image was taken by Ivana Steiner in her genetics lab while working hard on finding the cure for lung cancer. This time it’s an image of Transfected HEK-293 cells.

Currently the book is available as e-book and print on demand paperback on Amazon. In the next few days it will appear elsewhere…

Links are:
Amazon.com
E-book:
http://www.amazon.com/dp/B00VPK1WBA
Paperback:
http://www.amazon.com/dp/1511602473/

Amazon.co.uk
E-book:
http://www.amazon.co.uk/dp/B00VPK1WBA/
Paperback:
http://www.amazon.co.uk/dp/1511602473

How to be a Great Writer

I was having a conversation about Detective Fiction with a friend of mine recently.

He brought up the fact, apparently well known in detective fiction circles, that the mobile phone is killing detective plots. Writers are tying themselves in knots trying to invent situations in which their characters are unable to make phone calls: they lose their phone, they’re out of charge, there’s no signal, whatever.

Now, I should state again for the record that I don’t read much detective fiction. I’ve nothing against it, it’s just not my thing. But I can’t help thinking that the writers he’s talking about are missing the point. They’re making the same mistake that bad SF writers do: they’ve had an idea and they’re going to hammer the story around it to make it work. They’ve worked out a plot, and they’re going to follow that plot to the end, even if it means getting their characters to act in some pretty strange ways.

I’m often asked about how much I plot a story, and I usually say the same thing. I plot about half way, I have an idea about the ending but that’s it. I always end up following my characters somewhere else. This is one of those things that you can’t be taught, it only comes with practice.

Good writing involves finding an original set of characters and putting them in an interesting situation. Find those things and the story will write itself. A real character will have their mobile phone with them, they will remember to have charged it. Instead of asking how they will lose their phone, a good writer will instead ask what happens next after the character has made that call a lesser writer would have been trying to avoid. That will resuly in a far more interesting story…

You can tell great writing by the way that it just is. There’s something very unforced about it, something very natural, a sense that what you’re reading could be no other way than the way it is. Characters act naturally, any surprises in the story come from their circumstances, not from their reaction to events. Plots unfold in a manner which appears logical (at least on reflection), nothing seems contrived.

Great writing leaves the reader thinking “I could have done that. All I needed was the basic premise and I would have written that. I mean, what else could have happened?”

And that’s the point. It all seems so real, so natural. That’s the mark of a great writer. Someone who has worked hard to make it all look so effortless.

How to be a Great Writer

I was having a conversation about Detective Fiction with a friend of mine recently.

He brought up the fact, apparently well known in detective fiction circles, that the mobile phone is killing detective plots. Writers are tying themselves in knots trying to invent situations in which their characters are unable to make phone calls: they lose their phone, they’re out of charge, there’s no signal, whatever.

Now, I should state again for the record that I don’t read much detective fiction. I’ve nothing against it, it’s just not my thing. But I can’t help thinking that the writers he’s talking about are missing the point. They’re making the same mistake that bad SF writers do: they’ve had an idea and they’re going to hammer the story around it to make it work. They’ve worked out a plot, and they’re going to follow that plot to the end, even if it means getting their characters to act in some pretty strange ways.

I’m often asked about how much I plot a story, and I usually say the same thing. I plot about half way, I have an idea about the ending but that’s it. I always end up following my characters somewhere else. This is one of those things that you can’t be taught, it only comes with practice.

Good writing involves finding an original set of characters and putting them in an interesting situation. Find those things and the story will write itself. A real character will have their mobile phone with them, they will remember to have charged it. Instead of asking how they will lose their phone, a good writer will instead ask what happens next after the character has made that call a lesser writer would have been trying to avoid. That will resuly in a far more interesting story…

You can tell great writing by the way that it just is. There’s something very unforced about it, something very natural, a sense that what you’re reading could be no other way than the way it is. Characters act naturally, any surprises in the story come from their circumstances, not from their reaction to events. Plots unfold in a manner which appears logical (at least on reflection), nothing seems contrived.

Great writing leaves the reader thinking "I could have done that. All I needed was the basic premise and I would have written that. I mean, what else could have happened?"

And that’s the point. It all seems so real, so natural. That’s the mark of a great writer. Someone who has worked hard to make it all look so effortless.

How Writers Write: Neil Williamson

How Writers Write is monthly series of guest posts where established writers invite you into their workspaces, reveal their work habits and share their experience.

The series started last month with Keith Brooke.  This month it’s BSFA award nominee Neil WIlliamson’s turn…

How would you describe yourself?

waterstones reading

I’m not fond of trying to describe myself. Other people are usually so much better at it, even (especially) when they don’t agree. I’m a writer and a musician. If pushed to define musician I’d go with piano player, cabaret performer and songwriter. If pushed to define writer I’d tend towards fantasist, but with plenty of science fiction and a little supernatural horror on the side, as well as a stubborn streak of what we used to call slipstream back in the day. I like having the whole genre paintbox to play with.

What do you use to write?

papernotes

A pocket notebook for notes on the go. And my trusty wee Asus netbook for the actual writing. On the netbook it’s Word for short stories and Scrivener for novels. Word has always caught a lot of flak, but it does the job perfectly well. Scrivener I like for long works, but I only use a certain amount of its features because the netbook’s screen is tiny.
Short stories are written into a pre-formatted template, with any story notes kept in the same file until the end. Novels, obviously being larger, require a bunch of different files: character notes, plot outlines, timelines, snagging lists of bits that need to be added at some point but not right now. These can be in Scrivener or separate doc files, text files, spreadsheets, emails, whatever’s at hand.

For later on in the process, I’m still a fan of the print-out-and-scribble school of editing. Scrawled margin notes, emphatically scored out paragraphs, whooshy connecting lines. It’s all so much more colourful and dramatic than Word or Scrivener editing tools. Additionally, though, it allows me to second guess the changes I was so confident of a few days ago before I commit to them.

Recently, I went even more hands on by resorting to printing out all of my plot points and cutting them up and physically rearranging them in front of me. What can I say, you go with what works, don’t you?

When do you write?

pintlaptop

I have a regime that fits my writing in around my day job, home life and other creative pursuits. I had to establish one because there are so many things going on that nothing would get done otherwise. So, on weekdays I leave early and write for an hour before going into the office. Then at lunchtime I pop out and steal another hour. That adds up to ten hours a week. Weekday evenings I usually do not write: when I’ve not got a gig or a rehearsal, I usually don’t have the mental energy for it anyway, and I actually enjoy spending time with my bidey-in too. On Saturdays and Sundays, though, I try to spend three to four hours getting a good chunk of work done. So most weeks I’m doing 20-25 hours of writing. Which I don’t think is too bad.

Where do you write?

tealaptop

The weekday session take place in one of the many popular chain coffee establishments. These places seem to be purpose built for writers. Chair, table, power, wifi, selection of beverages, occasional moral support from interested serving staff. What else do you need? Somewhat obtusely, it’s my habit to drink copious amounts of tea in these sessions. This is for two very important reasons: it takes far less time for baristas to prepare which means more time for writing…and I fricking love tea.

The weekend sessions can be in a variety of local places. There are a few good cafes in our community, and there’s one in particular in which I’ve become part of the furniture. To change it up, I occasionally opt for the craft beer pub across the road instead, because…hell, craft beer? I got into the habit of using outside venues because our upstairs neighbours used to be pretty noisy, but we’ve new neighbours now, so I’ve recently “moved back in” as it were. I still find it easier to write outside of the house though, partially because the café environment is what I’m used to. It’s the office, it’s where the work gets done. And it doesn’t have a TV.

I am prone to distraction, though, so one vital ingredient is isolation music. I’ve got a Spotify playlist consisting mostly of film soundtracks that does the job very nicely.

How do you write?

Handwritten notes

This is something I don’t often really think about or analyse to be honest. With short stories, I have ideas, and note them down and when I have enough notes I…just go for it. That sounds insultingly simple, doesn’t it? Partly that’s because I’ve been a short story writer for many years, and have got used to creating on that scale, so the process is something that just happens now.

Novel writing is relatively new to me (I’m finishing my second one right now), and the process is similar except that for novels there are more notes. Many more notes. One of the things I found interesting (both frustratingly and rewardingly so) about writing The Moon King was that the deeper I got into writing the novel, the more ideas about the way the world worked suggested themselves. I went through several iterations where the plot changed quite substantially because I’d written myself deep enough to understand more about the world and the characters. I kept snagging lists of notes of stuff I needed to go back and change on the next draft. Sometimes these were tiny changes, sometime they were big. It seems like an inefficient approach, but the point is that I couldn’t have sat down and thought it all out in one go. I needed to write the place, to live there with the characters to discover these things. So far Queen Of Clouds has been the same. The longer I spend in it, the deeper I go, the richer the world gets, and the more times I have to go back and ripple it all through the story…sometimes changing the story itself pretty substantively. Hopefully it makes for a better book at the end, but it’s a slow process. Who knows, maybe I’ll get better at it once I’ve been writing novels as long as I have short stories.

In terms of drafting and redrafting, I used to be an inveterate polisher. Every word, line, paragraph had to be at least good before I could move on. Now I just don’t have time for that. Getting the story down is much more important. If I can’t think of the right adjective I’ll throw three in that are roughly in the ballpark and sort it later. I’m not sure about a detail or a character name or a piece of action, I’ll leave a gap and write myself a wee note to fix it in the next draft.

I don’t work to a daily word count, but I do give myself deadlines. That seems to work pretty well.

Questions of style. First Person, Third person, present tense, past?

Whatever suits the story. I’ve used all of those in the past (and why did you leave out second person?). I personally tend to avoid omniscient viewpoint. It can be done brilliantly, but also very badly, and I’ve no great facility with it, so I leave it well alone.

How many redrafts? – How many readers? – How easy is it to let go?

Redrafts – depends on the story. Some stories are pretty much good to go right away. Others never quite feel right and I can tinker with them for years before finding a way to make them work. I mentioned that novel writing, for me, seems to be a process of discovery through redrafting, but I’ve not done enough of those to know whether it takes two, or five or ten drafts before a book is generally right.

Readers – I’m very fortunate to be a member of the Glasgow SF Writers Circle, an excellent and longstanding peer critique group. I’ve also got some wonderful writer friends who I drag into service from time to time, but try not to abuse their generosity.

Letting go – I’m a pretty honest appraiser of my own work. I know when, even if it’s not perfect, it’s at least good enough to do the job I want it to. And I know when, even if people enjoy it, it’s still lacking something. I’m honestly not a perfectionist, but my internal quality controller has high standards.

What are you working on at the moment?

QOC sample

The second novel, Queen Of Clouds, is finally in the finishing stages. I’ve done all I can with it. Mined all I can from its depths. I’m just lining the words up for hopefully the last time (for now) and then we’ll see what my agent makes of it. And after that we’ll have a chat about what’s next on the novel front. I’ve an idea for a series of short adventure fantasies that I’d like to get into, but we’ll see.

Other than that, I’ve got a near future science fiction novella about surveillance states part-completed and a whole load of ideas for short stories. One of the things I’d like to do this year is go back and try my hand at horror again. I made my first sale to Black Static magazine recently with a supernatural tale called The Secret Language Of Stamps, and I’ve got a few more darkish ideas in production too.

That’s the thing about being a writer. You’re never short of ideas.

More Information

Neil Williamson’s Website: http://www.neilwilliamson.org.uk

5 Common Linux Misconceptions

1. The Linux Filesystem Hierarchy is a logical, sensible structure

It’s not. It’s something that has been cobbled together in an attempt to unify diverging practices. In an age of terabyte hard drives its easy to forget a time when you were limited to just a couple of floppy drives for storage and had to store programs across different locations.

That’s why program files today are stored in /usr and /opt. And /usr/local. And /usr/bin and /usr/sbin. Oh and /bin and /sbin. When you can’t store everything in one place, you have to make (sometimes artificial) distinctions between where things go. Remember a time when you used to boot up a computer with one floppy, then put in a second floppy with an application program, then a third floppy with data files?

Someone designing a directory structure in a world where terabyte HDDs are the norm might be persuaded it was a good idea to keep bootup files separate in /bin. But /usr/sbin? /opt? I don’t think so.

Have a look at Gobolinux http://www.gobolinux.org/ As they say

GoboLinux is an alternative Linux distribution which redefines the entire filesystem hierarchy.

If you want to know what goes where, there’s a nice overview of the Linux Directory Structure here: http://www.comptechdoc.org/os/linux/usersguide/linux_ugfilestruct.html

2. Bash is just like the Windows shell, except with different commands

Here’s a simple test. How do you use the ls command to list directories only?

Checking the man page, it’s obviously ls -d, right?

Wrong.

Do a Google search on linux list directories only and you’ll find a lot of people making the same mistake. It all comes down to failing to realise that its Bash that’s expanding the * wildcard, and not the ls command itself.

If you’re going to use Bash, you’re going to have to take a little time to read up on how it works. This is a great site: http://linuxcommand.org/

(My preferred method is ls -d */, btw.)

3. The .exe files are in there somewhere

It’s easy to accept that file extensions aren’t necessary in Linux, but it’s hard to shake the idea that something like exe files are still lurking in there somewhere, albeit under different names.

Not really. Linux is far, far more modular than Windows. This is down to the philosophy on which the system is built: programs tools chain their input and output to produce results. A typical Windows application is a flat pack wardrobe, something that solves one problem. A typical Linux application has been formed from many parts using the equivalent of saws, hammers, screwdrivers and chisels.

As an example, a GUI based program that would be a single exe file in Windows would typically be a graphic interface to command line utility in Linux. In terms of user experience, there should be no difference, but behind the scenes, things are very different.

4. Linux is faster/uses less resources than Windows

That may have been true back in the Windows Vista Bloatware days, and it may be true for lightweight distros like Puppy Linux http://puppylinux.org/ and Damn Small Linux http://www.damnsmalllinux.org/, but its not so true now.

Windows 8 may have the worst user interface ever devised, but it installs quickly, loads quickly and runs quickly, matching if not beating systems like Ubuntu 14.04 in benchmark tests.

Why mention Ubuntu 14.04? Well, that leads onto the next point…

5. It doesn’t matter what it looks like, so long as it works

It does.

It really, really matters.

You might do everything via the command line. You might think that Openbox is all you need as far as desktop management goes, but you’re in a minority.

If you’re the only person using your computer, then fine, but if your less technologically inclined partner, friends, parents or children are relying on you to provide the IT then all of a sudden looks really matter.

Of course they does. In a world slowly being taken over by Apple this is so obvious it shouldn’t need saying.

The command line is fantastic, lxde is a miracle of economy, damn small linux is damn fine, but they’re not what most people regard as a solution. What most people want is something that looks good and is so easy to use they don’t even have to think about it. And there’s nothing wrong with that. I don’t care how my shirts are made as long as they look smart and feel comfortable. Most people feel the same way about their computer.

How Writers Write: Keith Brooke

Following the interested generated by my posts on How To Write, I thought it might be interesting to see how other writers produce their work.

How Writers Write is monthly series of guest posts where established writers invite you into their workspaces, reveal their work habits and share their experience.

First up is the incredibly talented Keith Brooke:

How would you describe yourself?

How would I describe myself? I write, I edit, I design. I work in lots of different fields, under a variety of pen-names. Much to my (now-retired) agent’s frustration, I flit about between all these things, with little in the way of a coherent career plan. And I love it.

What do you use to write?

Story Notes
First Draft

Everyone raves about Scrivener so I keep thinking I should give it a go. I’ve even gone as far as buying a copy when it was on sale a couple of months ago. I’ve opened it, and followed a tutorial; I’ve played with creating my own templates to suit the way I work. And then I’ve gone back to Word and text files. It just suits me, particularly now that I have two monitors, so I can have lots of files open and visible at the same time.

I tend to keep notes of ideas on my phone, then transfer them to text files or Word docs every so often. When I’m in the thick of a draft, I’ll usually have a notes file on my phone just for that project, as ideas come at the most unhelpful of times. I’ll also have a Word file for that project’s notes: a short overview; notes on characters, settings and anything else that’s relevant (maybe some scientific aspect, or politics, or history). I’ll also have a more detailed outline to work from, which is very much a work in progress, modified as I go on and the real story emerges. And then there’s the actual draft itself: just one Word document, regardless of how long the story will be. That sounds awfully efficient and well-organised of me, and I guess to an extent it is: an approach refined over three decades of writing.

When do you write?

kblaptopBack when I had a day job I trained myself to write at any opportunity. The first draft of The Accord was written in coffee shops, bars, at an airport, at friends’ houses, in the back of a car, in lunchbreaks at work, and probably other places that I forget now. If I could grab even as little as ten minutes, I could get a few more paragraphs down; more importantly, it meant that the next time I had a more substantial writing session the story was fresh in my head so I could hit the ground running.

I left my day job last year and now it’s more a matter of juggling different projects: as well as writing under various pen-names, I edit, run the infinity plus publishing company, and do various other design and publishing activities. One consequence of this is that each day tends to be a different mix, and it’s rare that I get a day just to write. I do, however, get more frequent and longer writing sessions than I used to manage, which is lovely.

I try hard to keep my writing and publishing activities to normal working hours, so that I get evenings and weekends for other things. It’s flexible, though: sometimes real life intrudes during the week (that’s happening a lot right now), and sometimes writing commitments mean I get up early (sometimes I’ll start at 5 or 6 in the morning) or keep working into the evenings and weekends. I do manage to keep a pretty good balance, though.

Where do you write?

nopower

The Accord was probably an extreme example of writing wherever and whenever I get the opportunity. I do sometimes take my old Netbook away on trips and write on planes, in hotel rooms, etc. Now that I write and edit full-time, though, my habits are a lot more regular. Or rather, they were, and they will be; they just aren’t at the moment.

How it used to be… Up until January, I’d set up office at one end of our dining room table, with a desktop PC, two big monitors and a comfy office chair (I started out just using one of the dining chairs, but that played havoc with my back).

How it will be… We’re in the process of converting the dining room into a work area. My wife Debbie needs cake-decorating space (https://www.facebook.com/brookesbakes), so she’ll have a work area for that on one side of the room, and I’ll have a proper desk on the other side of the room.

At the moment… It’s a building site. We’ve knocked down walls and had plastering done, we’re re-doing the kitchen at the same time, and the place is complete chaos. I’m spending a lot of my time doing all the jobs we’re not paying other people to do: emptying cupboards, moving furniture, decorating… And my work? I’m on a cranky old laptop that runs slow and often not at all, with old software and nothing where I want it (I’ve been spoilt by the shiny new desktop PC!). At the moment I tend to work on one of the living room sofas, wrecking my back again (or maybe that’s down to all the lifting – a writing life doesn’t prepare you for all that physical stuff).

How do you write?

First Draft
Memento Notes

I can work in distracting, noisy places, but I don’t choose to have music or TV on when that’s within my control. I usually have ‘net access, but that can be a big distraction, so sometimes I just switch the wireless off for half an hour or so.

My working outlines are a lot more skimpy than they were in the early days – a confidence thing, as much as anything else. As a minimum my outline will have a few key points: opening, ending, and some landmarks along the way.

I’ve taught writing to postgraduate level, and I always make the point that I’m never going to teach people the way to write; it’s all about helping them find their own way to write. Having said that, there are some basic rules that tend to help most people. Foremost among these is that once you have words down on the page you have something to work with: bad writing can usually be fixed, but polishing that fabulous idea while it’s still in your head doesn’t really get you anywhere.

So I write. Often fast, just to get those words down. And often, even when I think I’m writing rubbish, when I come back to edit I see that it’s okay: there’s always something I can work with, at least. I’m disappointed if I don’t hit 2000 words on a writing day, and my peak, fuelled by caffeine, deadlines and desperation, has been more than 10,000. Some people may see that as hacking it out – how can the quality possibly be there, when you write so fast? I see it as honed technique: when I’m working like that, I’m capturing the big picture and writing with a lot of energy and momentum; the rewriting brings refinement and adjustment until I’ve hit the right balance. But if there’s one rule of writing, then for me it’s Get Those Words Down.

Questions of style. First Person, Third person, present tense, past?

pcYes, to all of those. Whatever suits the story. The Accord is my most complex in terms of viewpoint, as it’s told from first person present and past tense, third person present and past, second person present, past and future tense, and then various hybrids of multiple first and third person devised to portray the viewpoint of multiple characters and character-fragments sharing the same brain. It sounds complicated and for the first half of the first draft I didn’t even understand it myself, I just wrote each scene as seemed appropriate; and then, one day away from the computer, it all mad sense to me, the rationale for the different viewpoints and the drift for some characters from an intimate inside-the-head viewpoint to a distanced, more reportage perspective.

Viewpoint and style aren’t things I really sweat over before starting. They usually emerge while an idea is developing, so that by the time I sit down to start a draft the storytelling voice and approach are clearly established in my head. Sometimes elements of style emerge as I start to write (an angry voice, a consciously smooth style, etc), and when that happens it’s just a matter of going back and fixing the early pages – as long as you have those words down, you can fix that later, when the first draft is done

How many redrafts? – How many readers? – How easy is it to let go?

Edit Notes
Edit Notes

Back when I printed actual drafts, each piece would have at least three printings. I’d print the first draft and then edit it longhand until it was barely legible. Then I’d type in the changes, print a clean copy and repeat as necessary.

Nowadays I rarely print anything, so my drafts are far less easy to distinguish. I’ll often edit the early stages of a story to ease myself into writing new material for the day, so the early parts of a novel might be the equivalent of second or third draft even before the overall draft is complete.

After all the revisions, it’s off to my trusty first reader, Eric Brown. We’ve swapped drafts for something like 25 years – a trusted first reader is one of the most valuable tools in a writer’s kit, and Eric is a very good tool. I should probably rephrase that… Neither of us pulls punches when critiquing each other’s work, and we’re both prepared to ignore crits that we don’t agree with. Generally, I’ll act on about 75% of the things Eric spots; then I’ll probably mull over much of the remaining crits, wondering how he missed the point so badly. Then I’ll come back to the draft and probably act on those remaining crits, too, once I see that he’s right.

What are you working on at the moment?

kdpsales

I’ve been doing lots of work for infinity plus recently, with Garry Kilworth’s fabulous historical novel The Iron Wire published recently – this one tells the story of the men who constructed the first telegraph line across the heart of Australia in the 1870s. And Eric’s collection of ten short stories, Deep Future – it’s great to be publishing some of his books these days. My own most recent novel is the big epic fantasy, Riding the Serpent’s Back , a widescreen story of a civilisation’s end days.

More Information

Keith Brooke’s Website: http://www.keithbrooke.co.uk/

InfinityPlus: http://www.infinityplus.co.uk/

How Long does it Take to Write a Novel?

The answer? Fifteen days, twenty hours and fifty five minutes.

I know that because I finished Dream Paris yesterday and I’ve been clocking the time I spent working on the novel.

The time includes the writing of the first draft of the novel and three redrafts: first redraft, the second following feedback from my wife and a third following feedback from other readers. The novel is now with my editor awaiting his feedback and will probably undergo at least two further redrafts.

I’ve not counted time spent planning the novel or the notes I made prior to embarking on the writing. As some of the ideas, scenes and dialog that appear in the novel have been collected over several years, it was difficult to measure this.

Some statistics you might find interesting:

I started on the 18th February, 2014 at 9:58am
I finished on the 20th February, 2015 at 3:00pm exactly

If I’d been writing an 8 hour day the novel would have taken around 48 days to complete.

The book is almost exactly 100 000 words as it stands, given that it took just short of 381 hours to write that gives an average word rate of a rather pitiful 262 words an hour. Given that the first draft took around half the total time to complete, that makes the word rate a more respectable 524 words an hour. As I normally average around 850 words an hour, the missing words are partially accounted for by the fact that I cut around 60 000 words from the novel due to mistakes, changing my mind or no good reason.

If you’re interested how I collected this data, well, have I mentioned Emacs? I recorded the time taken using org-mode. You can find out more by reading this post on My Emacs Writing Setup.

10 Books I Couldn’t Put Down

I don’t know what my favourite book is, but the following are books I read at various times of my life that, at the time, I couldn’t put down. Most of them I finished in maybe one sitting – definitely no more than two or three – perhaps whilst lying ill in bed or on holiday.

Some of them I’ve read over and over again, two of them I’ve only read once (one of those because it’s not yet available on Kindle and I don’t buy paper books any more)

Most of them are expertly crafted, one of them is appallingly written. All but two have very good stories, half of them are strongly plotted, three of them are character driven, three of them made me laugh out loud, three of them made me smile, four of them had me on the edge of my seat, none of them made me cry. Maybe three of them would get into my top ten books ever.

In no particular order…

  • Rachel’s Holiday by Marian Keys
  • The Bonfire of the Vanities by Tom Wolfe
  • The Hitch Hiker’s Guide to the Galaxy by Douglas Adams
  • The Secret Diary of Adrian Mole aged 13 3/4 by Sue Townsend
  • The Mote in God’s Eye by Larry Niven and Jerry Pournelle
  • Complicity by Iain Banks
  • A Tale of Two Cities Charles Dickens
  • The Rainmaker by John Grisham
  • Harry Potter and the Deathly Hallows by JK Rowling
  • The Da Vinci Code by Dan Brown

​10 Books I Couldn’t Put Down

I don’t know what my favourite book is, but the following are books I read at various times of my life that, at the time, I couldn’t put down. Most of them I finished in maybe one sitting – definitely no more than two or three – perhaps whilst lying ill in bed or on holiday.

Some of them I’ve read over and over again, two of them I’ve only read once (one of those because it’s not yet available on Kindle and I don’t buy paper books any more)

Most of them are expertly crafted, one of them is appallingly written. All but two have very good stories, half of them are strongly plotted, three of them are character driven, three of them made me laugh out loud, three of them made me smile, four of them had me on the edge of my seat, none of them made me cry. Maybe three of them would get into my top ten books ever.

In no particular order…

  • Rachel’s Holiday by Marian Keys
  • The Bonfire of the Vanities by Tom Wolfe
  • The Hitch Hiker’s Guide to the Galaxy by Douglas Adams
  • The Secret Diary of Adrian Mole aged 13 3/4 by Sue Townsend
  • The Mote in God’s Eye by Larry Niven and Jerry Pournelle
  • Complicity by Iain Banks
  • A Tale of Two Cities Charles Dickens
  • The Rainmaker by John Grisham
  • Harry Potter and the Deathly Hallows by JK Rowling
  • The Da Vinci Code by Dan Brown