Before the Binge

Disclaimer: 99% of this entry was written before November. Also, it will mostly outline my plan of attack for the event NaNoWriMo. Also, I use the term 'shitty' more than once, but it's been that kind of month.

I was hoping to begin querying my first novel this past month, but alas it was not to be. I was going to use the Writer's Market as a resource and spam every corner of the literary world. Problem is that the Deluxe Edition I ordered was scheduled for October 8th never arrived. The book mostly disappeared or was labeled 'Out of Stock' by every place on the planet that sales books. The whole reason I paid extra for the 'Deluxe Edition' was to start querying right away. I ended up canceling my order and had to put querying on hold until after the first of the year. The standard version is scheduled to come out in early November and, even if that remains to be true, the holidays are a shitty time to query people. Plus, I have a book to write.

That book is currently titled 'Thermal Kings'. There's an eighty percent chance that will change by the time I'm done with it, but it is what it is for now. There are, of course, some days I won't be able to write. To be honest, November is kind of a shitty month to host this event. Thanksgiving being the chief reason among them. With that holiday and other obligations, I currently calculate that I have twenty-six days worth of writing. That means I need to write just under two thousand words a day to reach the fifty thousand word goal. However, I'm setting a daily goal of twenty-five hundred words a day so I can be, at least, mostly done before the week of Thanksgiving. Follow me on Twitter (@LesAbernathy) if you want plenty of word count shitposting.

Since I'm the ML, it's up to me to encourage people to keep writing so they'll forget everything dies and gets forgotten. I scheduled a NaNoWriMo kickoff event for Sunday at a local coffee shop. Because of course I did. I want to meet every Sunday, but let me meet these people and see if I want to keep meeting them. Since the event is in the future, we'll both have to wait to find out how it goes.

Not much else to say. There was some shitty stuff going on at work this month, but I've gotten as much as I can off my plate as I can before the big month. I'm ready, but I don't feel ready. If that makes sense. I hope to get into the flow of things and become unstoppable. Like I usually do. The trick is just to get started in the first place.

Until next time, and at all times, be kind.

P.S. Free Hong Kong.

Be Kind

Warning: Don't read the first two paragraphs. There is no news/information here. It is simply me getting something off my chest.

I was originally going to start this entry off with a rant. Then, as my anger cooled, it turned into more of a well-worded, but hostile, examination. Being more of an observer of humanity than a member, I started to notice something. The thing I was going to rant against has mostly good people involved. Like a charity that spends too much money on donuts. You don't want to call them out for wasting money because you'll look like an ass for criticizing a good charity. Even though that money could be put to better use. Even though I'm right. I saw people defending the good while shooting down any idea of the fact the system is flawed and requires reform. They were being nice. Which led me to something even worse than a rant: A lecture.

I highly value kindness. It's a rare resource or at least rarer than it should be, and it genuinely makes the world a better place. The thing is, I also highly value honesty. And, when you value honesty, you learn the difference between being kind and being nice. Imagine, if you will, that you have a good friend that's currently in a toxic relationship. Being kind is telling your friend to dump that loser. Even though it will hurt. Even though speaking up might jeopardize your friendship. You still need to do it. Because they're your friend and they deserve better. On the other hand, being nice is pretending you like your friend's loser partner despite everything. Sure, you'll be there for your friend when the relationship comes crashing down, but you probably should have spoken up earlier. Being kind requires honesty. Courage. Being nice just requires your presence. Don't be nice. Be better. Be kind.

Now that I've gotten the toxin out of my system, on to the news.

The biggest news, that doesn't involve moving, is that I finally finished the latest round of edits on my novel. I'm expecting to start querying it again in the next week and even entered it into the Pitch Wars contest. I don't expect it get very far since I'm a cynical asshole because I no self-esteem. Or I have no self-esteem because I'm a cynical asshole, depending on who you ask. Still, I march on. Let's hope I can sell this book before I'm dead.

I already mentioned that I'm the ML for my region when NaNoWriMo begins next month. Though, I haven't done too much about it. I've been holding off on planning the writing event because I've been too damn busy. Even as I type this, I'm waiting on the final task so I can complete the fiscal year-end at work. Step one will be to formulate a calendar/attack plan for the event and establish meetups with anyone will to listen to me talk about failing at writing for an hour or so. NaNoWriMo: spring break for writers.

Last bit for now. I finally got the results for the third quarter of the Writer of the Future contest. Another honorable mention. It's better than an outright rejection, but I still won't see my work published in any form. It's a so close, and yet, so far kind of feeling. The damnest thing is that I had a great idea for a short story in the middle of the night just last night. I didn't bother to write it down and now it's lost to the void. Just like my novel.

Until next time, and at all times, be kind.

Review: The Testaments

The Testaments by Margaret Atwood
My rating: 3 of 5 stars

There is a downside to high expectations. Mostly in the fairly obvious way that it prevents you from enjoying something for what it is rather than what you expect it to be. I try not to go into something with such forethought, but sometimes it can't be helped. You, dear reader, might be able to do better than I. But I doubt it. Not with as something as expectantly loaded as 'The Testaments'.

This book isn't a sequel to 'The Handmaid's Tale'. Nor is it a prequel. Nor any other type of 'quel' you can imagine. It is more of a companion. By expanding the lore by a few inches, it manages to carve out another story from the sad state of Gilead. While almost as depressing and poignant as the first novel, it has a larger scope and importance to the overall lore. Trying to answer questions about the old world nation-state while keeping the perspective on two seemingly inconsequential players. Like trying to tell the entire history of Battle of the Bulge from a single private in the 101st Airborne. You get a first-hand account. Lacking a better term, it's from the trenches. The problem being that you don't get a sense of scope while things are happening and the ending plays off as a little too overly dramatic because you never learn why things are important until after the fact.

For the most part, I'm happy I read this book. I doubt I would have been content with myself otherwise. It's just a fact that I didn't walk away impressed. It has problems with its narrative structure and a number of smaller things that kind of add up over time. However, I think its biggest problem is that it doesn't really have anything new to say. 'The Handmaid's Tale' is sometimes lumped in with science fiction because it answers one of Heinlein's big three questions: What if this goes on? Over the years since Handmaid was published, radicalized religion has gotten worse, not better, and the book's foreboding tale rings louder today than it did yesterday. With that in mind, it's nearly impossible to read a companion to that book and not expect something new out of it. I just didn't find it.

I know I've given better reviews to worse books, but I can't recommend Testaments beyond being in the know of its place in literature. And FOMO is a shitty reason to read a book. Not only does this book have a loaded expectation from its source material, but also has a high bar to climb in regards of who wrote it. There is no escapism here, and nor should there be. I know it might be unfair, but books have different standards for different reasons. Literature is placed not just by what is written, but why is it written. With 'The Testaments', its reasons just weren't good enough for me.

View all my reviews

Review: Gideon Falls, Vol. 1: The Black Barn

Gideon Falls, Vol. 1: The Black Barn by Jeff Lemire
My rating: 4 of 5 stars

All you need to know is that this is a good intro story into something much larger than what it is showing. That, and you'll probably love or hate it. As a first volume, it's intelligent but slow. You either go in for the long haul or you bail early. This is one you marry, not fool around with. I fully recommend you at least read this first volume. You'll finish with more questions than answers, but that isn't the point. It's all a matter if you care enough to keep digging and find out how far the rabbit hole goes.

The writing is good but can be a little uneven. Like I said before, it's slow. The main problem is that the book is trying to tell two stories at the same time, and they aren't equal in terms of pacing. In one story, you have almost entirely setup. Six issues in, and we're still wandering around looking for clues like the opening chapter of a grand novel. In the other story, the action is more immediate but still feels like a tease. There's more of an arc to the second story, which isn't a bad thing, but it's the contrast with the first that feels muddling.

In other news, the art is where it's at. At first, I wasn't sold on it. There's a graininess to it that can be off-putting at first glance. But behind the scratchy nature of it, you start to see patterns to make it some of the best art I've seen in a comic. What sucks about ninety percent of comics is that they're basically bad short stories with pictures. Going from panel to panel without any real interest in using visual art to help tell a story. Gideon doesn't do that. It instead fully invests the time and brainpower to utilize the art form. It might not always make sense, but it sure is refreshing.

I was originally going to give this book three stars. The opening issues spend too much time talking and not enough digging into the lore. It definitely has its pacing problems, but that doesn't mean it isn't a good book. It wants you to stick around but isn't willing to lower itself with cheap tricks in order to do it. Just make it to the end of the volume, you'll be pulled in and you're not going to want to come up for air.

View all my reviews

Review: Trail of Lightning

Trail of Lightning by Rebecca Roanhorse
My rating: 3 of 5 stars

Somewhere throughout reading this book, I came across the idea that this was the author's first novel. I double-checked to make sure I was right, as one should always do, and I was. As I usually am. There were just too many first author mistakes made that showcased such an aspect. Tendencies that more experienced authors would hopefully grow out of. A key example, several chapters end on a strong almost cliffhanger sort of note. The kind you would see on Star Trek right before they cut to commercial. The problem is that this was almost always followed by a short chapter to finish the conversation the characters were having right before the chapter break rudely interrupted them. Writing tip: Don't do that.

I could give several more examples of first-timer mistakes, but I don't want to sound like a writing professor. No one wants that. I'll refocus on the quality of the novel, which is best summed up as average at its best. The prose is decent, serviceable. Perhaps what it does best is world-building. Giving you just enough to maintain interest, but doesn't vomit out the entire history in the first third of the book. However, that maintenance to the pacing might be because there is plenty of room in later books due to this being a series. Because everything has to be a series these days.

This might also be due to this being a first novel, but there's a vagueness to the book. I don't mean in the prose. If anything the dialogue and descriptions is too precise. I mean in terms of the thread of the plot. Not in so much what is happening but rather in why is it happening. The main character, Maggie, is mostly led by the nose from plot point to plot point with things happening to her rather than because of her. The vehicle is moving, but Maggie isn't the one behind the wheel. There's only one part of the book, about 2/3rds of the way in, where she takes control. But then the book promptly hands her ass back to her and she returns to the passenger seat where she remains for the rest of the story.

Despite its problems, it's a decent book. Especially for a first novel. I did start to get bored by the end, mostly because another problem is it doesn't do a good job raising the stakes, but I was able to finish it without feeling I was wasting my time. There's a cultural element to it that I found refreshing, but I also can't comment if it's good or bad in its portrayal. This is mostly because I'm not qualified to do so and it would be foolish of me to pretend otherwise. That being said, you might enjoy this book if its issues don't stand out as much with you. It's a good light read, to say the least.

View all my reviews

Moving Pictures

Moving sucks. Good news is that we've set a goal for September 21st as the big moving day. It won't be the end of it, but at least we'll actually be living in the new house after that point. Assuming we can keep that date. The only writing news is that I've been named the municipal liaison for NaNoWriMo in my area. I'm stilling editing and waiting on all other fronts. Everything else is moving related.

For something completely different, I finished painting my room and here is the end result:

The big mural.

How this started was that I was staring at the blank wall wondering what the hell I was doing with my life. I had already resigned myself to doing a large mural but had yet to design it. I had recently seen Rembrandt's "Night Watch" and it had left an impact. Several thoughts later, I had the mural compulsively designed in my mind. The end product is 90% of what I envisioned. So proud of all my hard work I even initialed the damn thing.

Corners



The Door

Above the Shelf. I didn't paint the shelf.

 

The far side of the wall.

 





Window Wall. The latter is not a part of the art.

Squares. Ignore the Ethernet cables.

Well, that's my room. What sucks is that most of this will be covered by shelves, desks, and bookcases. But that's life. If you happen to run across this and have any questions/comments/praise/hatred, the comment box is below. It was fun to paint, but it took a hellish long time. Maybe by the time we move next I'll have forgotten how hard it was to do.

Review: Valley of Genius: The Uncensored History of Silicon Valley

Valley of Genius: The Uncensored History of Silicon Valley by Adam Fisher
My rating: 4 of 5 stars

Oral history books might sound like an easy book to write. Lazily copying and pasting the interviews into a readable format. However, once you dive into the final product, it becomes less clear as to the level of difficulty that was involved. The writer obviously has to interview someone. Just type out a transcript of an important person and call it a day. Though this book doesn't interview someone. It interviews everyone. Think of a name that's important to the history of Silicon Valley, and he/she/they are in here. How much it matters is up to you.

Genius does a good job sectioning the interviews by subject and timeline. For example, the interview with Steve Jobs appears throughout the book because it's cut up among the various topic and places in time he was involved in. The book more or less starts with Atari where most of the early figures of Silicon Valley, including Jobs, got their first tech jobs. Each chapter does a thorough run-through and history of each subject. Doing an excellent job of using interviews to tell an actual story. Which is where the book really shines. Using the voices of the people that were there to explain the beginning, middle, and end of a point in the valley's history.

The only real downside to a book of this format is the length. I couldn't help feeling this book would have been only half as long if the interviews were summed up rather than directly transcribed. Keep in mind I don't view the format as a bad thing. It's more of a point of order for someone else who is thinking of reading it. It might not be for everyone.

My only real complaint is the people in the book can be a little self-serving at times. It's not the book's fault, it's just holding up a mirror, but that doesn't change the fact it's there. In particular, the 'epilogue' had a lot of people smelling their own farts. As someone who has already used their smartphone three times since starting to type this, I really can't argue that Silicon Valley has been really important to our culture and history. But there was too much taking credit for the good while ignoring responsibility for the bad.

All in all, if you're the least bit interested in history and/or Silicon Valley, I would say this book is a must. It's extremely well put together and everyone who was someone is here. It even has Lars Ulrich.

View all my reviews