Tuesday, July 16, 2013

Not So Despicable

2010 was a great year for animated movies: Toy Story 3 (which made me cry), Despicable Me (which made my wife cry (which is not to say that TS3 didn't make her cry, but it's much more impressive to make me cry at a movie than her)), and Megamind. So, although we really loved Despicable Me when we saw, it still got overshadowed by the other two. Meaning we own the other two, but I never bought Despicable Me despite the incredible voice work by Steve Carell. I feel bad about that, now.

Which may seem kind of silly, to feel bad about not buying a DVD, but, really, we all, the whole family, loved Despicable Me. When it came out. But, see, the news of Despicable Me 2 didn't really do that much for me. It was kind of a shrug and "oh, yeah, that's cool," but I wasn't dying to go see it or anything. I'm sure that's because we haven't watched it again since 2010, and I'd forgotten how good it was. My daughter, however, was dying to go see it. I'm pretty sure she wants minions of her own.

So we went to see Despicable Me 2, and I'm pretty sure it's the best movie I've seen all summer. Okay, second best. Star Trek beats it but not by much. At any rate, it was so much better than Monsters University, which is its actual competition. Not only was Despicable more funny than Monsters, but it had all of the heart and soul that Monsters was lacking. And it made my wife cry.

I don't actually have anything negative to say about the movie. The closest thing to a negative is that the plot is almost conventional, but, see, it's only almost conventional. The fact that there is an attempt to recruit Gru to the AVL (Anti-Villain League) at the beginning of the movie, because of his expertise as a former villain, puts things just off-kilter enough that you don't really know which direction the movie is going. And I won't tell you which, because that would just spoil it.

And, I have to say, that scene where Gru is on the phone with the people who failed to send the Fairy Godmother to his adopted daughter's birthday party... well, that was classic. As a father, I've made those calls, and they had that bit down perfectly. All the way to the hanging up and... well, that, also, would be telling. But there are so many of  those moments incorporated into the movie that it made it great for kids and adults.

The animation was terrific. The voice work from the actors was excellent. The minions were funnier than ever.

Wait, now that I think about it, there is one issue with the movie. The title. Because Gru isn't so despicable anymore. I can't wait for a third one, and I'm gonna have to make sure I pick up both of these movies, now. It's great stuff.

Sunday, July 14, 2013

The Hand of Neil

Let me just start out by saying, Neil Gaiman owns his very own copy of Shadow Spinner.
"What?!" you may be asking, "How is that possible? And, if it was, how would you even know?"
Well, give me a moment, and I'll get there.

Gaiman has, perhaps, been more influential on me as a writer than anyone else, but it's not his writing that did it. Which is not to say that it wasn't something he wrote; it just wasn't any of his stories. As I mentioned waaay back in my post 400 Words, it was something Gaiman said about Terry Pratchett that finally convinced me to put my pen to paper and stick with it. If not for that one thing, that thing that gave me my "ah-ha!" moment, I'm not sure The House on the Corner would ever have been written. For that reason alone, Gaiman is important to me.

More specifically, though, and I talk about this more extensively in the author's note for "Part Five: The Police Car," Gaiman's character, Corinthian, was one of the primary sources of inspiration for The Man with No Eyes. When I got to the point that I needed a villain for Tib, I sat down (figuratively speaking, since I'm sure I was already sitting) and went mentally through the images that have most freaked me out in my life. The Corinthian is one of those images. So Shadow Spinner was directly influenced by Gaiman and his work.

All of that to say, when I found out that Neil was actually coming to my little town on his Ocean tour (the last signing tour he says he's ever going to do), I was very excited. In my normally subdued way. Meaning, you'd never be able to tell. Sometimes, that particular attribute of mine frustrates my wife. I'm sure it's related to why caffeine doesn't affect me. Or alcohol, apparently. The fact that I don't ever even get tipsy also frustrates my wife. Anyway...

I went to see Neil Gaiman. He read a bit from The Ocean at The End of the Lane, he answered questions, he read a bit from Fortunately, the Milk (which is not yet out), and, then, he spent the next four hours or so signing autographs. I know, because I was in the last batch of people.

By the way, Shirley MacLaine once pulled his hair. That was a funny story. And Gaiman thinks that everyone should have a hobby that could kill them. His is keeping bees. I'm not sure I quite agree with that, the killing potential of your hobby, but I think it's cool that he keeps bees. I like having bees around, especially when there are enough of them that you can hear their buzz in the trees. Or rosebushes. Or whatever. But I'm not thinking I'm going to take up skydiving or bungee jumping or, even, bee keeping, at the moment.

Yes, Mr. Gaiman was as entertaining as you might imagine. His stories were funny as were his answers, including the one to the question of whether he wears a hair piece, to which he responded with something along the lines of, "If I wore a hair piece, it wouldn't look like this." He was also polite and gracious, even at 12:30am, after he'd been signing for all of those many hours.

Other than The Ocean at The End of the Lane, I got my (1st Edition) copy of The Graveyard Book signed for my son. Neil drew a cute, little picture for him:
And I got the first two issues of The Sandman signed.
No, I did not go out and buy them special for this event, as I was asked by more than one person; I've owned those copies since they were the price on the cover. [I wanted to get my platinum edition of Death: The High Cost of Living #1 signed, but I'm not really sure what box it's in, and, once I had my Sandman issues, I figured that was good enough.]

The other thing I did was hand a copy, signed to Neil, of Shadow Spinner to him, which may be presumptuous, but I did lead off with, "...this is not a request for you to read this." Which it wasn't. Not that I would be upset if he reads it, but who knows if he will ever pick the book up again. What I did want to do is give him something back that would not exist if not for him. The House on the Corner might also not exist, but, maybe, it would; I don't know. Spinner, at least as it is, would not. So I thanked him for his stories and the stories they inspire and gave him the book.

He looked a bit surprised and, then, genuinely thankful. He began to look at it, but someone came and took it away from him and put it in a box with all of the other things he'd been given during the evening, none of which were books. Then, he shook my hand very firmly while looking me in the eyes and told me "Thank you." It was... nice. But, yes, I have washed my hands since then.

So there you go. Neil Gaiman owns his very own copy of Shadow Spinner with his name in it and everything. Not that he couldn't just write his name in it if he wanted to, but... well, I'm sure you get it. At any rate, it's nice to get the chance to say "thank you" and show your appreciation to someone that has meant a lot to you, so, even if it was presumptuous, I took my opportunity to show my appreciation.

And, well, at the least, I hope he loves Rusty's cover, because it's awesome.

Thursday, July 11, 2013

The Religion of Writing: Part Three -- Speaking in Tongues

The debate over speaking in tongues, or glossolalia, is not a new thing. Sure, we look at some of the "Charismatic" and Pentecostal churches and the spouting of gibberish from their mouths while they writhe around on the floor and think, "Man, if that's what I need to do to get into Heaven, then leave me out." [And don't ask me why they're called "charismatic" or why it's the "Charismatic Movement," because I don't see any good reason for the usage of the term (and didn't feel like spending more than the 10 minutes I wasted not finding an adequate answer).] Trust me, I'm with you. Well, I'm with those of you that feel the way I do about it. [Because what I can say is that we don't have examples of that kind of behavior in the Bible. Paul never "sizzled like bacon" while letting nonsense drip out of his mouth.] I am not flopping around like a fish out of water or roaring like a lion or any of that other nonsense that goes on when those people are all being "slain in the Spirit."

Which is the heart of the controversy, actually, because "those people" say  they're not doing it by choice. They're being possessed by the Holy Spirit, and they just can't help it. However, it is what gets you into Heaven (according to them), so, well, it's in your best interest to get in there with them and lose control of your bodily functions.

Now, here's the interesting part (isn't there always an interesting part?):
There has been a lot of research done into glossolalia. Which makes sense, because, if it's real, if people are spontaneously speaking some kind of language they didn't previously know, it would be a mighty strong proof of God or, at the very least, some kind of supernatural phenomenon. Before I go on, there are two types of glossolalia:
1. The kind everyone thinks of when they think of speaking in tongues: speaking an unknown language which no one understands. This is usually thought of as speaking in the tongues (languages) of Angels.
2. Xenoglossy: speaking an actual language that the speaker didn't previously know. Like breaking out into fluent Mandarin without ever even having had chow mein or orange chicken.
Here's the first interesting part: Nearly all of the actual instances of glossolalia in the Bible are xenoglossy. During Pentecost, it was xenoglossy that was happening. Or, perhaps, reverse xenoglossy since it was the listeners that actually heard the speakers in their own language.
If you look in the Bible for an example of what we think of when we talk about "speaking in tongues," we get exactly what goes on these days: a bunch of people (in Corinth) speaking in tongues and boasting about it, "Ha ha, we're better than all of you." Paul had to send a letter telling them to cut it out.

Modern xenoglossy is completely unverified. There are sporadic claims that it has happened, but there are never ever any witnesses or proof or anything of the nature. Usually, it's something along the lines of someone coming back from China and proclaiming to have broken out in Chinese while he was there, but there's no way to know if it happened, since there's never anyone available to say, "Oh, yeah, that guy totally spoke Chinese to me." The few case studies have pretty much shown that xenoglossy was not taking place.

Which leaves us with the gibberish form of speaking in tongues. Study after study after study (after study after study) by both linguists and psychologists have shown that no actual languages are being spoken during these episodes. [I'm not going to get into the technical aspect of how they know that.] There is also considerable psychological evidence that these bursts of "tongue speaking" are psychologically triggered in order to conform to expectations. Like peer pressure. What this means is that neither God nor "the Universe" is talking to any of these people. It's all coming out of their own minds.

Not that you can convince them of that.

And, also, that is not to say that there are not or have not been actual cases of speaking in tongues. I believe that some form of xenoglossy happened at Pentecost. There were potentially thousands of witnesses, and the event is recorded in some extra-Biblical texts. And, sure, there is the potential of the other form of speaking in tongues being real, too, just not in big groups of people the way it is commonly claimed today. So I'll admit the possibility of these things but not the current actuality of them.

Which brings me to the writing part of all of this.

So many, many writers claim to get their stories from "the Universe," or some muse, or some source of inspiration that is outside of themselves. "It was as if the story was just given to me, channeled through me, whispered into my ear," or whatever other nonsense. I'm sure there's no more validity to this than there is in the whole speaking in tongues thing. The human mind is a wondrous thing. Infinitely creative. The idea that we are incapable of coming up with remarkable stories is... well, it's just ludicrous.

It's why it bothers me so much that there are people out there trying to disprove that Shakespeare wrote the plays he's credited with. The idea being that no one can be that creative. What? Did the plays just materialize? Spring forth from the aether fully written? Beamed down by aliens? As with a rose, why does it matter what we call the guy who wrote those plays? Someone wrote them, but, instead of just saying, "Wow, what a creative mind," we have people out there trying to prove that, what amounts to, no one having written them. It's kind of insane.

What I say is this:
If you wrote something, own it. I mean, really own it. Don't try to blame it on some outside force or influence. Take responsibility for it, good or bad. And, if it's bad, keep working on it and make it better. If it's good, say, "I did this! Me!" I don't see why it is that we have to always discredit ourselves and our achievements, like we're not good enough. And that's what you're doing when you try to blame your art on the "the Universe": discrediting yourself.

So, yeah, I will admit to the possibility that "the Universe" or the Force or God or, even, aliens may have influenced someone at some time to write something. Or paint something. Or make music. But, just like with speaking in tongues, I'm pretty sure it's not happening on any kind of regular basis. People are just scared to own their creations, because, like in mass "tongue events," society says pretty consistently, "You can't say that you yourself did a good job." But, not only that, society says that when someone comes along and tells us we did, we have to brush it off and say "it was nothing" or "I was inspired." It wasn't me.
What hogwash.

Don't be scared. Take credit for your work. If aliens want to send us books, let them send us the books. They don't need to whisper them in anyone's ear.

Tuesday, July 9, 2013

The Importance of Liking Your Own Work -- Part Two (an Indie Life post)

A couple or few weeks ago, someone said to me that one of the reasons that she likes my blog is that I know how to take criticism. That, of course, started me to thinking, and the first thing I thought of was the incident that I talked about in part one of this. The point of that is this: when you approach a topic (whatever that topic is, from an idea to a creation) from a stance of confidence, it allows you to take any incoming information (critique) and say one of two things:
1. Well, that's obviously not valid, so I can discard that.
2. Oh, that might be valid; let me look at it and see.
When you lack confidence, when you don't believe in yourself (whether it's an idea or a creation), you only have access to one of those options.

You can either discard everything (because you have to) and cling to whatever belief you have, even when you have nothing to back it up with other than dogma (as I was talking about here (which is not to say that that behavior is only about religion; it's not. It's just as common in politics or science or, even, dieting)). Or you accept everything that challenges you as valid and try to accommodate all of it, which can be rather tumultuous, like being battered by waves at sea.

For an artist, a creator, either of those can be crippling.

You get people, on one end, exploding all over the Internet about anything negative that's said about their work (of which I have firsthand experience) and people on the other end trying to incorporate every critique given to them, even when they conflict with each other. Neither person has any actual confidence in what they've created.

So what is it that allows someone to take criticism well?

When it's an idea or belief, confidence comes from knowledge. From having researched your position, looking at the different perspectives, and coming to the best conclusion you can from the facts at hand. When someone throws something at you that you've already researched, you can disregard it. If it's new data, you can go look at it and see if it changes your perspective. Either way, you're approaching the situation from an area of confidence (that you just wouldn't have if you've accepted your stance on someone else's say so).

When it's about something that you've created, at it's essence, it's the same issue. The key, though, is having created something that you like. If it's the way you want it, it's rather the same kind of thing as having done the research on an issue or a belief. So, if someone comes to you and says, "I don't like the way you had that fart joke in there," if it's something you like (and think is funny), then you can shrug and say, "That's too bad." Or, maybe, someone says, "Hey, what if this thing happened here instead of that other thing?" and, maybe, it's something you never considered, but, then, you can look at it and see if it changes what you've done with your story and see if it really is a good suggestion or not.

If you don't like all of your story or don't know what works or are too busy trying to write a story that other people will like instead of one that you like, you have no way of evaluating what people say to you about what you've written, because you have nothing to judge it against. If you can't say, "I like it," then, well, you have nothing.

Here are two examples:
In one book I was reviewing, I mentioned that it felt like there were two stories going on that didn't fit together well. One of the main characters had absolutely nothing to do in the entire book except that, at one point, he shows up some place and does one thing that has significance to the story. And it's completely accidental on his part as he doesn't go there purposefully to do that thing, he just appears there and his appearance causes the thing to happen. I mentioned that, if that was his only role in the whole book, then, maybe, those two stories should be separate.

The author let me know that originally, it had been two different stories but someone else told him he should combine them, and he'd listened. He'd listened because he had not been satisfied with either story, felt they were both missing something. So, instead of working to make them both into stories that he liked, he started taking suggestions on how to make them better. He wasn't satisfied with the end product, either, but, once he'd put it out there that way, he felt he had to defend it even though he acknowledged the issues, issues he himself had with the novel but couldn't reveal in public. So he had meltdown online over my review and proceeded to call me all sorts of names and, well, it was messy.

But it was because he didn't have a story he actually liked.

For myself, one of the things people mention about The House on the Corner is that it starts slow. I spend too much time on character development. But, as I was just talking about in my review of Doc, it's the character development that's important to me. The action of the story is only there to reveal the characters to us, so I want to know the characters. So, when someone tells me I "take too long" to get to the story, that I don't start with a lot of action, well, I'm okay with  that, because my story is doing what I want it to do. [I want it to be clear that the choices of Tom and Sam and Ruth happen because of whom they are as characters and not because of the arbitrary whims of meeting the needs of the plot.] I'm in a place of confidence, because I like my story. The negative criticism doesn't matter so much.

All of this brings me back to a point that I've made frequently over the course of my blog: as a writer, write the story you like. Don't worry about anything else. If you like it, there's very little chance that there won't be other people out there that like it, too. If, however, you try to write the story that other people like, you won't be able to do it. You'll write a story that some people like, maybe, but will have to deal with the other people that don't like it and, probably, won't like it yourself. And you may end up with something that no one likes. If you write the story that you like, well, at least, you like it. And that's what let's you look at a 1-star review and say, "You know what, that's okay, because I'm happy with what I've written." And, in the end, that's all that's really important.

This post has been brought to you by Indie Life.

Sunday, July 7, 2013

The Ocean at The End of the Lane (and The Light of Knowledge)

There are things when you are a kid that you cannot understand. Things beyond your control. Things you are powerless to prevent or to change. Sometimes these are singular, sudden things, and sometimes they are... life. The ongoing patterns of how things are. The problem is that growing up and coming to understand those things doesn't change the experience of  them. It doesn't change what you felt, then, when you were a child and small and powerless.


The Ocean at The End of the Lane is a different kind of book from Neil Gaiman. He has called it his most personal work ever, and I think that shows in that it's written in first person, the first of his novels to be written that way. There are probably some of his short stories written in first person (the one about the cat in Smoke and Mirrors is poking at the back of my mind), but it's been long enough since I've read any of those to actually remember. It gives the story a very personal feel in a way that most first person projects do not. Also, and this could be because I have listened to him reading (I especially like February's) more than a few of his stories, I could just hear it in his actual voice in my head.

There are many things about the way he presents the story that I really like. There are few descriptions. The things that are are just the things that are. The sister is just the sister. We know that she's younger. The mom and dad are the mom and the dad. His father's face gets red when he's angry. It's the kind of thing a child would notice while the other things, the rest of everything, just is. There is no teenage girl staring into a mirror admiring her hair and thinking about her chocolate-brown eyes, and, for that, I was especially thankful. The things that are described are the kinds of things a child would notice, that would stick in his head. The car stuck in the mud. The face of  the opal miner. His bent comic book. It really allows the reader to just travel along with the boy, experiencing as he experiences. Feeling the events that happen much more than seeing them.

The novel centers around one of these events. A moment when a child finds out that he is, indeed, a small thing and powerless to withstand the force of an adult. This event is not the inciting incident nor is it the climax; it lies somewhere in-between, but it is the event upon which the story revolves. The thing that changed the life and perspective of the child. A moment where, after it has happened, you just want to go back to before it happened. But you can't go back.

It's also about the negligence of adults. How they can dismiss as unimportant something that is the world for a child. Or how they can think things are replaceable when they're not. A cat is not just a cat, not any cat, and a dog is not just a dog. No more than a child is just a child. Or, even, a toy--or a washbasin, just his size--is just a toy. Things can't always be solved with, "I'll buy you a new one" or "I'll get you something better."

And, then, there's the whole question of memory and what's real. Something we, I suppose, can never be quite sure of.
"Is it true?"
"What you remembered? Probably. More or less."

This is a pretty great book. I didn't enjoy it quite as much as I did The Graveyard Book or Neverwhere, but I think this one is going to linger much longer. Ask more questions. Give fewer answers. But that's okay. I like books that hang around in my head and make me think about them.

In other news:

Today is the FREE! release of Part Twenty-five: The Light of Knowledge in the ongoing Shadow Spinner serialization. Remember, if you want the whole story RIGHT NOW!, you can get it at that link I just left.
Also, be on the lookout for very special Shadow Spinner news coming up next week (I think). Here is the list of today's FREE! offerings (and, no, I have not managed to get the first few chapters collected, yet, so, hopefully, that will be next time):
"Part Twenty-five: The Light of Knowledge" (also available for FREE! tomorrow, Tuesday, July 9)
"Part Twenty-four: The Serpent"
"Part Twenty-three: The Harlot"
"Part Twenty-two: The Undying"
"Part Eighteen: The Angel"
"Part Seventeen: The Tree of Light"
"Part Sixteen: The Dark Tree"
"Part Fifteen: Food of the Garden"
"Part Fourteen: Anger and Laughter"
"Part Twelve: The Gash in the Floor"
"Part Eleven: The Kiss"
"Part Ten: The Broken Window"
"Part Nine: The Shadow of the Tree"
"Part Eight: The Cold and The Dark"
"Part Six: The Man with No Eyes"
"Part Five: The Police Car"
"Part Four: The Cop"
"Part Three: The Bedroom"
"Part Two: The Kitchen Table"
So... there you go. 19 of the 25 chapters. I should point out that "Part One: The Tunnel" is not free this week and won't be offered as a free promo ever again. In fact, it won't be available in this current format for much longer.

Thursday, July 4, 2013

The Religion of Writing: Part Two -- The Hierarchy

Disclaimer: The following example is a paraphrase of the events, so to speak. It's just a general idea of how things happened and how they work and not meant to be exact fact.

Way back in the way back, God had relationships with men on an individual basis. There was God and Adam, God and Methuselah, God and Noah. Then there was God and Abraham, and God and Jacob, and God and Moses. By the time we get to God and Moses, the Hebrews were getting a bit tired of the whole "indie God" scene and wanted a more traditional pub...um, I mean, god, so, to deal with the issue, God gave them some basic guidelines to live by. There weren't too many, because God didn't want to bog everyone down with a bunch of rules, and, really, those rules boiled down to two things: 1. Love God and 2. Be excellent to each other.

But you know people, and they couldn't deal with things being so straightforward, so the agents, I mean priests, got together and made lots of rules. Lots and lots of rules. LOTS and LOTS of rules. So many rules, we've lost track of them all. And you couldn't just join the "Hebrew club" anymore, either. There were lots and lots of rules and tests and all sorts of things you had to do to get on the inside with God. According to the Pharisees, at any rate.

After a while, God got tired of all of that, so He sent his Son down to deal with the people. His son, Jesus, said, "Dudes, no more rules. Just love God and be excellent to each other." Of course, we all know how that turned out. But the apostles understood the message and started spreading the love. Except, almost right away, people started making new rules or re-imposing the old ones and, eventually, along came the Romans and made it all Catholic and stuff, and, pretty soon, there were even more rules than before and, again, no one could just decide to follow God; they all had to jump through special hoops and get rid of all their adverbs and stuff before they were let into the "Catholic club."

After another while, this other dude, Martin Luther, came along and said, "Dudes! Jesus came to get rid of all of these rules. And, oh yeah, the agents, too. We don't need those guys!" Things didn't go well for Martin, either, but a bunch of new small publishers sprang up that, initially, did away with agents (I mean priests), but it wasn't long before they put new agents in place and made all sorts of new rules (like you can't go to Heaven unless you speak in tongues, and dancing will send you straight to Hell).

I'm sure you get the idea.

So let's look at something else.

Way back in the not quite as way back there was a dude that wrote a book. He paid to have some copies printed, then he tried to sell them. Other guys did the same thing. That worked out for some of those guys and not for some of the others. Some guys had more money than others, so they could print more books, and things tended to work out better for them than for the guys that couldn't afford to print very many. There was no such thing as "best seller" back in those days, but some of those books are still around.

Eventually, some poor author (because almost all of them were poor (are poor)) had the bright idea to hire a printer to be his publisher. Since he couldn't pay the guy that owned the printing press in advance, he offered to pay the printer, now his publisher, from the profits from the book. The printer saw the opportunity to make more money than if the writer just paid for the number of copies he could afford and, thus, was born the modern traditional publishing model.

However, I want to point out that when all of this started, the author was in charge. The author communicated directly with his readers, often selling his books to them by hand or taking them to small stores to sell (because there were not, yet, bookstores). The printer/publisher worked for the author, not the other way around. As the idea of being paid from the book profits took hold, the whole process became an invest for the printer/publishers, but, at first, the author was still in control. But the balance of power shifted to the money guys as more and more authors sought out the same publishers. And then came rules. And agents. And more rules. Until the author was at the bottom. No longer communicating directly with... anyone. Except the agentpriest.

And all the people began to worship the traditional publishing house and abide by its rules and jump through its hoops to get inside. Agents really are the priests of the traditional publishers, testing people to see if they're worthy, but, just like it was with the Pharisees (charging for sacrifices and requiring that people only use special "temple money") and the Catholics (selling Indulgences to have your sins forgiven) and the televangelists, it's all about the money.

And, now, we have self-publishing, which is kind of like the Protestant Reformation. And, just like the Catholic church condemned Luther, we have the big traditional publishing houses condemning Amazon and other self publishing outlets and calling people that do self-publish all kinds of bad things.

And we have people clinging to the old model. To the church of Traditional Publishing.

And I have to wonder about what sorts of rules we're going to develop for self-publishing and what kinds of hoops we'll eventually have to jump through for that. Because, well, we humans seem to love our rules and our hierarchies. I guess, that way, we know who's "winning." Charlie Sheen, right? Or is he still winning? I don't know.

I'm not much of one for outdated traditions. Or any traditions that aren't relevant. All of this post has been to say that we ought to really look at what the people "in charge" are telling us and figure what part of it is useful. Because, as far as I can tell, unless you are just in desperate need for the validation that comes from being traditionally published, those guys aren't doing anyone any good. Not anymore. And, hey, really, if you are looking for that pat on the back, I'm sure there are better places to get it.

Tuesday, July 2, 2013

The Importance of Liking Your Own Work -- Part One (an IWSG post)

Back when I first moved out to California, I worked at Toys R Us. At the time, TRU was one of the worst possible places to work at. They had incredible turnover amongst their employees, and, the funny thing is, they couldn't figure out why. After all, they paid minimum wage, right? Anyone should be happy with that. A job where they hire no full-time employees so that they don't have to provide benefits. A job with no employee discounts. A job with absolutely no flexibility to your schedule and, even worse, no routine to it. Really, they did their best to own you by making you be available to them whenever they wanted you to be.

But you should be thankful for the job.

I've heard that it's better there, now. Well, at least, now, they have an employee discount program. I'm not sure about the rest.

And, yes, I'm sure I just described quite a bit of corporate minimum wage retail jobs, but I only have experience with the one. [And when I say that it was one of the worst places to work, I'm not saying that from my experience. During the time I worked there, it was ranked in the top 10 worst retail places to work and, I'm pretty sure, had the highest turnover rate of any retail chain store.]

But all of that is beside the point. Background, if you will. I suppose it's important to note that no one worked there because s/he wanted to work there. No one aspired to working at the local Toys R Us. [On the other hand, I did actually know people when I was growing up (and, remember, this was the South) who did aspire to work at Wal-Mart. Their goal was to one day get to be a manager!]
[I'm totally serious about that.]
[Completely, totally serious.]

To cut through what could be a long story, it wasn't long before I was put in charge of other people. Actually, for someone that started at the complete bottom of the TRU food chain (maintenance (a fancy word for janitor)), it was incredibly quick (as quick as they could make it without violating any of their weird policies). It was unhappy-making for some people that had been working there for years, but, see, I was self-motivated (meaning I didn't wait to be told what to do (because most people, upon finishing a task, would just float around the store until someone found them and gave them a new task (which meant a lot of people spent a lot of time just avoiding being found))), decisive, and more than competent (meaning I didn't need to be told more than once how to do any particular thing).

Which brings us to the interesting part of all of this: I was put in charge of other people because of those traits. I was good at figuring out what needed to be done and making sure it got accomplished. [Actually, my biggest issue was with delegating, because I feel much more comfortable just doing tasks myself rather than depending upon someone else to do them.] These were things the managers liked seeing in their employees. They were not traits, however, that the other employees liked so much. Specifically, they were not traits that employees working under me particularly liked.

Every morning, all of the department heads had meetings with the people that worked under them to hand out tasks. Mostly, this was a pretty uncomplicated interaction that went kind of like this:
"Okay, Employee 1, you need to do Task A, today. It's not a rush job; you just need to be finished with it before you leave for the day." [That's eight hours to do a job that shouldn't take more than two or so to do, but you had to leave in time to help customers. Still, those kinds of tasks shouldn't have taken all day, although they usually did.]
"Employee 2, you need to do Task B. This is a rush job, and you need to focus on getting it finished as quickly as possible. If a customer has a question that you can't answer on the spot, call someone else to help her."
"Employee 3..." [I'm sure you get the idea.]
Seems straightforward, right? Except this one morning, a young lady interrupted me by saying, "Why do you always act like you know everything?"

I think I stared at her for a moment, because, really, I had no idea what she was talking about, then said, "Excuse me?"

"Why do you always act like you know everything?"

"I don't know what you're talking about."

"You never say 'I think' or 'I believe,' you just tell us what to do like you know everything."

Point #1: If you think something or believe something, it's redundant to say "I think" or "I believe," because, obviously, if you're saying it, you must think or believe it.

But that's not what we've been taught in our current society. In a world where everything is subjective, we're supposed to always preface anything we say with a phrase that casts doubt upon what we're saying. Personally, I think that's bullshit. [Yes, I prefaced that with "I think" on purpose.] I don't go around saying "I think 2+2=4." Why? Because I know 2+2=4. Sure, I could be wrong (I'm not), but I believe that I'm correct, so I just say it: "2+2=4." People, though, get all bent out of shape with when you act confident about anything more complicated than that, because, you know, we're all entitled to our own beliefs.

And, see, I believe that. We are all entitled to our own beliefs. But that doesn't mean I have to be wishy-washy about what I believe. And you shouldn't either. If you believe it, if it's really what you think, drop the preface. Just own it and say it. Don't make it sound like you don't know, yourself, if you're sure about what you say you believe.

My response was something along those lines, "If I'm saying it, I must think it, so why should I bother to tell you that's what I think."

"Well, other people say it that way. They tell us what they think we should do. They also ask us if that's what we want to do. Why don't you ask us?"

"Do you mean I should say, 'Hey, would you like to re-do the endcap on aisle 7, today?'"

"Yeah, why don't you ask?"

"Because it's not an option. If I'm giving you the endcap to do, you don't have the option of saying 'no,' so why should I ask you if you want to do it? That would be misleading."

By this point, the other 5 or 6 people under my charge were all staring open-mouthed at us.

"Well, why don't you see which things we want to do and let us pick or something? I don't want to do [the task I was giving her for the day]."

"That's why I didn't ask. It's my job to assign the tasks to the people I feel best equipped to handle them, and you get to do [whatever the task was she didn't want to do]."

Point #2: If you're in charge of something, if it's your thing, it doesn't matter what other people think or feel about it. You have to make the decisions. Trying to figure out how everyone else feels about a particular thing and making it work for everyone will result in some things never happening. Like, you know, when someone smeared poop on the bathroom walls (and, yes, that would happen in the boys' restroom every couple of months), someone had to go clean that up. It wasn't something that was really up for debate, because that's one of those things that no one ever wanted to do, so saying, "Hey, who wants to go clean the bathroom?" wasn't going to get you any responses. You had to pick someone and tell them to do it and ignore any "Why do I have to do that?" and "I don't want to"s.

You may be wondering, at this point, what any of this has to do with, as a writer, liking your own work, but both points are very relevant. And I'm not saying that feedback can't be useful, but too much feedback, or trying to accommodate too much feedback, is debilitating. It's yours, your work. Believe in it. And I'll talk more about all of this in part 2.

Just to wrap up the story, as it turned out, that particular employee had been passed to me through about three other people who couldn't get her to do her assigned tasks. They had not been firm enough and had given assignments out as if they were options: "How would you like to do..." or "Why don't you take..." or "It would be great if..." She had taken all of those assignments as if they were optional and opted out of doing them. So they gave her to me, and she did what I assigned her even though she didn't like it.

However, about two weeks later, on a day when I was not at work, she had tried on a manager what she had tried on me, and she was fired on the spot. Actually, she was told she could "go home for the day," because they (TRU) never actually used the term "fired" (except that one time the one guy was caught stealing a buttload of video games, but that's another story). Then, she was never re-scheduled and when she came in for her paycheck, she was told "things aren't working out" and let go. Don't you just love all the euphemisms? I think they're great.

This post has been brought to you by Alex Cavanaugh and the IWSG.