Sunday, April 13, 2008

Or SWARM

In order to keep my brain from filling up with too many adjectives and risk getting busted for using a copious amount - plus I really, really wanted to read some fiction - I went to the library the other day to pick up the remaining books I have to read for this term. I've been a little slow in reading them this time around, but I knew Prey by Michael Crichton would only take me five days to read, max, leaving me plenty of time to finish Word Painting and get on to The Dreams Our Stuff is Made Of.

I underestimated just how much I wanted to get into some good fiction. I borrowed the book on the 9th. I finished it the next day.

Prey revolves around the semi-typical story of robots getting out of our control. What makes it different is that this time they're nanobots, robots put together on the molecular level. And these aren't just mechanical either. I want to recommend this book to my sister since they use E.coli as a part of the nanobots, which makes them kind of like nanocyborgs.

I'm no stranger to nanobots weirding out and getting smart. The first time I saw nanos taking over was while watching a Gargoyles episode. Anyone ever watch that? That cartoon rocked, just for the record. Except there the nanos wanted everything to be ordered, less chaotic.

Crichton's nanos are program-based (though I suppose most would start out that way) and evolve at an astounding pace. What I enjoyed here was the amount of research Crichton had to do - he even includes a bibliography at the end that spans about 4.5 pages. You get semi-info dumps throughout the book that enlighten you about nanos, bits of microbiology, and distributed intelligence programs. I say "semi" because while they can technically be considered info dumps, they're done in such a way that they feel more like an aside by Jack, the main character, or even a brief moment in his mind as he thinks. The dumps are short and the surrounding text is done in a connecting manner so the dump takes on the feel of a flash of thought by Jack. Though I felt one or two may have been repetitive ("Wasn't this already mentioned?"), for the most part they were pretty necessary. Hey, I've never heard of distributed intelligence programs and the kind of viral programs and such mentioned in the book before, but now I do, and they make perfect sense.

It was exciting and I loved evey minute of it. Sometimes Jack made me want to scream though - "How can you not put two and two together dude?!" - but otherwise it was a great read. Creepy, edge of your seatness, wonder, and "What's going to happen next?" tension. Crichton, or rather, Jack, mentions near the beginning how "No one ever does anything until it's too late." That right there is the freakiest part of the whole book (second only to seeing the result of his wife getting eaten alive by nanos). People are so short-sighted, they fail to take a step back and look at the big picture. They make sloppy patchwork fixes that can only be considered temporary and neglect to examine the consequences of every action.

That's why I keep saying when we are killed off by AI, just like every SF writer ends up writing (or at least, what? 90% of them?), it's going to be Japan's fault. Why? Have ya looked at their robots lately? They're bent on making their robots better, smarter, etc. It's only kind of funny how people think SF writers are imagining this stuff. These days it's more like they're What if-ing this stuff. I don't think people like to let that get into their brains though. Makes them uncomfortable. Suddenly reminded of Ian Malcolm in Jurassic Park, "They were so preoccupied with whether or not they could, they didn't stop and think of whether or not they should."

Oy. It's exhausting to think about. But you know what was really exciting for me? In my novel I decided to use nanos (not made by us, mind you) as a reconnaissance method when checking out a new planet through a portal. Lo and behold, that's exactly what Crichton's company was doing in the book! I was very excited to see my idea echoed (albeit 6 years ago, but hey, I didn't know that), especially by someone like Crichton. The funny part is that when I was writing up the nano section, I made a point to have someone mention the possibility of the nanos getting out of control, my scientist shooting the idea down immediately. I refuse to do an AI out of control deal. It's been done many times, and now Crichton's done the nano thing. Besides, the research involved is a lot of work in itself. Another reason I've realized I like writing fantasy more than SF.

Great stuff. Very glad I stuck it on my reading list this semester. Been meaning to check it out for a long, long time. Totally worth it.

Read the Review


Currently: Thinkin' about mah sistah.

Friday, April 11, 2008

Sniffing, Tasting, Seeing, Hearing, Action

McClanahan has some good stuff in this book. The editors picked a good person to write about description, let me tell you. Frankly, I think this has been the most helpful thing I've ever dealt with when it comes to writing description. Everyone else is too vague. "Show don't tell." "Use personal experience." "Oh, and did I mention show, don't tell?"

I hate that phrase. Mostly because whenever I heard it, no one explained it. I only had a fuzzy idea of what it meant and what people expected from it. Reading McClanahan's book, on the other hand, has been a real treat. The end of every chapter is filled with exercises for practice, and even within chapters she mentions a few things worth trying out.

What's more, she doesn't just talk about describing setting, which is what most people tend to think when it comes to description. She goes into characters, their actions, their objects. She mentions the other senses aside from just seeing - something everyone wants to do (and mentions) when a person or place pops up. "I don't know what so-and-so looks like. Can you describe him?" She has all sorts of little tricks up her sleeve I wouldn't have ever thought about. What's on your character's grocery list? If your character were to go on a trip, what would he/she/it pack?

Ever since reading McClanahan's book (and I'm not quite done yet), I've snorted spices (ok, not literally, but for some scent description training) and eaten a few, thought a some descriptions of my characters (like how I should mention Ballard has a climber's body, something that's become even more important since one of my crit partners thought Ballard was an old guy), picked at some of their actions, looked for more specific words than before so I can go for "the proper naming of a thing," and so forth.

I have a lot of rewriting to do yet, but I think the second time around things will be much better.


Currently: It's early, but I'm awake and feelin' good.