Friday, June 13, 2014

Supporting We Need Diverse Books

A campaign called We Need Diverse Books began not long ago. As bloggers, authors, and readers started to notice the lack of diverse characters in novels, specifically in the YA genre. Certainly, the lack of diversity in YA novels is astounding. Even when characters are stated to be characters of color or the color of their skin is left ambiguous, fans and media representations of the characters are often whitewashed. Take, for example, Harry Potter's titular character. Harry Potter himself is never described as white. Readers know he has green eyes and black hair, but Rowling refrains from outright saying Harry is white. And why should she? In my experience, if a character's skin color is left to the reader's imagination, he or she is automatically imagined as white.

Of course, I'm speaking as a white individual. While I can certainly promote and support We Need Diverse Books as an ally, I can never truly understand the issue from a person of color's perspective. I think this is totally valid -- naturally I don't have a right to insert myself into such a conversation: I have nothing valuable to add. But that is my issue here.

With a call for more diverse books in the libraries and in the book stores, I feel, as a writer, responsible. I want to help the best way I know how: writing. But I can't do that effectively because, as a white person, I do not have the same experience with prejudice and oppression as POC. Sure, I have experienced sexism as a woman. But I can't say that I have ever been followed around a store because of the color of my skin, nor have I ever been called a racial slur. So is it right for me to try and represent a group of people (although I recognize that no one story is representative of a whole group) I have no experience as?

I don't think so.

Men, certainly, have written books from the perspective of women. Women have done the same for men. And, certainly, I could interview POC in an attempt to make a novel as faithful to the POC experience as possible, but if I am to show true respect to my readers and my characters, it's a disservice to them to write characters who aren't white.

From We Need Diverse Books

So what do I do? I can buy books with diverse casts. I can protest whitewashing in film adaptations. I can write about other aspects of diversity with which I am familiar -- anxiety and depression being two. When I'm a librarian, I can create book displays centering on diversity and plan programs to support diversity. And I can happily take suggestions and criticism from POC and others regarding any offensive thing I may unintentionally write.

But I cannot pretend that the best way for me to support this movement, for once, is to write diversely. As much as I'd like to, it just doesn't seem fair. As always, if anyone has any comments or suggestions, I'm happy to take them below!

Tuesday, June 10, 2014

13 Books That Changed My Life

I've read a lot of books. Most of you are probably un-surprised to hear this, but there it is. I've read so many books that I don't remember most of them. There are some, however, that stick out in my mind. Either they had a profound impact on the way I thought at the time or there was an element within them with which I strongly identified. Here's my list of life-changing reads. What are some of yours?

1. War for the Oaks by Emma Bull
While it was Tithe by Holly Black that first introduced me to the world of faerie and urban fantasy, it was War for the Oaks that got me hooked. There was something about the sophisticated, yet playful prose that struck me while I read. Admittedly, this is my favorite novel. I loved the lyrics woven into each chapter and the kick-ass heroine, Eddi. Bull took on the huge task of incorporating faerie into 1980s Minneapolis. And she did so seamlessly. This book opened a whole genre for me and totally changed my perspective on what "fantasy" meant.

2. Simon Says by Elaine Marie Alphin
Simon Says gave me my first dose of major character death. For days after reading this YA novel about mental illness, I was devastated. I had gotten caught up in the subtleties of Alphin's storytelling and Charles' struggles as an artistic prodigy. Being an angsty teenager with what I felt was a creative streak myself, I connected with Charles. Alphin amazed me. The first time I read it, I was impressed by how adult and non-trivial everything seemed in the book. It felt so unusual to have an adult writer write teenagers as teenagers really are, rather than dumbed-down and caricatured versions of young adults. The book made me feel validated, in many ways, and continues to push at me years after reading it.
From Goodreads

3. The Dust of 100 Dogs by A.S. King
A.S. King took me into a genre of fantasy into which I had not previously ventured. Featuring Emer, the novel details the existence of a girl cursed to live one hundred lives as a dog before returning to her human form. Like the Simon Says, The Dust of 100 Dogs made me feel as if King was telling me a story, rather than trying to talk down to me, as many YA novels do. The genre has been shifting lately, but in the past, respect for YA readers has been difficult to find. I loved the mature style of the book and King showed me it was okay to read YA (and even fantasy YA) without the fear of being somehow mocked.

4. The Catcher in the Rye by J.D. Salinger
While we're on the topics of initialed-authors, I can't very well make a list like this without mentioning Salinger. I read The Catcher in the Rye in middle school and again in high school, both times for my own enjoyment. It may be an obvious choice, but Salinger captured the bitterness of Holden Caulfield in a way that makes the character easy for both teens and adults to latch on to while still maintaining the qualities of "important literature." The symbolism in the novel can be explored over and over again and, while Salinger wrote little more ("A Perfect Day for Bananafish" being his other big hit, among less-popular works focusing on the fictional Glass family), Catcher is a work which is frequently listed as an inspiration and a classic. It certainly holds a place in both of these categories for me.

5. Boy Proof by Cecil Castellucci
When I first started Boy Proof, I anticipated a brain-candy read: nothing too philosophical, or even well-written. Just some trash to keep my eyes and my mind occupied. I ended up being totally wrong. Although brief, Boy Proof made me ask myself some really important questions about identity and popularity. Like Egg, Castellucci's main character, I felt relatively isolated compared to my peers in high school. I was a "nerd" and a "geek" who actually enjoyed homework, enjoyed fangirling over various books, television shows, and movies, and didn't have a whole lot of opposite-sex interaction (and that which I did was strictly platonic). I felt pathetic. But Castellucci's novel made me feel differently. I became proud of my passions and interests, even if the people around me were repulsed by them. Of course, it takes more than one book to change something so drastically, but this was the beginning for me.

6. Falling Up by Shel Silverstein
Like many others, I grew up with the poetry of Shel Silverstein. I read and reread his poems, even taking on the responsibility of memorizing "Snowball," a personal favorite. It was Falling Up (and his other collections) that made me realize poetry didn't have to be sterile and distant and, well, difficult. Poetry could be fun. You could use wordplay and jokes. And that's what Silverstein did. He totally changed my perspective on lines and verse, leading me to later appreciate more challenging works such as my next choice.

7. Macbeth by William Shakespeare
From motherfuckingshakespeare's Tumblr
I admit, Macbeth is not my favorite Shakespeare play. (That title goes to Hamlet.) However, it was in a senior English class in which I read Macbeth (and later Hamlet) that I learned how absolutely ridiculous Shakespeare was. If you don't already know this, let me be the first to tell you: Shakespeare was pretty crude and hilariously so. Just scroll through the Shakespeare tag on Tumblr, and you'll get a good idea how so. If you open to a random page of a complete works of Shakespeare, chances are you'll be able to locate a penis joke. Of course, there are many more wonders to Shakespeare than just phallic humor. But when my teacher introduced the class to the hilarity of Shakespeare through some passages in Macbeth, Shakespeare suddenly became infinitely more accessible. (Also, while I haven't had a chance to read this one, it looks like a good way to spend some time: Filthy Shakespeare.)

8. Every Time a Rainbow Dies by Rita Williams-Garcia
To be honest, I'm not sure what it is that has made this novel stick with me. I read it once years ago, and haven't even perused it since. Perhaps it's the harsh reality of the world projected into the book that caught me. The novel deals with rape and death but is hopeful. I think of it often, especially as case after case of rape (or murder in the face of refusal as in the recent stabbings and shootings by rejected boys) pops up in the news. Its relevance is, unfortunately, real. Still, the strength it offers remains with me even years later.

9. Eight Seconds by Jean Ferris
Eight Seconds is the first novel I remember reading featuring gay characters. I read it at a relatively young age, at which point I don't recall discussing sexuality or sexual orientation with anyone to any great degree. It intrigued me, as a young, straight, girl. While it may not have been representative, it was an introduction to a community with which I was unfamiliar (at least, in a conscious sense).

10. Fat Kid Rules the World by K.L. Going
Around the time I was really into music, I stumbled upon Fat Kid Rules the World, a novel about a depressed, overweight kid who falls in with a scrawny, troubled kid and finds his passion in drumming. Like almost all the other books on this list, I fell into seeing myself in Troy. I, too, was depressed. I, too, felt music rescued a little piece of me when I felt there was nothing left to rescue. Apparently, the novel was made into a movie in 2012. The book dealt with some heavy things, but that's what good YA novels do -- they attack the tough stuff that adults seem to think teens can't handle. Often, it's these very things teens are going through on a regular basis.

11. It's Kind of a Funny Story by Ned Vizzini
Like Fat Kid Rules the World, It's Kind of a Funny Story took on suicide and mental illness. Drawing from personal experience, Ned Vizzini details life in a mental hospital. This book helped me through one of the most difficult times in my life, shortly after I was diagnosed with depression and a general anxiety disorder. The novel helped me be okay with taking prescriptions and generally accepting help to deal with my issues. Vizzini, unfortunately, took his own life in December 2013 at age thirty-two. A film version of It's Kind of a Funny Story debuted in 2010.

12. Lolita by Vladimir Nabokov
From Flavorwire, Jeremy Irons as Humbert Humbert and Dominique Swain
as Lolita in Lolita (1997).
I read Lolita in May 2012 while I waited to close the dorm rooms as a resident assistant. The prose was rich and took some getting used to. But page by page, I found myself sympathizing with Humbert Humbert. I was disgusted with myself. When I looked into it, I found others had a similar experience. Nabokov's masterful prose didn't encourage sympathy for the titular character, but for the pedophilic narrator. I was amazed at how Nabokov had manipulated me, even with my guard up. Even as an English major, already disillusioned by literature and believing there was nothing left to surprise me, I was astounded by the power of literature with Lolita as the example.

13. Thieves Like Us by Stephen Cole
It never occurred to me that books could be action/adventure, but Thieves Like Us adamantly corrected that notion. Whenever I hear of a kid who "doesn't like to read," I insist he or she just hasn't found the right book. More often than not, I hear this about boys who are active and like exciting action films. When this is the case, I think of Thieves Like Us. Most of the time, this suggestion goes ignored because the kid is so convinced he dislikes reading that he won't give it a chance. But I'm even more convinced that this book will change their mind because it is that cool.


Monday, June 2, 2014

Life Update

Hey all.

With graduation a week and a day behind me, life's started to slow down a bit for the moment. I've been back in New Hampshire for almost a week now, and it's been pretty nice. Mostly, I apply for jobs, read, and watch Supernatural. I've been trying to learn how to cook, too. Last Wednesday was fish, Thursday was gourmet grilled cheese (Swiss cheese, tomatoes, spinach, and avocado), Friday was chicken cordon bleu, and then Dad took over for Saturday when some extended family came over.

I've also been casually thinking about a website design. I sketched one out while I was in Roanoke and I'm refreshing my HTML and CSS skills with CodeAcademy. I rarely have occasion to use either language, so the refresher is necessary. I could design all the sites I want, but they'll never be used (in most likelihood) so it's hard to motivate myself to do it.

I haven't been as avid a reader as I have been in the past. Searching for jobs is a full-time job (and a poorly-paid one, at that...it's like indentured servitude to yourself). Anyway, I finally finished Orange Is the New Black by Piper Kerman and I'm working on Don't Look Behind You by Lois Duncan. Don't Look Behind You is definitely something of an artifact. It was written in 1989 and it shows. Not only are there none of the technologies we enjoy today, but there's something very 1980s about the main character, April. Maybe it's just Duncan's writing, but April comes across as a clichéd 1980s-cheerleader type. It's like watching a twisted episode of Full House.

I'm doing my best to read through what's in my closet library. (And by "closet library," I mean my closet which I use mainly to store books.) It's difficult because a lot of the books I've purchased, I've since lost interest in. Still, I feel obligated to read them because, well, I did buy them and as a bibliophile, it just seems plain wrong not to give them each a good chance. After all, this is America: books are good until proven bad. Right?

But I need to get through as many as possible before I leave so I can clear up some space. I already have so much stuff to sort through and either pack up or get rid of so my parents can use my room as they please when I leave in mid-July. I'll be back, of course, for Christmas and the like. My bed will remain. My undersized dresser will probably stay, too. And it looks like Mom will want to use my sewing desk and maybe my desk-desk, so those will stay too. As for everything else? I don't know. I have so many crafting things and art supplies that I can't possibly justify bringing to DC. Not only will I be unlikely to have the time to use any of them, but there simply isn't enough space. Luckily, I don't think my parents will mind me using home as storage until I'm in a condition to take the things out.

I'd like to blog more regularly again, but of course, I'm struggling with topics as usual. My days here are pretty standard. I wake up in the late morning, I go for a walk, I have breakfast, I scroll through Tumblr, I apply for jobs, I scroll through Tumblr some more, I watch a couple episodes of Supernatural, maybe I reward my job-searching efforts with an iced coffee from Dunkins, and then I wait until Dad gets home and have dinner ready. We watch TV in the evenings and then we drift off to our own rooms to sleep. Sometimes my brother comes home, sometimes he doesn't. I don't hold my breath waiting. But who knows what will happen. Maybe you'll hear from me more often. Maybe I'll get struck with some profound thought to share.

Until then.

A

Thursday, December 5, 2013

Now Back to Your Regularly Scheduled Blog -- Maybe

Okay, so let's get into something with a little more substance this go-around.

I had my final interview with Teach for America today at Virginia Tech. I can't talk about it because there are rules about those kinds of things (what is this, Fight Club?) but what I can tell you I will.

I went to bed at 7:30 last night because I knew that if I didn't get enough sleep I would be a wreck and I had to get up at 7:00 today to ensure that I left on time. So, I went to bed at 7:30 and around 4:30 in the morning, the poster next to my bed fell on my face and I was not pleased with this. However, there wasn't much I could do about it, being half-asleep and all, so I went back to sleep until I woke up again naturally around 5:30. At this point, my body was just done with sleeping because, well, it had been almost eleven hours and that's a pretty decent sleeping marathon (though I've done better). Still, I had time left to sleep and, really, what else was I going to do by psych myself out? So I returned to dream-land once again. This The Sound of Music with my Dad. This production was not staged, as I had originally thought, but projected onto a screen in this weird concrete-like building thing. I don't even know. It was weird.
God, I look so short. Also, psycho look on
my face. I hope I wasn't wearing that
during the interview...
time, I had a dream that I went to see a production of

So I eventually actually woke up when my alarm went off and, since I built some time in for the snooze button, I enjoyed using that a couple of times. I got out of bed at 7:15, got dressed, took out my eyebrow piercing, brushed my hair, put on my shoes, checked my bag one more time and was out the door.

Before I got on the highway I picked up some McDonald's for breakfast because, why not, and then was on my way. Getting to Tech was easier than I expected and navigating the campus itself wasn't a total disaster, so that was nice. I got to the building I was supposed to go to on time and was not the last person to show up -- A+ for Abby. The two people in the room introduced themselves and then we got on with things. I wish I could tell you more but sadly I cannot.

After the day was finished, I got back on the road (this was around 2:00). When I got off the highway, I went back to the McDonald's I started at in the morning because I knew the dining hall at school was closed and I was hungry. Sue me.

I've had a lot of people ask how the interview went and, to be honest, I don't know. I'm not the greatest at reading people and there were additional circumstances (gah, the secrets) lead me to believe it would have been even harder to read this particular interviewer. That said, I'll just have to wait and see what happens.  In the meantime, I'll remain on the lookout for additional opportunities. It's tough because for the field I'm interested in going into while I earn residency in Maryland, most of the organizations/businesses aren't hiring now or recruiting spring 2014 grads. (If you know of anyone that is, though...you know where to find me!)

As far as my writing goes, it's going. I'm not really writing anything but my thesis at the moment. Sometimes I wish I could write something else but then I'll feel guilty for wasting my creative energy on something that isn't my thesis, especially when I really needed to "get my rear in gear" if I'm going to have a completed and revised draft by the time I rocket out of here.

I know, my life is so exciting. Aren't you jealous?

Sunday, December 1, 2013

Humdrum

It's been a long time since I've posted on here. I've been busy, of course, with other things. Most of the time, I am working (as in, Housing & Residence Life tasks), doing homework, attending class, or maintaining my Tumblr, which is a far more personal blog than this. Sometimes I get a day or a night to do my own thing -- catch up on the many television shows I watch or work on the job hunt, which is just as stressful and tiresome as I remember it being. During meals, I typically eat with friends, though when I don't, you can find me thumbing through my cell phone to pass the time between bites.

I also spend a lot of time working on my novel. I won't say much about it here, but if you see me in person, I'm happy to tell you about it individually. This has been the first book/longer written piece I've done that I haven't gotten bored of by twenty pages in or so. I'm optimistic about it and hope to start sending it out to publishers by the end of next summer. Maybe sooner.

This post probably isn't very coherent. I drove five hours from DC today to get back to school. The drive usually takes about three-and-a-half hours, but with the Thanksgiving traffic and a rather unforgiving sun today, it was atrocious. I'm trying not to think about it and put it behind me.

Other things going on. I'm an aunt now. That's new. That happened on October 10. His name is Aaron. I haven't met him yet, but I expect I will when I go home for Christmas break.

I'll be twenty-two in two weeks. I don't know if I'm doing anything for my birthday. In fact, all I think I really want is a good sleep. I think I sound old.

Ring Night is over. It was so much fun and I'm sad it didn't last longer.

My life has been pretty standard lately, so I don't have much to talk about. Perhaps sometime in the near future you'll hear from me again.

Friday, August 9, 2013

CodeAcademy Cutie

I first learned  HTML (hypertext mark-up language, for those of you who have always wondered) in high school in a computer class. It was easy enough and we used a program called Dreamweaver to make it even easier. Previously I had messed around with HTML on my MySpace page, mostly copying and pasting code from other templates. I had done a little bit of linking and formatting on LiveJournal. But I never coded consistently over long periods of time. Whenever I did pick it back up, it wasn't too hard to re-learn, though I wouldn't say it was like riding a bike.

This year I decided to try again and try harder. I started using a website called CodeAcademy to refresh on HTML and learn the new formatting for HTML5. For several weeks, I hesitated to start learning CSS. I had seen CSS coding in the past and my boyfriend insisted it was really easy, but the number of brackets and semi-colons scared me a bit.

In my sophomore year of college, I took a Java programming class to fulfill my math credit. I did well enough but it was one of the hardest things I've ever done. Maybe this is because I think more abstractly than concretely. It took a lot of effort to do well, which is not something I'm used to.

Somehow, I managed to get through it. But when I saw CSS and saw how similar, on the surface, it looked to Java. So I waited and waited and waited.

Two weeks ago, I was tasked with designing (just on PowerPoint -- so, just design, not program) a website for my internship. Although the programming was being contracted out, I decided to mess around with the HTML the site would theoretically use once I'd designed it in my free time. I realized before starting to mess around with the coding, however, that I would need to learn CSS.

So I trudged back to CodeAcademy, feeling less than confident, and began the lessons.

I don't know what it is about CodeAcademy that works so well for me (maybe the repetition?) but it worked. I now feel very confident with my HTML and CSS coding skills and know where to find help/resources if I need it. I can create some really cool stuff and it only took me about a week to get to the level of skill I currently am. I think that's pretty cool.

I was able to code the homepage of the website I designed. Also very cool.

I recognize that this is a valuable skill. While I can't (yet) program a library catalog or anything, I could certainly design and program an About Us or Events or Resources page.
 
I found the CSS and HTML programming to be relatively simple. CodeAcademy explained it in a way that I understood and the exercises were relevant and well-written.
 
Meanwhile, when I started up JavaScript again (nudged into it by my boyfriend who insisted it wasn't so bad), I struggled. I'm still in the JavaScript lessons and, because there are so many more little details to be aware of in JavaScript than there are in HTML or CSS, I get lost. Frequently, I just type what they tell me to and go on without truly understanding what it is I just did. While this happened sometimes with HTML and CSS, I managed to play around with it until I really understood what it is I had accomplished. This isn't the case with JavaScript. This may be my own failing, or it could be a shortcoming of this particular section on CodeAcademy. I'll leave that up to others who haven't learned JavaScript before. I sometimes wonder if it's that I've already learned JavaScript in a different order than its being taught to me now. If one of you try it out, I'd love to hear your take on it and what section you prefer.
"I can code like a boss."
"You're hired." 
 
Still, I'll keep at it because it's valuable and important and, honestly, I imagine it will help me write the novel I'm currently working on for my senior honors thesis.
 
Even if you're not interested in coding or afraid of it, try CodeAcademy out. Start with HTML. It becomes addictive, once you start building things out of nothing. Once you see that you could recreate your favorite website (though maybe not so much in functional terms, because that would include more advanced code, but in its visual aspect). If nothing else, it's great for professional development. If you want to be hirable or even more mobile in your current position (assuming you work in an office of some sort), take up coding. You'll instantly become more valuable.
 
Codeacademy image courtesy of uwbnext.
Interview image courtesy of GlassDoor.

Friday, August 2, 2013

Faster than a Speeding Bullet or, #ProductivityProbz

At my internship this summer, one of the biggest "complaints" I've received regarding my work from my supervisors is that I work too quickly. This is a problem for them because they can't always come up with stuff for me to do (that isn't just busy work or has no actual meaning) quickly enough. To be fair, I'm working for a government agency and we all know the government is notorious for their sluggish pace.
I accomplish more in an hour than Congress accomplishes
in a whole year.

It's funny because, in the dozen or so interviews I've ever been questioned in, I'm frequently asked
how I work under pressure. As someone whose first job was at McDonald's (with a double drive-through which I frequently manned independently, even during rush hours when we'd serve up to a hundred or so cars within an hour), working under pressure is one of my fortes.

Additionally, I've always just been someone who works quickly. I was often the first person in class from elementary school on to finish an assignment. Teachers chided me and reminded me that it wasn't a race. But I wasn't working fast to finish first or even just to "get it over with." I am just naturally a fast worker. I type fast (typically I type around ninety words a minute, but I can do more without much strain or effort), I eat relatively fast (maybe because lunches were twenty-three minutes in high school), I get ready to go out quickly (no, you don't understand -- in high school, I woke up at 6:25 and be outside for the bus by 6:32), and I talk fast (maybe this is a New England thing, because it's certainly not this way in the South).

My current supervisors say to me, "Slow down. It's fine."

But why would I slow down if I can comfortably (perhaps more comfortably than if I slowed down) complete a task that takes someone else an hour in half-an-hour? Productivity, in my mind, is a good thing. And I don't believe my work suffers for my speed. I make just as many (or as few) mistakes as anyone else, sometimes even less. Believe me, if my speed was hurting the quality of my work, I would force myself to slow down. I have a thing for doing the best I can at everything -- it's how I enjoy work; even if I don't enjoy the work itself, I like to do things well. But that's another topic for another day.

So I can slow down by taking five minutes here and there to check Facebook or pick a new Pandora station or take a walk around the office to stretch my legs. And I do, but I still work too quickly. Maybe if I'm accomplishing twice as much work as anyone else is, then I should get paid twice as much. (Hint, hint, future employers -- just kidding, of course. Kind of.)

I spoke with my mother about this and put it this way: I work as quickly as my brain allows me to. But my brain thinks as fast as it thinks -- I can't go all meta on it and make it slow down. If there's a way to do this, then I am not aware of it. I don't think meditation qualifies. In fact, meditation, like defragging a computer, probably frees up those jammed neuron paths to make your thought processes outside of meditation even faster. I'm typically not hopped up on caffeine (although I had more coffee yesterday than I've ever had in one day before -- I was desperate and even put a note up facing out on my cubicle that said I was now accepting coffee donations).

I don't have a solution for this problem with the speed at which I work. I don't know that I want to "fix" it. I'm not sure it's really a problem. It's only a problem for me in that I don't always have something to do because I eat up all of the assignments before anyone can make any more for me. I'm not even entirely sure of the source of my fast-moving work style. Maybe it's my fear of death and mortality. Maybe I want to accomplish as much as I can before I die (which I recognize at a conscious level, but perhaps it effects my working style at a more subconscious level). It's not that I can't concentrate on one thing for extended periods of time. I definitely can, but if I don't have to, why would I?

Even this blog post, now at 760 words according to 750words.com, took me approximately ten minutes to write. I began with no plan except for the general topic of how quickly I work. No outline, no phrases in mind, just a topic. And here it is.

Did the quality suffer for the speed?  You tell me.


Congress image courtesy of thinkprogress.org.
Speedometer image courtesy of wallgc.com