Dammit Google...

[thistlechaser]

Or maybe my subject line should be "Dammit Me...". Even when I'm really, really curious about something in the middle of a book, I try not to google it because there's too much chance of spoiling something later in the story. Whenever I make an exception to that, I always end up spoiled.

I'm reading a really great book now, and I got to a spot that made me go "buh? Wait, does the author mean... he can't... but earlier in the book..." in a good way, so I googled to see what other people thought. And of course on the google result page I saw the biggest spoiler possible.

Sigh.

It did confirm the ending I hoped for the book (but I hadn't thought the author would be bold enough to use), so... I know I'll like the book's ending, but dammit, all the impact will be gone now.

I knew better. Usually I can resist. But this was such a great, subtle nod to a same-sex relationship, I just had to find out if it was really there or if I was just seeing what I wanted to. (Others found more clues than I did, it really was there!)

Related: The book is the last book of Patrick Ness's Chaos Walking trilogy, which is in production to become a movie! I hope they do well by it. The books are A-M-A-Z-I-N-G, I can't wait to see it on screen.

Comments

[ashmedai.livejournal.com]

I'm the type who reads the last pages first, just to make sure the book is worth reading in its entirety (but I admit I'm not so much into fiction, I read mostly non-fiction).

[thistle-chaser.livejournal.com]

You're the second person on my friends list who does that! I could see that plan working better with nonfiction, yeah.