Category Archives: Character

Sunday Reads: 8 April 2012

Welcome back! Another week gone and here’s another 10 of our favourite reads.

 

Considering writing in first person? James Scott Bell discusses some of the pitfalls in First Person Boring.

Kidlit.com talks about drawing the reader in by Eliminating the Frame.

Time to start those rewrites? Writer Unboxed has a great post about How to Think Like An Editor.

Tim Kane has a cooking-inspired post in Layering Flavors In Your Writing.

AC Wise made me stop and think hard about my current manuscript with Heroine Quest, or The Fairytale Problem.

And while we’re talking about heroines, Marcy Kennedy discusses How To Keep Strong Female Characters Likeable.

Terrible Minds highlights 25 Lies Writers Tell (And Start To Believe In).

Over at Rock Your Writing, they’re talking about How To Build a Writer’s Support Network.

Jane Friedman outlines 5 Principles for Using Facebook.

Jody Hedlund has 3 Ways To Find the Perfect Opening For Your Story.

And James V Smith Jr explains The Dos and Don’ts of Novel Endings.

 

 

Self-consistency and Maintaining the Fourth Wall

When many, if not most, readers enter a fictional world, they want to stay there until they’re ready to leave. For us writers, that means having to avoid doing anything that pulls the reader out of our world. Failing in this task may make it difficult for a given reader to buy into our creation. They may set it down and move onto something else. If this happens, we’ve lost them.

Any aspect of storytelling is vulnerable to this. Someone breaking out of character, the introduction of a deus ex machina, and even poor handling of point-of-view are all good ways of infuriating readers, and rightly so: they are violations of an unspoken trust with our readers that the stories we are telling them are self-consistent.

Setting is an aspect of storytelling which is particularly vulnerable to this kind of violation, especially in genres where setting is important, such as in fantasy, sci-fi, and historical fiction (by setting, I mean all things related to world-building, such as culture, dress, geography, the laws of physics or magic, etc.). Read enough reviews in any of those genres and you will see that one of the widest criticisms is that the author described some event that could not or would not have happened in that context, and thus the reader was pulled out of the story. There’s a good reason for why this can be such a problem for a writer: setting, by its very nature, consists of a vast number of interrelated concretes. Consider the difference between a character arc and a city, full of people, buildings, roads, belief systems, cultures, and so on, and you should see what I mean. It’s very possible (and necessary) to track the shape of a particular character’s arc, but far more complicated to track the goings-on of every person and thing in a city. There are many ways we can forget a detail that affects the story later on, and thus cause one of those reader-losing violations.

Of course, simply not knowing how an aspect of your world works can also do this. Many of our readers are smart enough to know that you can’t ride a horse at a gallop while swinging a fifty-pound sword for five hours straight. As most writers should by now know, doing some research solves most of these problems.

But there’s another related issue that can be a little subtler, and it relates purely to a world’s self-consistency. Unless you’re writing an alternate history or time travel yarn, your Imperial Roman soldier isn’t going to call his wife on his cell phone, since cell phones didn’t exist back then. An obvious example, but things get a little trickier when you’re writing in a purely secondary (or, purely imagined) world.

I once wrote an epic fantasy story in which one of my characters was exhausted, and was described as feeling as if he had just run a marathon. While it seemed pretty innocuous to me at the time, someone in my writing group couldn’t buy into it, because the word “marathon” is named for the run of Greek soldier Pheidippides during the Battle of Marathon. And since such an event never occurred in my world, he argued, how would the concept of a marathon in the normal sense even arise?

Hearing his criticism was a bit of a wake-up call for me, and now I sometimes find myself watching out for the same thing with books that I read (as much as I’d rather just sit back and enjoy them). Of course, in my hierarchy of priorities, I’m going to put a satisfying plot over catching myself using the word “marathon,” but I still keep an eye out for something like that slipping in. Whether or not you’re that meticulous about your world’s etymology, rest assured that some of your readers will be.

* For another interesting post on the topic of word choice, check out the earlier post by Mignon Fogarty, a.k.a. Grammar Girl, if you haven’t already.

Take Note of Inspiration

Have you ever been out and about and something, could be anything, makes you think -ooh, that’s a cool story idea?  Did you write it down, note it in your phone, leave yourself a voicemail about it… anything… so you don’t forget?

You should.

I was in my local used book store and the clerk looked perfect for a romance hero.  I told him and he let me take a picture that I can now use that for inspiration.  I love that.  Sometimes, my boyfriend actually tells me things I think are perfect for a romance hero to say.  Yes – I write them down and save them.  They’re gems.  It could be a piece of dialogue you overhear, a character (literally and figuratively), an outfit, a setting, a feeling, a mood, a reaction, a hairstyle, a building, a show, or any of a million other things.

I hear a lot that ideas are cheap and this is true.  I wrote about it in my post Ideas are Cheap and Everywhere.  Now, I’m telling you… write them down!

We’re writers… it shouldn’t be difficult  🙂    

Take note because you never know when that idea will inspire something great.  Someone told me they only wrote them down if the idea wouldn’t go away.  I can see that.  If it’s persistent, then maybe it’s really good.

BUT, what if that tiny little nugget of an idea – like the enormous icicle hanging on the tree outside my window falling on someone’s head and creating a seemingly weaponless crime once it melts – is interesting to me today but when I look at it in a year, it inspires my next book?  You just don’t know.

I think if you have a fleeting idea, picture, scene, character – whatever – jot it down and every so often pull those notes out and look at them.  You just never know when a random little seed idea will spawn a complete freakin’ tree.

You have nothing lose, Fictorians, and everything to gain.  Write it down and see what happens.  Anyone already had this happen?  I’d love to hear.

Programmers, Hackers, and Technology

As a Software Engineer and Security Analyst, one of the things that always bothers me in modern media is how programmers and hackers are portrayed. There seems to be a common belief that they have almost magical powers to pull usernames and passwords out of the air or complete complex tasks in seconds. I know my complaint is common and that anyone in a specialized profession can share my angst, but I thought I would write a little bit on how it actually works. In order to maintain the tempo of your novel, you may be inclined to skip all my advice and use HollywoodOS (the fake Hollywood systems) but at least you’ll be more informed. I’ll try to talk about where we are and where I believe we’re going in the future.

Starting with programmers, we’re a group very similar to writers. All of our work is creative in one way or another. Most of us are given (or help create) a specification that defines what the finished project will be like. Consider this your outline that talks about each chapter and how the characters move around in it. And much like writing the pages of the novel takes time, writing a full application takes a while to code. This is changing even in our lifetimes, however. Frameworks exist that give the developer the ability to create fully functional applications in a short time. Consider this like having a library of plot snippets that you can freely take and insert into your novel. All that is left is to customize the look and flow between the parts. As this advances, I can easily see a future where “programmers’ just tell a system what they want, how they want it to look, and the resulting application is built for them.

Next we have the hackers. I will say that the term “hacker’ has many connotations and many of them are negative when they shouldn’t be. The word hacker itself is used to describe a group that enjoys the challenge of building new things. This can be that kid down the road that turned his wagon and lawnmower into an awesome go-cart, or even you as a writer. It also commonly talks about people who break software or computer security. Technically, this group should be called a cracker, but since using the term hacker to refer to this group is so common, I’ll bear it and follow suit.

Hackers have many different subsets and it’s hard to classify them as a group. I’ll touch on a couple of the subsets here, but I can’t touch on all of them. First, I’ll talk about the lower class members commonly (and usually derogatorily) called script kiddies. This group attacks using software or scripts obtained from various sources. While their methods are effective, they often do not understand the full mechanics of the attacks they are carrying out. They are quick to take advantage of systems that are out of date and not very well maintained, but are unable to penetrate well maintained systems that may not have any vulnerability already exploited. I wouldn’t be surprised if there was a well organized group that gathered and used these scripts as a form of cyber-warfare.

The other side of that coin, and in my eyes the elite group, are the security experts. These are the members who write the code and find the exploits that the other groups use. This group looks the systems and start prodding them to try to figure out how they work. The simple way of looking at this group is like a spy attempting to enter an enemy’s base. They first scout it to determine how it’s configured and look at all the entrances. With enough information they can pretend to be someone else and walk through the front door, or learn the weak points and attack there. Most commonly, unlike the movies would have you believe, this process does not involve the user sitting at the login screen trying to guess the password. They involve lots of surveillance, analysis, and a great deal of luck.

There is one final group that should probably be included and that’s the social engineer. This is probably the most common type of hacker in television and tv. The social engineer doesn’t look at exploiting the computers, but rather the people who work on them. A social engineer attempts to deceive the users to give them information that can then be used to access the system. This information can be usernames, passwords, secret information concerning the infrastructure, or even just access to the secure systems themselves.

While this only briefly touches on these technological roles, I hope you find them useful in building your characters and perhaps making them a little more realistic. If you have any questions or comments, please ask them below!