The Night Has A Hero (sort of)

I've been itching to read something by Clive Barker for some time now. Cabal is now my official Clive Barker introduction.

Meh.

While I haven't yet read the short stories included in the book I have (I'm not sure if they're with every edition of Cabal or not), but I finished Cabal a week or so again and have since moved on to other things. I'd mentioned needing gore, or good examples of it, in the hopes of making, ah, messy things in my book a bit more visceral. Cabal had some good bits to that end, but overall I felt a bit let down by the story. It's only about 200 or so pages, but it feels shorter than that.

I think my main problem was that I never really got into the characters. At all. Boone was just some random guy who got sucked into all this. I never knew much of his history, which I suppose was necessary because of his "memory loss" but I was curious as to why he was visiting a doctor in the first place. In fact, when I pictured the guy, despite the fact that seeing a psyciatrist is expensive, I thought of him as scruffy, scary-looking, almost of a homeless guy quality. I didn't have much to go on. I didn't even know he was supposed to be handsome until his girlfriend took over the story and said Boone was a fine-looking guy. The story was actually hers...sort of. The blurb made it seem like hers, she had the most camera time (so to speak), though there was the occasional head hopping.

I wanted to see more of Midian. For those of you wondering, Midian is a place where all the super-freaks, creatures, and monsters of the world live, staying out of the sunlight and away from people who would kill them without a second thought. I would have liked to explore that place, it's history, and more of the things that inhabit it. But to no avail.

Maybe I would have liked it better if I were more in tune with the characters - when Lori was in danger of getting killed by a total psycho, I hardly felt her fear. I don't often read horror, so when I do, I expect it to totally freak me out. I mean, hell, I still have fear the dark from time to time. Just last night I had a paranoid chill up my back and looked over my shoulder into a dark room and in my mind, threatened whatever was lurking in there with death, or at least one hell of a fight. So for this story, in which the dark contains all sorts of weird things creeping around, to leave me feeling "meh" and without any extra fear of, well, anything (not like I need any), is a bit disappointing. Maybe I would have liked it better if Midian wasn't under attack by a bunch of podunk small town cops (in Canada no less). By the way, all the inhabitants of Midian knew what was coming. One creature had a procog vision of it. The head honcho that created Midian knew they'd be invaded. And they didn't put up a few snags? No defense? I mean, if creature-A knew creature-Bob was going to die, wouldn't Bob not stand by the door later on? Maybe they didn't know the exact circumstances, but still, when creature-A starts naming names, wouldn't those named get as far away from the surface of danger as possible?

I also wish I would stop critiquing books as I read. I noticed Barker did a lot of this:

"Do you think so?" said Lori.
"Of course," came the reply.

A lot of "came the reply" tags. It kind of sucked when more than one person was involved with the conversation. I felt like Blinkin of Robin Hood: Men in Tights. "Pardon? Who's talking?"

Normally my imagination runs wild. Not so much here. I would have preferred to stick with Boone and explore Midian. Find out what happened to Peloquin. I don't care that the head sheriff gets his best ideas on the crapper. *snort* Little things, mostly.

Anywho, one down, four to go. Live Girls or Berserk will be next. Shouldn't take long to read them either. 3 days for each, max.

Read the Review


<-- Kuski's work makes me think of Midian. Check it out, it's liquid awesome.

Oh dear

During residency (which I have yet to blog about in the Life O'Me section, and when I do, you'll all get to hear about the crazy things that happened, from my invisible powers to The Battle of Farrell Hall) I discovered that it was Mystery's turn to choose the book to read. I took a look at the list of possibilities and lo and behold, there was a book I'd read back in November - In the Woods by Tana French. I had a brief panic attack and from then on "casually" mentioned to anyone around me that "I hope they don't pick this one. It wasn't that good." The blurb offered up by the book was misleading, which is likely why I was irritated with the whole thing.

I have mixed emotions about this book. I reviewed it and while I rant on about how I dislike it, I did give it 4 stars. Yet if I had to read it again (which I suppose is expected...maybe?), I wouldn't. Er, in this case, won't. No thanks. I gave it 4 stars because of the skill involved with the book, much of the plot, as well as other items but overall it's defintely not something I'm ever going to rush out and buy (such as when I saw it at work the other day released in paperback - I kind of snorted, waved my hand at it, and walked on). I just think...if no one liked Lies of Locke Lamora...oh god. The horror....

So, for any WPF people reading this and who may be curious about my likes and dislikes, check out the review.

And just so you all know, I don't dislike mysteries - I just was not all that jazzed about this one. Looking at the reviews at BN.com, I realize I'm not the only one. Good to know.


Currently: They did what?

The Dreams Our Stuff Is Made Of

An interesting book. Going in, I'd though I'd chosen another history book - like I'd wanted - only to find I was once again reading a series of essays connecting the real world to the worlds of SF. However, Disch's book is much more coherent than Hartwell's. Half the time I wasn't sure where Hartwell was going in his ramblings, though I was sure there had to be a point in there somewhere. Though occasionally it felt a little like Disch strayed a bit from time to time, I have to say, the man had some seamless transitions. He does stay on topic in relation to his chapter title, and that's really what counts.

Though I still want a history of SF, mostly to give me more structure in terms of SF's development through its authors and over time, this did offer some semblance of order given though the topics and time frames Disch decided to discuss. My favorite chapter had to be "How Science Fiction Defused the Bomb" in regards to the atomic bomb panic and radioactive possibilities. It's just that it's still a relative topic today, which is ironic because when Disch wrote the book, the scare had already died down and everyone learned to live with the bomb. We still live with it, but it's become a fear yet again and it's still bringing up monster movies (at least, atomic testing is one of the many theories beind the Cloverfield monster).

Throughout the book, I kept wondering what Disch would have to say if he'd written this today or even a year or two ago. Even though I consider 1998 to still be semi-recent (nevermind that it's already a decade ago), the book felt dated. I guess technically it is, another reason it would have been neat to see DIsch's thoughts on the now. Especially since NASA is still in full swing, SF/F movies have taken a firmer foothold in Hollywood than ever (and most of them directly from books), Star Trek is still loved, so much so that a new movie is coming out in 2009, computer graphics have become more fantastic than ever (often to my annoyance, in fact), and so forth.

The chapters were easy to get sucked into, the connections Disch made between SF and other areas of life/the world from religion to politics to wigged-out people committing suicide in the name of God-knows-what, all rather solid with great examples. Disch lived through most if it, I'm sure, and whatever he didn't deal with directly, he did his homework, something I admire because I'm certainly not as willing or likely to do so.

I'm not too sure I agree with him on Poe as the head of the SF bonanza, but he has a commendable argument. I can see his points and on several occasions, pulled out my fat, leatherbound everything-Poe book and read some of the pieces Disch referenced. I admit, I haven't yet had the chance to read all of Poe's work, so Disch has a one-up on me there, I'm sure. Maybe as I continue reading, I'll start to agree more. Still, I think there were too many before Poe that could collectively take the slot of parent(s) of SF, but again, I'm fuzzy on all my dates, so more research on my part would be needed. Now I just need a list of authors and to get motivated...

As a whole, a very good read and insightful, especially concerning the past. The present and future are easier for me to spot and connect (obviously) so seeing past events coupled with SF influence through a writer like Disch was enjoyable and a better read than Hartwell by far.



Currently: Dreaming of floating away and sleeping

Improbability Drive, Activated!

*squeak, honk, erk, eek, boink!*

Hmm...luggage.

Right, now that normalily has been restored (I have The Hitchhiker's Guide to the Galaxy on the brain - and on my desk over there so, you know), here's the blog entry I meant to write several days ago, but keep forgetting because I swear if I don't write this stuff down, I forget it.

I should invest in some Post-It notes.

Anywho, I finished up Word Painting and I have to say, Dr. Wendland chose a perfect book when it comes to working on description. Admittedly, my description still needs some work, but that's beside the point. McClanahan really does touch on every aspect of description and includes so many useful exercises, it's great. I haven't really had the chance - okay, you know what? That's a lie. I've had chances, I just don't use them properly. I need to reorganize my time and stop screwing around, though this week I haven't even really had time to screw around, but next week I only work 8 hours (down from 34 - how the hell that happens I don't entirely know) so I've got plenty of time on my hands.

Ok, moving on. I plan to review this book, but when I do, it's getting 5 stars, all the way. I'm really glad to have found it and as time goes on, I'm going to go through it again, one chapter at a time, much slower, maybe devoting an entire month to a chapter, and working on all the exercises, taking my time and searching for the proper and special naming of things (which I feel is my biggest weakness. When it comes to scent and sound and touch, well, those I just forget, moreso during this story because half the time my guys are all wrapped up with oxygen masks and full protective bodysuits). Well, almost all the exercises anyway. A few I don't think I could do because I'd get distracted. Any that have to do with music at least. For example, there's one that suggests walking about 6 blocks or so noting details as you go, first with one type of music and then again with a different type to see what differences you see. That wouldn't ever happen because any time I walk around outside for any period of time with music, my mind wanders to one story or another and it's like a switch going on in an idea factory. Ka-chink! Ideas rolling down the conveyor belt and dumping into buckets for later use.

That will be good though, to take my time and work on this and that in better detail, revising and practicing and tweaking. I can use my ridiculous fanfic as practice as well, one of the reasons I decided to keep it going, as stupid as it likely is.

The point is that the book is useful, extremely helpful, and anyone in need of descriptive help should look into it. Not sure what else is on the market, but this isn't getting replaced by anything else anytime soon. In fact, it's slotted in my brain as a potential class when I eventually do my little module thing before graduating, right beside idea generation and name creation.

The Dreams Our Stuff is Made Of is my final book, but I plan on writing about that after I finish, which should be too long as I've only got one chapter left, except it'll probably take me until the final deadline to write about that since I freaking forget everything.

Really should get some Post-Its...

ENGAGE IMPROBABILITY DRIVE!


Currently: An octopus?

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.

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.

I Couldn't Stand Watercolors

As it says on the main Profile, I'm reading Word Painting by Rebecca McClanahan. My goal this term is to work on my description. Bleh. Er, not about working on my description, but just the fact that for some reason it's become not-so-good. I don't know why, but let's forget about that at the moment.

As I read McClanahan's guide to writing more descriptively, I realized something that helped to explain my difficulty in getting description to transform from mundane to pure awesomeness. Don't know why I never really saw it before; it seems like it should have been as plain as day. I read other great descrptions and think, "Man, I wish I could write like that." Maybe if I'd been paying attention, I wouldn't be at this juncture. The problem lies in my issue with finding just the right words. I find myself constantly trying to find great words to truly express what I want to express. My thesaurus has become dog-eared with use because I just can't seem to fit all these good words into my head. I make little marks next to words as I write, putting notes in the margins, * find alt word, when something doesn't hit me right and I don't want to stop (or I have stopped and haven't found the right word so I simply return later).

McClanahan speaks of the proper and special naming of a thing, as well as words that describe as opposed to merely labeling something. That could not be more right. Without the proper words for an object, action, and so forth, the description isn't as precise and can make all the difference. I need to focus on doing that. Exactly what I needed to be beaned in the head with.

She also mentions taking time to examine things, look at them in different ways, with different perspectives. At least I can say I do this. Often, actually. I like to go outside and ponder the tiny veins in a maple leaf or the way a spider keeps her legs on individual strands of her web, pulling them taut to detect even the slightest movement, which could indicate dinner. Just today I found a black ant, a soldier, in the sink. No idea how he got there, and at first I thought he'd been smashed and someone swept him in there and failed to swish him down the drain. But when it doubt, a little puff of air from your mouth will tell you whether he's alive or not. He was, so then I plopped my chin at the edge of the sink and watched him, letting my soup bubble for its three minutes. I like to just eyeball things and describe them in my head - like the baby praying mantis I once found, who (and I swear by this) loved my petal pink nail polish. But I never put any of it down on paper because I never considered it of any use. Perhaps I should have as practice.

Considering McClanahan's words, maybe I should do this more often before putting anything down on paper when it comes to my story. Sit back, close my eyes, and put myself in the room. Stand next to a character. Touch the table he's at. Stare at the scene he sees (or she in some cases).

I need to sweat the small stuff.


Currently: Somewhere being ethereal.

P.S. More on this book to come as I continue reading.

Mmm, spicy.

Working at Barnes & Noble, I can borrow hardcover books, and as long as I don't mess them up, return them after two weeks so they can go back on the shelves in still-perfect condition. We do this all the time, but if we screw up the book, we have to buy it.

BWAH. Always make sure lids on tupperware are completely closed before putting it in the same bag as your book - especially when the container had chili in it. *oh so sad*

Actually, I managed to clean the book off fairly well, and could have probably gotten away with putting it back without buying it, but I couldn't do so in good conscience. So I ended up buying a $30 hardcover edition of Dune by Frank Herbert. I'm not mad anymore, though it does bug me that the book isn't in pristine condition (I'm very anal about the condition of my books - exactly why I'll eventually buy a hardcover edition of LOTR and leave the paperback with those who messed it up). Oh well. I suppose if I were to ever buy Dune, I might as well get it in hardback because it's big enough to merit the strength hardcovers bring.

Likewise, this gives me a chance to comb through it again in the future and look for the technical error as pointed out by my mentor Anne. We briefly discussed the book vs. the Sci-fi channel's miniseries and how there was a techinical error in each (the same one), but I can't remember the Sci-fi channel's version (though I do remember the costumes and color being fantastic), and I didn't see the hiccup in the book. The best I can come up with is the difficulty in transforming Dune from a desert planet to what everyone kept talking about in the book. Frankly, I don't think it could be done, not without a nice set of mountains to help regulate the weather once all the water was eventually released into the atmosphere (and it would be too). If you still need the desert, you'll need some kind of block to keep desert from encroaching upon jungle/woodland/whatever they want to make. Though I might have missed the error because I'd start out with it in my brain and then read and forget and keep reading and only remember the next time I picked up the book. I'll have to find the Sci-fi miniseries to find it I'll bet.

Ok, aside from that, I pretty much got what I expected from the book. At first I was jealous of Herbert, because he head-hops and he gets away with it. I'd love to head-hop like that, which is probably why I get in trouble for doing it. I don't head-hop like he does; it's not structured enough. Well, at least the pieces I had people read didn't have it structured enough. Either way, I don't think I could match Herbert's style, and in reality, why would I want to? Not to put down Herbert of course, but I mean why be him when I should be me? Besides, I can do a little skipping around when I get to my romance novel (oh so far in the future). Anyway, there were a few times when I thought, "Wait, who's thinking/talking now?" due to the hoppage, so even Herbert isn't perfect. Nyah nyah. (I'm so rude...and Frank Herbert passed away 1986 so I should stop).

I'd seen the movie long before this point in time (ah, I remember watching it that one time in college knowing I was the only girl in the room that would enjoy it, haha) and think that aside from a collected number of things, it was pretty close to the book - especially in terms of style. Talk about head hopping there. I think that movie is the only one with that many people thinking thoughts. Very interesting indeed. But the movie was a bit too dark and Paul was too old and it failed to delve into Paul's issues with stopping the jihad.

Speaking of which, I was very interested to see the amount of Middle Eastern-style words and concepts in this book. I wonder why Herbert went this way. Did he study something in that area? Know the language? Associate desert with the culture? He's had a lot of jobs, so who knows (oyster diver! I'd totally do that). Whatever the case, I don't doubt that either research or experience had a hand in it.

I realized a problem that readers have with my work from time to time as I read one of the action scenes in the book. I had no idea what was going on because it was fast and used disembodied weapons and body parts. I didn't know who was doing what and thought, "Aaah, so this is what it's like to read one of my action scenes." Haha. It was a good lesson and reminded me that it was okay to slow down, add a few details as necessary, and be clear on what was going on.

It was a good choice to read "Science Fiction's Supreme Masterpiece" (as it says on my book cover). I'm not sure about all that, though most people have a pretty good idea what you're talking about when you mention Dune. Hey, Donald Maass (head honcho of an agency company) is looking for "the next Dune" so at least now I have a much better idea of what people are asking for when they mention it (you can't include the movie - they're never accurate enough). I don't think my work qualifies as the next Dune (not enough betrayal, economic conflict, and other elements requested), though I really would love to be able to portray the kind of scope Herbert did. Or Tolkien. I love the scope. I want the scope. I've been gathering up worlds and peoples since I was 13. When done right, I think it can bring in so much to a novel and leaves open so many more fun and exciting possibilities.

Problem with reading Dune? Now I have to read the rest of them. Just like with Hyperion. Great, more stuff to add to my already massive library list, hahaha.

Review of Dune

Currently: Oh I dunno. Something like this I guess.

Fuck It

The title pretty much sums up my attitude at the moment. Come to think of it, I don't think that's the first time I've used that title for this particular blog. I think I must have forgotten about the syndrome I adopted in high school when the need arose. The Fuck It Syndrome. Came in handy for things that shouldn't be obsessed over. Kind of goes hand in hand with Robin Williams' Fuck-It-All drug. Sweet.

Anyway, so what's the syndrome for this time? Once again, my story is annoying me. Actually, it's not really the story's fault (ok, so it's never the story's fault - it's my story so it's my fault. Fine. Picky, picky). While starting the whole thing was a huge, annoying pain in the ass, this time I've just been fussing over whether or not to include a specific couple of scenes involving two of my characters. Should I bother? Does it do anything for my story? Do I want them in there because they rock out?

I've been agonizing over this little conundrum for quite some time. Longer than I should have, truth be told. I think a part of that agonizing included, "Well how the hell do I change it if I leave it out?" I didn't know. So I was kind of freaked. I was rather used to it the way it was, and even though I enjoyed the scene, I still didn't think it was truly fabulous, so the "Do I want it because I like it?" question was only so-so. Sure I like it, but I wouldn't cry if I had to cut it either.

Things finally came to a head a few days ago when I got to stay up nice and late the way I LOVE to do because they cut back on hours at B&N. I get less hours which = less money, but it's a blessing in disguise because I get more time to write. But what the hell does that matter if I'm not even writing? Ah, here's the "Fuck It" part for you.

The last time I wrote a fanfic was when I went out of my mind and thought, "Why the hell not? It'll be short anyway." By the way, that fanfic has transformed into a great romance story for the future. Hoorah. Anyway, the other night I watched an early episode of Doctor Who and because I'm a complete nerd and think David Tennant is hot (ok, maybe not hot, but I'd be like a kid who was just told the candy store he's in is now his if I ever found David Tennant in my bed, or hell, even in my vicinity...God do I ever need to get laid. Honestly kids, this whole virgin thing is getting OLD), and went to bed dreaming dreams of visiting London and meeting him in a bar...ah I wish.

That morning I woke up and laid in bed for a while, pondering ideas. I don't know about other writers, but I tend to get some great ideas when I just lay there, thinking. Either at night or in the morning. I go through whole scenarios that way. That's exactly where a huge chunk of my current book comes from. An hour of laying in bed. So there I was, pondering a Doctor Who scenario for...God knows what reason. Come to think of it, I'm not even sure where it came from. I'd thought up a character before to hang out with him, but I'd never acted on it (as in wrote it down as a fanfic) though I know exactly where the whole kit n'kaboodle would go. But this idea. It was good. I liked it. It was violent. It had tension (hahaha - sorry, Seton Hill giggle), and I thought, "That would be fun." And then I got up.

I didn't do anything about it for a while until I went through the day thinking about it and realized just how much I wanted to sit my ass down and write it. Of course, those thoughts were tarnished by the thoughts of, "Well, I should be working out this Anna/Rilst problem." Finally, I remembered Mike Arnzen's class, and decided, "You know what? Fuck that. I'm going to write what I want to write." I got up and grabbed my red notebook (*drool* God I love that notebook) and started writing.

Aaaaaah. It was good. God it was so good. Words went onto the paper, endorphins flooded my brain, all was well with the world. Ok, so I don't know about the endorphins part, but it was so nice just to feel my pencil swirling over the paper in pretty little letters to make pretty little words. I don't care that it's a Doctor Who fanfiction and it's a waste of real writing time. In essence it is real writing time. It made me happy and hey, that's all that matters. I've been working on it instead of my story, but I don't much care. I have an entire week off and I have enough done already that I'm not under any crazy pressure constraints.

So yeah. Fuck it. >=)

Currently: Take that bitches!

"Did you just make a yummy sound?"

Read the Review

Thanks stomach flu! *blarg* So above I have my "professional" review of the book. Haha. Professional. Whatever. Anywho, that contains half my thoughts on Frankenstein. Yes, Mary Shelley did a good job. Skillful writing, descriptions you can sink your teeth into, and a vocabulary I wish I had. Ah, to have lived during that time. Then again, had I lived during that time, I wouldn't be writing what I am now (well, who knows?). So what do I have to say here that I didn't say in my review?

Hah!

Aside from my continual disbelief that Frankenstein's creature (ok, you know what? I'm tired of calling him that. From now on, Victor will be Victor, and his creation will be Frankenstein. There.) is able to communicate so flawlessly, I have a bone to pick with Victor.

He is a selfish, selfish man. That's what I kept getting from him. Not in the very beginning, even when he's making Frankenstein, because then he's got this semi-wacked out haze going on in his head: "I can do it, I can make it, it will be fantastic, just think!" and so on. He's so bent on creation, he's basically forgotten everything else. A lot of people can, and have, done that. Though it was a selfish desire that motivated him. Glory, oh glory! Fool. But after that, it became all about Victor, in his mind at least. Oh, sure, he had his moments of "Oh William! Oh Justine! Oh Elizabeth!" and anyone else that had a moment of vulnerability to Frankenstein in Victor's mind, but otherwise it was aaaalll about him. Things like, "Oh how I'd hate to see that wretch [Frankenstein] again! How I am so miserable! Woe is me! I wish I'd never created that abomination!" Yadda yadda yadda. Now, I can understand falling into a guilty depression of Dear God what have I done? This is all my fault! But the man was so consumed with his misery, he didn't ever seem to take into consideration the misery of those around him. Did he ever think on how to solve the problem? No. Did he ever confess his crimes? No (well, once to the judge and then to Walton, but those don't seem much like confessions to me). Even when he thought on death - "Why did I then not die?" - to me it seemed selfish. Sure, your misery is so bad, you think you should just die in order to be free of all the pain. But what about your father, fiancee, brothers, and others around you? And what about Frankenstein? Hmmmm?

I think the height of his selfishness (to me) appeared when Frankenstein said, "I will be with you on your wedding-night" and Victor immediately thinks, "He means to kill me then." Victor may be a genius, but the man has no sense. Take a moment; you'd just refused to create a mate for Frankenstein. Franky's already killed three people close to you. He seeks to make you miserable the way he is; alone. He plans to pop up the night you're married. Just WHO do you think he plans on killing? It doesn't take a rocket scientist. Yes, yes, I know, if Mary Shelley hadn't written the book this way, it may not have gotten to where it needed to go, but I think it's entirely possible for Victor to have known better and still failed. Heck, he can never flippin catch Franky anyway.

There were a few times when Victor managed to get his head on straight and think in the right direction. First when traveling with Clerval and panicking in thinking that Frankenstein might pop up and kill Clerval. Then when pausing to think on what might happen should he finish making a female version of Frankenstein. That was a good, solid train of thought.

Victor is also a fool because he never fully understands just what he has done to Frankenstein. Sure, he listens to Franky's story, but he doesn't truly listen. Franky, in my eyes, really did have promise. Sure, he's a freakish thing in terms of appearance, but consider how often he tried to be good, tried to be useful, and appealed to the better sides of mankind. I'm not defending him when it comes to the murder he does, but I don't doubt that without proper education of morals (despite what he might have heard and read before) and love from the one that made him, he could have turned out much differently.

So, what about the book as science fiction? It's nice to read something from very early on, just for history's sake. Helps one to see how writing and content has evolved since then. Content seems to have continued on the same course. This could have been written now and still rocked the house. It would have to be written differently, of course, as not naming Victor for so long (as mentioned in the review) would bug a lot of people, and having so little dialogue and mostly narration could turn people off. Then again, who knows? The book is still in print, isn't it? Except now it's read as a classic (sometimes a necessity depending upon the classroom teacher that decides to stick it into a lesson plan) as opposed to the stuff on bookstore shelves that others consider mindless sludge. "All that sci-fi nonsense. It's so lame." Actually SF has a better rep now, so maybe not. It always depends on the readers.

Come to think of it, we've redone Mary Shelley's Modern Prometheus story already. Take a look at one of the many AI stories out there. Funny. The things we make always tend to turn around and destroy us, oftentimes because we fail to teach it correctly or reject it and attempt to destroy it, which then leads to the creation attempting to save itself. And what about superiority? Well Frankenstein did inform Victor (who was already quite aware) of his abilities to survive through much more than any human ever could. Small amounts of food, extreme heat, extreme cold, etc. Victor wanted to build a superior creature - he did. In SF humans wants to build better robots - we do. Scary.

When our modern-day, metallic Frankenstein finally wakes up, I don't think it'll be here. I'm willing to bet it will be in Japan. I'm telling you, they need to stop with the smart robots, but will they? Noooo....


Currently: OMG RLY? (slightly spastic for no reason)

Strunk Has Style!

The Elements of Style by William Strunk and E.B. White, as we all know (at least, my residency posse knows), is a tiny book filled with nuggets of gold for writers. That can include everyone, if you're still in school working on college papers and whatnot.

The book is the smallest grammar/style book I've ever encountered, due to (ah, now here I almost wrote "the fact that" - Strunk would be hitting me in the head with a ruler) only a certain number of "rules" listed. Where to put a comma, a semicolon, how to handle yourself with apostophes and so on. I have another grammar book leftover from a creative writing class that lists more usage rules for em dashes, puncutation inside and outside of quotation marks (which I wish Strunk had addressed), and other such items. You get the idea. There's also a nice list of words; how to not screw up allude with elude. Again, you get the idea. If you remember those Mead folders with all the junk on the inside, you should remember the English one with the list of commonly confused words.

But enough about what's inside the book. What about it? It's good (what did you expect?). Strunk wrote this for his students, something I thought was a fantastic idea, and when I started to think about it, I wondered why I'd never heard of the book before. I think everyone in my high school English classes could have used this book. Especially since our teachers (except a one of them) didn't do jack to teach us. It's amazing I love English at all, considering much of the time was spent either watching movies or filling out sheets of busy work. Or doing nothing. I recall doing very little in my senior English class. Right, so I don't get on a rant about poor English teaching, back to the book. Strunk chooses brevity over wordiness, a good idea since wordiness can kill a sentence. I loved some of the ideas he put down on ways to cut out unnecessary words and phrases. I was happy reading, knowing that many of these things I was already doing through choice. You know, that feeling of "That just doesn't sound right" before you reword a sentence? I think a lot of us tend to do that, not because a teacher told us to, but because it isn't hitting our ear right. We want ear candy. Ear candy!

I did feel a bit ignorant when reading words like "gerund" and "participle" and other grammar terms because I couldn't remember what they meant. Ok, shut up, it's been years since I was in a 7th grade English class learning these things. Even then the lack of enthusiasm the teacher had made me drowsy and I couldn't ever stand picking sentences apart and graphing them. I always thought, "This isn't right! A sentence shouldn't be subjected to this!" I was too busy being indignant on the sentence's part to accept what I was supposed to be learning. Now that I sound like a bad student (wasn't, really, I aced the class, but our teacher needed a vacation or to spice up the class somehow). ANYWAY, to get back on point, I had to go look up what some of those meant, only to find out later that (duh) there was a glossary in the back of the book. I laughed to myself and hoped I wasn't the only one who needed it.

I wonder who put it there - Strunk or White? Either way, good move.

I only borrowed the book from work (yeah, again I look like a bad student, I didn't buy it right away, but I have learned that when I do, I'll opt for the paperback instead), but it's on my list o' books to buy. I have no shelfspace (no, seriously, I don't. But I am the God of Organization, so I'm sure I'll be able to think of something), even though I did find a great deal on a pristine copy of Word Painting by Rebecca McClanahan. Yeah, my description has been sucking this time around. I think this surprised one person at residency who had my submission piece. Looking at some of my other works, I don't know what's going on. I have some lovely similes and metaphors.

Strunk and White, eventual revision buddies.

Currently: Whoo!

Weirdly Ironic

I first heard about Nineteen Eighty-Four when I was in college. How we were headed that way. How scary it all was. I was intrigued. Since then I heard other things about it. How well it was written, etc. It's been on my "To Read" list for a long time now.

So I've finally read it.

Easily, I can give all those who praised it for skilled writing their credit because it was crafted very well, despite the few times when the hero would lapse into a memory and at some point I wasn't sure if I was still in the memory of if I'd reverted back to the present. It's still better than what I've produced, and likewise Orwell gets plenty of kudos for making something like this during 1949. Not for the content, as that sort of thing is still around, but more the futureness involved. We still don't have telescreens and the closest we've come to making one could be the little camera you have on your computer where you and your friend share real time video of one another. Considering the way telescreens are used though, that's a good thing.

When it comes to people freaking out over the government and the whole "Big Brother is Watching You" thing, they fuss over telephone conversations and emails. Now while I don't see us headed in that society as of yet, or in the immediate future either, I can't believe people ignore the other restrictions the government wants to put on us. People fuss about privacy. There's no telescreen in your house yet, but what about saying what you can and cannot consume/do to yourself? Cigarettes are barred from public places statewide. Yeah, ok, yammer on to me about cancer and while sure that's a possibility and the government wants to keep us all safe from secondhand smoke, consider also where it stops? Hmm? I read an article once about a consideration on taking Coke and Pepsi machines out of schools just to keep kids from getting fat. Are you serious? Whatever happened to conscious, intelligent thought? Don't want your kid chugging down suger-filled drinks? Don't give him/her money for it. Sure, he/she might get money from a friend, but face it, that friend isn't going to keep supplying them forever.

Here's one thing that always freaks me out. I'm a chocolate junkie. There's a really bad movie out there named Demolition Man where things deemed bad for you are outlawed. Chocolate is one of them. In this book, people get chocolate rations. You know what I say? Fuck that. The day chocolate is restricted in any form or fashion is the day I freaking riot. That's when you know things are getting way out of hand.

But back to the book. In some ways, I found myself disappointed. First because of the content. I expected something like The Giver or Fahrenheit 451. But a lot of it turned out to be exposition that no doubt contained Orwell's concerns at the time. That's all very fine and well, but it takes things down a notch when you have different expectations. It's just that everyone all giddy about it gave me that initial impression. Ah well.

Second is the end. I accept it, but I'm not thrilled by it. I guess that too is Orwell's thoughts on the subject. That "they" win in the end. Well...hopefully not. The whole world was like that? Eech. You get just a couple glimmers of hope throughout the book only to have more rhetoric take over and then whump. The end. Hero loses. Game over. Unless you read the appendix like some critics do; as the subject content is written in the past, it implies that Winston, the hero, was indeed right, and the Party fell. One may never know...

That's my take on it as fiction. It's still quite good, the fact that it freaks people out, not just as in "Ohmigod, that could happen to us!" but instead as politically dangerous and thus getting it banned from libraries and such. Well, well. More power to it then. The more a group rejects a book, the more I tend to rally behind it. Especially if it's a ridiculous claim *coughHarryPottercough* and people start chucking books into fires. Nazis.

You know what this book did remind me of though? V for Vendetta, totally. At least in that movie we get to see what might have been the results of the rallying lower class.

Ah well, hat's off to Orwell. I'm tired.


Currently: Blah.

P.S. I forget what's "weirdly ironic" as my title says. I'll be sure to come back and mention it if I manage to remember...

Read my Epinions review on Nineteen Eighty-Four.

No more balking!

Swain's book is good stuff. He breaks down a lot of the pieces that make up a novel, and alerted me to things I'd never thought of before. I'd like to list them, but there are too many (ok, here are some; character drives, beginning help, ending ideas, an unhappy Unconscious and so forth).

I should have brought sticky tabs with me to work so I could have marked all those spots. No matter, I don't have to return this book until December so I can have until then to skim some of these ideas again and get them more firmly lodged into my brain. I liked how he not only included writing methods and items to look at, but also preparation for writing, locations to write, and so on. I've read some writing books before, and none of them really put it as well as Swain does. He mentions that if you have a window, you're likely to stare out at the world beyond it and forget about writing.

....Ok, this is in no way a joke, but I have a window practically in front of me, and I was just staring out of it. Yikes. Then again, I am running on very little sleep so...

Another thing he mentioned that I thought was absolutely fantastic and I've never read in any other writing book: Get out and exercise! Do you know how good of an idea this is? I mean, just a nice walk around the block can help clear your brain. I go with my mom to the grocery store - I just did yesterday, in fact, in order to keep my brain from completely melting. Of course, I end up with a container of Chips Ahoy Cookies beside my desk, but you get the idea. Anyway, I thought it was great he mentioned that and I think a lot of writers would benefit from it. Otherwise, what? We'll all get slobby in front of our computer screens (or in my case, a notebook). Haha. Ok, maybe not necessarily, but do you know how many ideas and scenarios I've gone over in my brain while running on the treadmill to some good music? I once read that most writers get their ideas in the shower. ...Shower? I have never once had an idea in a shower. I've even considered this information and made a point to think about my stories in the shower, but I inevitably start thinking of something else totally unrelated. And hey, if you do get ideas in the shower, then you can hop in after you get a bit of exercise and have a double think session.

Of course, unless you live in a world during 1984, then doublethink is a bad thing...but that will have to wait until another blog entry!



Currently: Inspired

By the Way

I forgot to mention two things.

First, when it comes to the end of the world through our own destruction (and by that I mean human error - and that error could be anything, from overpopulation to developing AI that becomes self aware and freaks out on us), I think SF readers and writers will make it out alive the most. Why? Because those who can imagine the all-too-logical AI: "Humans destroy the planet, thus they must be destroyed themselves" or be able to realize the fact that we might totally ruin our planet (Al Gore does not count, I don't care what you say, that guy is an idiot. Did you hear his speech? The beginning of it made no sense for God's sake) are probably the ones that will see it coming the quickest. We'll look at the rest of the world and say "Fuck this" and move to places like Colorado or Wyoming and live where it's quiet and end up going back to hunting and stuff to survive. So yeah, when you watch movies of post-apocolypse type stuff, those survivors are genre readers and the people that got lucky.

Ok, not necessarily, but come on. When's the last time you read a SF book or even watched a movie and thought, "Oh crap. We're headed that way aren't we?" Some of the stuff that went down in The Fall of Hyperion didn't surprise me at all. Think of yourself as plugged into the Internet 24/7. I mean like, literally. A little wireless Intel Processor in your brain. And after centuries of this, people suddenly get cut off from it? Hell yeah there would be people that would go insane. Then there's 1984 but I'm not going to get into that quite yet. Waiting until I read enough of it to truly go on a tirade of some sort.

The second thing also has to do with (naturally) The Fall of Hyperion. Maybe it's a moot point, or not even really a point, but it made me smile...chuckle a little. Not in a happy way, but more of the ironic sort. As in, "Why does that not surprise me?" Here's the passage that did it, and by the way, for those of you who've never read the book (probably everyone reading this), this takes place at least 700 years into the future (probably more), so we're at the year 2694 or so, and the only means of world connection (ship travel excluded) has just been destroyed, thus cutting all worlds off from one another:

"On Qom-Riyadh a self-appointed fundamentalist Shiite ayatollah rode out of the desert, called a hundred thousand followers to him, and wiped out the Suni Home Rule goverment within hours. The new revolutionary goverment returned power to the mullahs and set back the clock two thousand years. The people rioted with joy."

I'll leave you to think about that yourself.



Currently: Feelin' Magical

So is the Shrike dead or what?

Back in June I read a book entitled Hyperion by Dan Simmons. It was required reading by the program just as the romance book Bet Me is required this time around. Hyperion is pretty hard science fiction reading, something that actually surprised me because I enjoyed it so much. Up until that point I'd been pretty convinced that I wasn't a fan of hard SF. Now I think it's just like any other genre; some books have it, some don't. I guess I never should have thought anything in the first place because I'd never really read any hard SF, so technically, I had nothing to go by.

Anywho, that book ended on a "to be continued" note, so naturally I decided I had to read the next book. How could I not? I mean, come on, you're talking to the girl who reviewed over 50 volumes of Inuyasha and a ton of Fushigi Yuugi like a loser. Basically I finish what I start, and besides, since I enjoyed Hyperion so much, I figured I'd probably enjoy the next installement.

Good times.

Granted, sometimes Simmons will ramble on with tidbits of information we really don't need, which I'm sure could pare the book down by...probably a decent number of pages, but oh well. To me, it never really gets excessive. Mostly because somehow he manages to make it seem relevant and it doesn't get too boring or repetitive. Compare that to Jane Eyre and the entire page dedicated to how blue the sky is. Ok, I get it, move on please. Yikes. The techno-babble never bothered me because it settled in so nicely to the rest of the text. There were a few places where I thought, "What?" but not many and they didn't seem to major so that if I didn't fully understand it wasn't any big deal.

For a brief moment in time, when I read that the AI's "God" was at war with a human developed "God" I almost laughed in an "Aaaah, you've got to be kidding me" way. Something like that meant that after hundreds of pages, everything boiled down to a hyper-detailed and elaborate version of humankind vs. artificial intelligence (that we created...yet again. Why are we always doing this? You'd think humankind would know by now). But there's way too much going on for it really to be trimmed down to just that. Even if it sort of still is. If any of that makes sense. Mostly because it's not so much "robot vs. human" like in Terminator or The Matrix, but that on a higher plane of existence. Strange, but that's the best I can describe it.

It was a wild ride, though I have to say, I was getting a little....maybe not annoyed, so much as "Get on with it!" Monty Python style with the whole John Keats thing. Is Dan Simmons obsessed with John Keats? Did he write some graduate dissertation on the man or something? Having poetry laced throughout this kind of SF book was a little weird, occasionally annoying, and sometimes fitting. For example, the giant AI personality speaks in verse at several points which was both annoying and yet in some ways fitting. I know a lot of people would roll their eyes and think, "Lame. Why is an advanced AI rambling in poetic verse?" Yeah, I tend to agree. However, the simple fact that I've never heard of or encountered any other AI doing so gives this an interesting twist. Then again, as I've said before, I've not read much in terms of hard SF, or anything that's ever had AI in it either.

There are still plenty of questions to be asked. What happened to all those poor bastards on the Shrike's thorn three? How many Shrikes are there? What was up with Brawne's air-walking and Shrike killing? And the whole time traveling thing makes me feel like I was just in the middle of some really bizarre episode of Doctor Who. But concerning all the weird stuff that went down in this book, I tend to agree, or at least apply the Doctor's concept of time as being just a big ball of wobbly...stuff. Certainly seems that way here.

Of course, I'll have to read the next book. Yes, that's right. The craziness keeps on going. There's Endymion and The Rise of Endymion to go through. With this thing going through crazy AI, humans, semi-humans, non-humans, portals, time travel, Gods, and other totally off the chart I-don't-even-know-what, how can I not read the next couple of books? Besides, I want to know who wins the war, that the real deal is with the Shrike, and what this supposed message is that is so universe-shattering. ...I'll bet I'm the only one out of the whole residency group that plans to read all four books.

Hey, I told you I finish what I start.

And by the way, the cover art for this book sucks. That Shrike is not scary and dammit, the thing has four arms, not two! Does no one tell the artists of this? Becuase I don't think it had four arms on the first cover either, but that one looked a little freakier at least...




Currently: BLEH!

Techniques and a bit of Hyperion

I realize I never really did finish talking about my previously read book about SF history and whatnot. Guess I'll finish that before going on my next ramble.

In a nutshell, I was disappointed. I was hoping for a good, strong SF history chunk and instead got...well, truly, I'm not sure what I got. Not a real, clear history lesson, that's for sure. Expectations made the text hiccup; I was hoping for [this] and instead found myself reading about [that]. The fact that he drifted a lot didn't help. One minute we're talking about 1984 and the next it's something about Star Trek.

Fine, whatever, I perservered. I finished. Book's back at the library. Clean cup, move down.

I'm nearing the end of Techniques of the Selling Writer by Dwight Swain now. Actually I'm reading two books at a time - I've been slowly chewing on Techniques and just recently plucked out three other books from the library (because they were finally available - though I might as well just buy them, truth be told). Some people might worry that since October 25th is nearby, I'm taking a risk by procrastinating. Psh. Obviously no one knows the way I function. The Fall of Hyperion will take me 5 days max. Judging by my current speed, that's about right. 1984 will take much less - 2 days, 3 max. But back to Techniques.

I have to admit, sometimes I zone out and will read through a page without really reading it. Annoying because then I have to reread it. Sometimes I don't because I've caught enough to fully grasp what Swain is talking about and realize, "I already know that." But of course there are oodles of ideas and things he's mentioned that I've either had trouble with or never thought of in that light.

For example, I've always had issues with time. In my previous books it wasn't a worry because things naturally progressed quickly. Days were just fine and dandy as something interesting would happen each day (sometimes night) and I never had to worry about "3 months later" and so forth. It wasn't until book #1 that I had to plan out days. Anyway, before I get too off track with other books that need polishing, Swain pointed out a great way to bridge that span of time. Slip it into the middle of a character's musings or current emotional feeling. That's the abridged version of his explanation, of course, but with his examples and whatnot I thought, "That's perfect!" And it seemed so easy too. Why hadn't I done that before? Doy, I was too preoccupied with the time factor I totally missed out on how I could gloss over it with just the right flicks of the pen. Not to say that the time isn't important, but it's a hell of a lot easier to slip it in so your reader knows 6 months have passed as opposed to trying to drag it out saying what went on these 3 months and then these next 3 months, blah blah, when it's not even important and all your reader sees is, well, "blah blah." I hate that extra crap.

I love Swain's style too. It's quick, to the point, and clear. I've always had trouble with the difference between "show and tell" and frankly I'd love to strangle both of those words, something I frequently have to do to my internal editor because she's back there poking a finger at my text saying, "Show, don't tell" and my description comes out like crap. Oh how I could go on about my description. But reading The Fall of Hyperion helps with that too because while Simmons can go overboard sometimes, he does have some good ways of presenting it. Better than myself, that's for sure. Swain also notes showing and telling and gives a few tips and explanations. His style is sort of like an outline (no, literally, it's like an outline with writing in between, it's rather great, actually), which keeps things orderly and helps restrain potential rambling, which after Hartwell, is really nice.

Something he mentioned near the beginning of the book was "Grammar as a fetish." I thought that was brilliant and giggled. Too many people can get stuck on perfect grammar. Personally, I love a good fragment. I don't think I've used any in my current book, but I know I have a lot in book #2, all intentional of course.

His section on beginnings is rather helpful because of my current fist-shaking at my own beginning. What to ditch. What should be important. Cutting and flashbacking. Other concepts to make sure the reader doesn't say your book is garbage and puts it where the rest of the garbage is. I think what he had to say will help give me a better beginning. More interesting. Less backstory since much of it is indeed inconsequential to the reader. One thing he mentioned is along the lines of "What may be important to you concerning backstory isn't always going to be important to the reader." Even if I need it to make my world work, they probably don't. Keeping that in mind makes cutting down a lot easier. Adding to that is The Fall of Hyperion's description and the fact that it gave me a few extra ideas that could be fun to include in the beginning (again, working with description and not just offering readers some lame, punch-out postcard crap). I feel much better about this.

Haha, my mentor Anne Harris warned me that Swain is a little sexist. Or maybe not so much that he is (was?) but that the book kind of is since it was written in '65. There are several places where, yeah, I can see it. Hahaha. I don't mind, of course, as long as I'm getting good advice. But it is kind of funny. Women tend to be leaving or cheating on their husbands, and the hero is always a guy. Sometimes I'll hit on something that's obviously guy-sided, but I just smile and shake my head. And I'm not all that feminist either, haha. Still, it's good stuff and I've already suggested it to a few people because he's got some handy points.

Cool beans.

Currently: Feelin' magical.

Outlet

Ok, I need an outlet and since this was originally a writing blog (temporarily a reading journal for grad school), I'm going to use it.

I'm pissed. That, in short, describes what is going on with my story. It's pissing me off. I've never had to work this much to get past something, I've never had to muscle through so many chapters before when compared to the past 4 books I've written. Maybe it's because this time it's serious, this time there are deadlines, this time once I'm done with grad school there isn't any more school and I've got to either sell a fucking book or I don't know what. That's a slight understatement, but you get the idea.

I have a headache, even now. I've read my mentor's comments, and the shitty thing is that I already know I have an issue and I'm having problems getting over it. Here's the thing. I want to start from Point A: Humans discovering portal and get all the way to Point B: We help to win a huge planetary war. The problem isn't so much the idea, it's just that there's so much boring bullshit that occurs following Point A that it's hard to get to the good stuff that leads up closer to Point B. Humans learning this and that, smalltalk to get between little conflicts that are so minor they don't even have much reason being there. Again; pissing me off. I've waded through the boring stuff before, but it's been okay, necessary boring stuff that doesn't last too terribly long. The thing here is that I know readers would easily get bored and toss my book away in favor for something better where they can get to the meat much sooner. Hell, as a reader, I would toss my book away in order to get to something better. That can't be said for my other ones. Good stuff happens in them. Conflict arises quickly. Characters have issues to work through during said conflict, blah blah and all that good stuff. Here they're just wandering around like a bunch of idiots. NOT what I want my characters to be doing.

So I finished a brief "Adjustment" list which basically is a short version of how I'm going to revamp my story. I'm going to be cutting the shit out of it, that's for sure. Fuck the prelims, fuck all that boring crap and rambling useless nonsense. I'm going to put the trust into my readers and characters; that the readers will understand and my characters will do their thing without a lot of explaining. I'm getting too bogged down with info dumps or stuff that is info dump-like. Time to smack them around, toughen them up. I'm tired of muscling through this thing and being pissed off that nothing is going the way I want it to.

Time to make it go my way and have a bit of fun.


Currently: Fuck you story!

Haha, Los Angeles sucks

While Hartwell managed to stay on task for the most part in the next few chapters, in chapter 6, "Where Do You Get Those Crazy Ideas?" he started to wander again. With that chapter title, his wanderings didn't make much sense. Going into it, you're going to think, "He'll talk about places authors get ideas" and instead he begins to go on about what ideas can do and the purpose of ideas etc. etc. and sort of leaves the wondering reader in the dust about idea origination. I think he could have easily gotten away with it had he just named the chapter something different.

I did like the phrase "Science fiction writers are like magpies." Collecting all sorts of random bits and pieces of information and what might seem like junky trivia to others. I do that all the time. I have all sorts of random "stupid" things in my brain that are just waiting to be used. I think this can be attributed not just to SF writers, but to a lot of writers. Tell me the fantasy writer doesn't soak up crazy information or the horror writer isn't collecting bits of something that might make for one freaky-ass story later on.

The chapter on the use of the term "science fiction" was good. I'd never really thought about it before, but it is kind of oxymoronic. Sort of like creative nonfiction. Haha. The problem is that people automatically think infallible facts with science, and that's not always true. Scientists get their theories disproven all the time, so science is more like the search for truth rather than truth itself. Therefore, I see nothing wrong with science sitting next to fiction. Especially since science fiction writers have come up with ideas that have later become reality, hence the reason the government started asking for the help and creative minds of some science fiction writers. There was a whole article about that, which I thought was awesome.

And yeah, once it becomes reality, it's no fun anymore. Of course, I tend to think that in that moment when fiction is no longer fiction and that invisible vest is actually functioning on a human being, both SF and science are totally kickass. After a while the elation will fade off, but I'll still think of how cool it was when it became real. Execept now we can't write about it like we used to, but oh well. I like to think that will keep the genre fresh and force new ideas to arise. And anyway, you never know what will come next. I remember when they thought they would never invent the gigabyte. Hmm.

My computer has 78 GB. (I could have had around 200 but I didn't have the money at the time).


Currently: Just kinda normal

Wait, what was that again?

So I'm on my next book, Age of Wonders by David Hartwell as my sort of history book for science fiction. I thought it would be cool getting into science fiction's history because even though my current novel is science fiction, I've read little in the genre (seems counter productive, I know) and figured knowing some of it's roots would help. I'm a little more well versed in fantasy, which would make sense considering that's what I do most of the time anyway. This is my second large science fiction idea, and I thought it was interesting how almost all my short stories were science fiction instead of fantasy....

Anywho, Age of Wonders. I'm trying to get it out of my way so I can devote my full time to Harry Potter, which may be a mistake because I'll probably start hearing all sorts of things about Harry if I'm not careful. I haven't read a lick of it yet and I know once I do I probably won't be able to stop. Like me and a bag of Chewy Chips Ahoy cookies. I'm still not very far yet, and I blame the book, actually. Ok, I should blame myself, but up until recently, Hartwell's writing is sort of like mine actually, although I tend to think my ramblings digress a little before getting back on track and it's a little hard to get lost.

Ok, see, Hartwell's book isn't exactly a history book. This is good because it means I'm not going to be drooling on myself while I go through dates and facts presented in an uber-boring manner. Instead he's upbeat, obviously interested in what he's talking about (as he's a SF writer as well), and knows his stuff (and if he didn't he looked it up). Therein lies a bit of the problem.

Sometimes I think he got so into what he was talking about he just sort of...kept...talking about it getting to a point where I was sitting here thinking, "What the hell does this have to do with the chapter?" While I give it to him that perhaps he found his rhythm in the third chapter because it actually follows a line of thought and stays on topic, the first two just started to bug me. The first chapter was called "The Golden Age of Science Fiction is 12" and while I was able to grasp what he was going for (and I guess that's what's important), once he was done talking about omnivorous SF reading behavior, he started babbling about specific authors and what they've done. This may be a problem because he's set in his time (80s) and it sounds as though he isn't planning for future readers. More like this book was for the current audience of the time. I wasn't born until '83 so I wasn't likely to read this book anytime soon.

He does it again in the second chapter, "I Have a Cosmic Mind - Now What Do I Do?" Come to think of it, I don't think he ever really answers this question. Maybe suggests books to read, but if you were an outsider of the SF genre and read that chapter, I honestly don't think you would be any closer to knowing how to handle your newfound reading world.

What I do credit Hartwell with is the way he describes SF people, reminding any non-SF person that, duh, SF people are just like you except for their enjoyment of SF. The guy at the water cooler, that woman in the grocery store picking out apples, your boss, who knows? Kind of helps kill the stereotype that all SF people speak Klingon or sit at their computers and get fat and think that the government has covered up an alien crash. Blah, blah, blah. Whatever. Truth is, that isn't (always) true. Most are the everyday people you see, just with an internal sense of, as Hartwell puts it, wonder.

I have a little problem with his attitude toward Star Trek though. Now, I'm not a trekkie and I've probably only seen a handful of episodes and yes I do realize what the show has done to the SF scene (both in good terms and not so good terms [all SF people are like trekkies]), but I don't take too kindly to Hartwell's condescending tone toward the show. I guess I can see his points and all that, and he's not horrible toward it or anything, but just the way he talks about it rubs me the wrong way. Like I want to tell him to lighten up on the show, give it a break. *shrug* Maybe it's just me.

I just hope he stays on track in future chapters.


Currently: I was happy but now I'm kinda bummed

Kids? Really?

One of the books I put on my list to read during my writing term (as we are required to read a certain amount) was The Time Machine by H.G. Wells. You know, the one about the guy that goes back in time? Meets the Eloi and Morlocks? Come on, it was made into a movie - twice.

Before I get into more details, I have to say I'm surprised at where I found this book during my search for it. Jobless and strapped for cash as I am, I opted for the library. I looked in two different places; the public library and the Penn State University library. While in Penn State's library it was just sort of hanging out, I was quite shocked to find that Schlow Library had it residing in the children's section. The Time Machine - a children's book? I recalled reading War of the Worlds when I was in 8th grade, but that doesn't count as a child's book, does it? (Difficult for me to really know, since this is the same girl who planned to read Gone With the Wind over Christmas break in 7th grade and didn't because it got checked out) I was even further confused about the choice when I actually started reading the book. I wonder what age group it's stuck in at the library because when I think of children's book, I think at most 6th grade and under. The concepts the Time Traveller talks about in the beginning are things I probably wouldn't have grasped too well until after taking geometry or algebra, subjects I didn't take until middle school and up. Time. Space. Fourth dimensions.

I also don't see the style as something a child would tolerate. We're being told a story by the Time Traveller (he's telling his buddies and we're sort of listening in). There isn't any back and forth dialogue, paragraphs can be long, and there just doesn't seem to be the sort of thing children can get into. Maybe I'm underestimating kids - after all, they are driving through 700-page Harry Potter books. However, those read much differently.

Anyway, having said all that, on to the book. Much better than the movies (though I only remember fragments of the first one), which both failed in terms of Morlock looks, Eloi looks, landscape, and just far ahead he traveled. Though I don't often read SF, (ironically enough - it's just that I don't know what's good to read and I'm not into the hard SF) I do find myself strangely drawn to the time in which Earth dies. I know, weird, but it's a fascinating thing to think about - mostly because I seriously doubt it will ever happen in my lifetime. So what would it look like? How would Earth change in the future? In the book the atmosphere grows thin, green plantlife dies away, and we're left with a barren, rocky landscape with a dying ocean and giant crabs roaming while the sun slowly fades or dies or whatever happens to it when it starts to grow red and...unless it was because of Earth losing orbit, falling into the sun.

When you can see something like that in your mind in such a bizarre way, do you know how scary that is? That's why people don't leave their lives for very long and think about our insignificance. You think ants are small, but we're just the same in many ways. Sure our brains are bigger, but what then? People kill each other over religion, but to what purpose? Will it all matter in the end of all things? When our planet slides closer to the sun and our kind die away - and we've lived only such a short time as it is, both as humans and as a country. Rome didn't last. Persia didn't last. How long before we go too? Maybe that's why we strive to live so much. How many shots do we get? I think that's why I go a little mad sometimes. Stuck in a house, thinking about how I have to get a job. Life is to short to spend it in a cubicle or selling bullshit clothes, credit cards, or other crap to people. Stepping outside one's comfort zone to think of the utterly massive amount of space and strange stars and things far and beyond is frightening. That's why I'd love to see it - do you know how thrilling that would be? Forget sky diving, the rush would be so much more intense, holy cow...

But, as usual, I digress. H.G. Wells had a great imagination, you have to hand it to him. I'm extremely fond of his description, a skill I think I need improvement on, and maybe even if I don't, there's no reason not to try making it even better. I simply loved the fact that he had the sun rise and set in the west at one point. I have a world where I really, really want to do that, but I didn't know if it was possible and had considered asking someone well versed in planetary movements. I feel a little better about the idea now, though I would still consult someone, mostly because if the orbit of the planet is going a certain way, I don't know if there would still be grass and living people on that particular chunk of land with the sun moving in that way.

Oh, and I chuckled a little at the beginning as they discussed space and time. About the present, past, and future. It made me start thinking about the original Buddhist doctrine (yay Buddhism class in college!) and how there is no Present. Just the Past and Future. As we are perpetually moving forward in time, there never is any present, and though the concept was difficult to fully grasp at the time, thinking about it in terms slightly different, it actually works for me now. Crazy huh?

“What happened to then?”
“We passed then.”
“When?”
“Just now. We're at now, now.”
“Go back to then!”
“When?”
“Now.”
“Now?”
“Now!”
“I can't.”
“Why?”
“We missed it.”
“When?”
“Just now.”
“When will then be now?”
“Soon.”
“How soon?”



Currently: Wishing I was in the Infinite