Summer Reading List 2024: Second

The world’s a mess, my life’s a mess, but at least I’m reading. Right?

Military History

Title: The Guns of August
Author: Barbara Tuchman
Genre: Military History
Year: 1962

World War I has always fascinated me. Ever since I was in the 6th grade, when I had a to choose a topic for a social studies project (that year was world history, and I had reached the early 20th century), I was hooked by the stories and the sheer scope of the Great War. My grade on that project was terrible—I almost failed, simply because there was just so much to learn that I couldn’t narrow it down enough, and didn’t have time to rehearse—but the memory remained.

Over the past decade, the war that had languished in relative obscurity all my life finally started to get back into the public eye. Mostly, that’s because of the centennial, the 100th anniversary of Archduke Franz Ferdinand’s assassination in June 1914. That milestone brought about the desire to make new media, whether movies (1917), video games (Verdun and its sequels, Tannenberg and Isonzo), web series (Indy Neidell’s The Great War), or music (Sabaton’s…er, The Great War). Many of these are excellent, and I’ve spent the past ten years basking in the knowledge that I finally got to be a history hipster.

But I haven’t read a book about WWI in decades. And I hadn’t planned on doing so this summer, either, until Elon Musk shared a list of his must-listen audiobooks. Since I don’t really care for audiobooks—I’m a visual learner—I downloaded them in written form, and I picked the first interesting one I saw that wasn’t 11 volumes. Sorry, Will Durant.

The Guns of August is a fairly detailed narrative, drawn from diaries, newspapers, the occasional eyewitness report, and other primary or good secondary sources. Its topic is, broadly speaking, the first month of the war. In practice, it starts somewhat before that, with the death of Edward VII, King of England. His death, and his succession by George V, created a power vacuum in a geopolitical landscape that was already growing increasingly tense. Europe had four years until war finally broke out (ignore the Balkan Wars for a moment), but the buildup had already begun. Edward’s death, as Tuchman argues in a roundabout way, set Europe on the path to war.

Most of us know the broad strokes of the summer of 1914. Ferdinand was shot in Sarajevo. Austria demanded reparations from Serbia; recall that this was before Yugoslavia existed, much less Bosnia. Favors were called in on both sides, drawing in first Germany, France, Russia, and Great Britain, then seemingly every other country in the world. Four years and many millions of dead young men later, the original belligerents peaced out one by one, ending with Germany signing the Treaty of Versailles.

As not enough of us know, that treaty was designed to be so ruinous that the German Empire would cease to be a nation able to project power abroad. Indeed, it was the end of the empire as a whole. Instead, the Kaiser’s rule was replaced with the decadent debauchery of the Weimar Republic, which served to suck out the marrow of the German economy while leaving its society fractured, fragmented. Exactly as we’re seeing in modern America, but I digress.

Anyway, Tuchman’s book isn’t about that part of the war. In fact, it leaves off as the Battle of the Marne begins, ending with a series of what-ifs that are tantalizing to the worldbuilder in me. What if the German armies hadn’t tried to do a forced march just to stick to their predetermined schedule of battles? What if Britain’s Field Marshal French hadn’t been swayed by a rare emotional outpouring from the normally stoic General Joffre? (Now I really want to write that alt-history!)

No matter what might have happened if things had gone differently in August 1914, the author makes it clear that what occurred in the weeks immediately prior to the German advance to the outskirts of Paris were pretty much set in stone. Before Franz Ferdinand was so much as cold, Europe was going to war. It was only a matter of when.


As far as the book goes, it’s a good read. It’s nothing brilliant, and certainly not worth a Pulitzer, in my opinion. The writing can be almost too highbrow at times, as if Tuchman is trying to capture the last gasp of the Victorian Era in words. To be fair, that’s how most of the major players talked and wrote, but readers even in the 1960s wouldn’t have been exposed to it except in literature classes. Certainly not when discussing military history. There are also scores of untranslated sentences in French and German, an oddity in a book written for English speakers.

The pacing is also very uneven. The Russians get a couple of fairly long chapters, but are otherwise forgotten; Tannenberg is practically a footnote compared to Liege. Conditions on a forced march get page after page of narration, including diary excerpts from soldiers, while the battles themselves are mostly reduced to the traditional "date and body count" sort of exposition.

If there’s any real critique of The Guns of August, it has to come from its very obvious and very intentional Allied bias. While the happenings in Germany and among the Kaiser’s generals are well-represented, they’re often cast in a negative light. When the Germans demolish a village in retaliation for partisan attacks, it’s a war crime and an international outrage. When the French demolish a village because they think they might need to put up defenses, it’s a heroic effort to save their country.

This is, of course, the same kind of thinking that still permeates the discussion about the Great War’s sequel. The "bad guys" aren’t allowed to take pride in their country. Their nationalism is evil; ours is sacred. (This line of reasoning also leads otherwise sensible people to praise Communists.) The simple fact is, the Weimar Republic was far worse than it’s portrayed, and the governments to either side of it on the timeline, whether Empire or Reich, were not as bad as they’re portrayed. Barbara Tuchman, being a student of her generation, can’t get past that. Even if she tried, I imagine her publishers wouldn’t let her.

Otherwise, The Guns of August is a worthwhile read for its subject matter. It’s a good look at the backdrop to World War I, something that occasionally gets lost among the trenches. Personally, I find it a bit overrated, but I’m glad I read it.

Summer Reading List 2024: First

It’s been about a month, and I finally made time to read something. Thanks to my brother’s timely discovery of a Youtube channel called "In Deep Geek", I got a little inspired for this one. Man, I hope that guy starts posting on a site that respects its users soon.

Biography

Title: The Nature of Middle-Earth
Author: J.R.R. Tolkien (ed. Carl Hostetter)
Genre: Biography/History?
Year: 2021

I don’t really know how to classify this book. It’s basically a collection of notes and scraps that Tolkien left behind. Much like his son Christopher’s History of Middle-Earth series, a ton of editing had to be done to make something readable. And…well, that didn’t quite work. The book as a whole is very disjointed, full of footnotes and editor comments and just a mess overall.

That makes perfect sense, though. Tolkien was probably the first great worldbuilder. He worked in an era without computers, without the internet. He had to write out his notes longhand. And there were a ton of those notes, because his constructed world began all the way back in the days before World War I. 1909, or thereabouts, was when he first started sketching out the conlang that would become Quenya. By his death, those earliest notes were senior citizens. There was a lot of cruft.

This book, then, is about organizing a lot of that cruft. In that, Hostetter does a good job. His is the job of an archaeologist, in a sense, as well as a forensic scientist. Oh, and a linguist, because Tolkien’s languages were ever the most important part of his creation.

The Nature of Middle-Earth, as its name suggests, gives us notes and drafts related to some of the fundamental questions and thorny problems Tolkien had to solve to give his invented world verisimilitude while also keeping it true to his long-standing ideas and ideals. After all, Middle-Earth is intended to be our world, just a few thousand years in the past. How many, exactly? It’s never stated anywhere in his published books, but this book tells us that Tolkien saw his present day—well, in 1960—as being about 6000 years after the end of LOTR. Convenient, that number, since it’s basically the same as what creationists claim.

And that brings me to the point I want to make. Our editor here repeats his own note a couple of times, emphasizing that Tolkien saw his world as a "fundamentally Catholic" creation. He was a Catholic, so that makes sense in some regard.

Much of the book—much of Tolkien’s corpus of personal notes—is thus about harmonizing a high fantasy world at the cusp of the Dominion of Man with the low, anti-human dogma of the Catholic Church. So Tolkien writes at length, and sometimes in multiple revisions, that his Elves were strictly monogamous, and that they didn’t reincarnate into different bodies. The men of Numenor were the same (except that he didn’t have to worry about reincarnation for them) because they had grown more godly.

In a few cases, Tolkien shows glimpses of a modern scientific worldview that was probably heretical in the churches of his youth. Sure, it’s all in an explicitly theistic framework, but he even accepts evolution for the most part; he can’t quite make the logical leap that humans are subject to it, too, but he meets science halfway, which is more than most would dare.

There is also a glimpse of what I’ve previous called "hardcore" worldbuilding. Tolkien was, of course, a master of that, but The Nature of Middle-Earth shows the extremes he was willing to go to for the sake of his creation. Multiple chapters are taken up with his attempts at giving believable dates for some of the events that were considered prehistorical even in the tales of The Silmarillion. In each, he went into excruciating detail, only to discard it all when he reached a point where the numbers just wouldn’t work. I’ve been there, and now I don’t feel so bad about that. Knowing that the undisputed master of my craft had the same troubles I do is refreshing.

All in all, most of the chapters of the book are short, showing the text of Tolkien’s notes on a subject, plus the occasional editorial comment, and the copious footnotes from both authors. We get to see how the sausage is made, and it’s sometimes just as disgusting as we’d expect. Not one reader of LOTR or The Silmarillion cares about the exact population of each tribe of Elves, or what the etymology of Galadriel’s name indicates about her travels, but Tolkien isn’t writing these things for us.
When worldbuilding, we authors do so much work not because we expect to show every bit of it to our audience, but so that the parts we do show are as good as they can be.

If this book has any lesson, then, it’s that. Worldbuilding is hard work. Worse, it’s work that accomplishes almost nothing in itself. Its sole value is in being a tool to better convey a story. Perfectionist and obsessive that Tolkien was, he wanted an answer to any plausible question a reader might ask. But he also wanted to create for the sake of creating. Remember that the intended goal of Middle-Earth was to become a new mythology, mostly for the British peoples. When you set your sights on something that sweeping, you’re always going to find something to do.

Summer Reading List Challenge 2024

Is it already that time of the year? 2024 seems like it’s just flying by, or maybe that’s because I’m old now. Whatever the case, it’s Memorial Day, and that means time to start a new Summer Reading List challenge! Take a look at the original post if you want to see how this all started. If you don’t really care that this is the 9th straight year I’m doing this challenge, then read on.

The rules are the same as always, because they just fit the challenge perfectly. As always, remember that the "rules" presented here are intended to be guidelines rather than strictures. This is all in fun. You won’t be graded, so all you have to do is be honest with yourself.

  1. The goal is to read 3 new (to you) books between Memorial Day (May 27) and Labor Day (September 2) in the US, the traditional "unofficial" bounds of summer. For those of you in the Southern Hemisphere reading this, it’s a winter reading list. If you’re in the tropics…I don’t know what to tell you.

  2. A book is anything non-periodical, so no comics, graphic novels, or manga. Anything else works. If you’re not sure, just use common sense. Audiobooks are acceptable, but only if they’re books, not something like a podcast.

  3. One of the books should be of a genre you don’t normally read. For example, I’m big on fantasy and sci-fi, so I might read a romance, or a thriller, or something like that. Nonfiction, by the way, also works as a "new" genre, unless you do read it all the time.

  4. You can’t count books you wrote, because they obviously wouldn’t be new to you. (Yes, this rule exists solely to keep me from just rereading my books.)

Social media is an awful place these days, and even my usual fediverse haunt is in flux at the moment. I’ll try to post on my alt @nocturne@bae.st, but don’t hold your breath. Instead, just wait for me to write something here. Of course, you can post wherever you like, even if that’s to Facebook, Twitter (I’m not calling it anything else), or something weird like Threads.

Have fun, and keep reading!

Summer Reading List 2023: Final

Coming in under the wire yet again this year. I have my reasons, though. The woman I love had a lot of…misfortune this summer. A man I’m beginning to despise has denied me a fortune of my own. And then we have all those other trifling things happening in the world, but I digress.

Fantasy

Title: Dawnshard
Author: Brandon Sanderson
Genre: Fantasy
Year: 2020

Before I start talking about the book itself, I need to tell the story of how I got it. This was not just something I picked up on Amazon, you see. In fact, I thought it was an ebook-only release, since I’d only ever seen it listed with electronic versions. That, to me, meant that I’d have to give it a miss.

I prefer physical copies for multiple reasons. One is simple texture: I love the feeling of a real book in my hands. That’s why I was so excited to be able to get real paperbacks of Nocturne, Before I Wake, and my other novels. The pleasure of reading real words on real paper is something no screen can match.

Beyond that, I avoid purchasing ebooks because I know that I wouldn’t really be purchasing them. Because of DRM and other nastiness, electronic media sidesteps the traditional first sale doctrine, which basically states that once you buy something, you own it. Publishers, greedy leeches on society that they are, hate this, so they long ago introduced artificial scarcity into online shopping. (It’s not only in books. Steam turned gamers into a culture of renters. TV and movies are now primarily streamed, where their very existence is ephemeral and fluid in a way no physical copy could ever be.)

So I thought I’d never have a chance to read Dawnshard by "legal" means. But then my partner and I went on vacation.

We went to Gatlinburg in April. If you don’t know Tennessee, Gatlinburg is the closest thing we have to a mountain resort. Definitely not an Aspen or Lake Tahoe, but maybe a very slimmed-down Vail or Snowshoe. It’s a beautiful place for a mountain-lover like me, and it’s only about a three-hour drive from where I live. Ahem. Where we live.

In this little hideaway, far from the ski lifts that were closed for the season, the nature park with its four-hour line (and 60 dollars I’ll never get back…), and the bustling town next door, there’s a back road that leads through the Gatlinburg Arts & Crafts Community. We went there searching for fudge on the one rainy day of our trip, but there was something even better across the street from the mediocre fudge shop.

Indie bookstores are a dying breed everywhere, but this one seemed almost perfectly placed in our journey. I’d seen it on the map, so I knew I wanted to check it out, but I thought it’d be a quick little peek and nothing more. Instead, my partner found no fewer than six books that interested her, plus the self-guided journal I talked her into getting.

As my tastes are more eccentric, I doubted I’d find anything worth buying. Indeed, the fiction section was mostly full of woke nonsense, as is common throughout the industry now. What was left after I ignored all that didn’t leave me enthused: multiple copies of A Song of Ice and Fire books, way too much Stephen King, and a handful of oddities. And Dawnshard, in a pocket hardback format. I was so surprised that I showed it to both my partner and the bookshop’s sole employee—he seemed almost as amazed by its presence. And now I had something to remember The Next Chapter besides the freebie bookmarks.


That’s the story behind my copy of this book. What about the story itself, though? Well, it’s a typical Sanderson tale, really, just in a much condensed format. This is the first time I’ve read one of his shorter works—Dawnshard is basically an oversized novella, about the same length as one of my mainline Otherworld stories—and I have to say that the pacing is dramatically different.

The plot is kind of a side quest for the Stormlight Archive series. It follows a couple of random B-team characters (Lopen, the one-armed guy whose dialogue has a lot of made-up words that make me imagine him as Hispanic; Rysn, who was so forgettable that I can’t even remember which book she’s from) as they search for…various things. It’s a Pirates of the Caribbean bit of swashbuckling, in a way. Almost the entire story takes place at sea, far enough from the main series’ action that it isn’t necessary to read it.

Of course, knowing Sanderson, he’ll find a way to tie it into everything else. And I don’t just mean the Stormlight Archive, either. This is a part of his own little cinematic universe, after all, and there are vague references to the Mistborn books and probably others that I missed because I haven’t read them. These don’t overpower the story, because there just isn’t room for much more than name-dropping.

What I like best about Sanderson’s works is the worldbuilding. Even in its meager 280 pint-sized pages, Dawnshard delivers on that. As always, the world of Roshar baffles with its sheer alien nature. Now that it’s canon that this world is being affected by beings from other worlds in his shared universe, though, that takes things up a notch. Now we get to see his take on the old "ancient guardians protecting something too mysterious for mere mortals" trope.

As you may expect, I utterly detest that trope, and that’s because I reject its very premise. There is nothing in this world (or any other) that is too dangerous to be known. Knowledge is power, but knowledge is also humanity’s birthright. So you’ll never catch me rooting for the guardians, even if their intentions are shown to be completely honorable. In this case, they aren’t—that would make for a boring story, to be honest—and they’re thus the bringers of conflict.

All told, Sanderson handles that conflict well. He doesn’t get bogged down in the minutiae of battle (as he did in Rhythm of War) or lose himself in intricate plots. The pacing is swift, and the action flows in a way that even Mistborn couldn’t manage. Either he’s grown as a writer over the last 20 years, or this format suits him better than thousand-page doorstops. Of course, the prose is still a little clunky, but even that is improving. (On a side note, can somebody out there teach him how to make a proper conlang? From the names and the few words he tosses in, I assume Rysn and her people are supposed to be some kind of Slavic analogue, but the sheer lack of vowels hurts my head.)

Dawnshard is a good read, and a good way to wrap up an eventful summer. It’s nothing special or spectacular, because it just isn’t big enough for that. Instead, it’s…cozy. And yes, that opinion is very much colored by the circumstances by which it came into my life. For a book where supposed fate is a major plot point, that makes sense.

Summer Reading List 2023: Second / Great Books 05

Here’s a nice little bit of synchronicity or kismet or whatever you call it. The second entry in my Summer Reading List challenge for this year also gets to cover one of the slots in my Great Books challenge!

Literature/Theater

Title: Tartuffe, or The Hypocrite
Author: Molière (Jean-Baptiste Porquelin)
Genre: Theatrical Comedy
Year: 1664

Yep. I read a play. First time I’ve done that since high school, and the first time ever that I’ve done it willingly. Since I neither understand nor like French, I used the modernized English translation available from Project Gutenberg. I’m sure there are a lot of translation errors and cases where the original meaning of the text is lost, but…whatever.

Anyway, Tartuffe is basically the French Enlightenment equivalent of a sitcom. It’s a five-act play about an aristocrat of the time who has been swayed by the words of a so-called holy man (the titular Tartuffe) to the point where he’s willing to give this charlatan his estate and even his daughter. The patriarch, Orgon, spends the first three acts defending Tartuffe as his family and servants call out the man’s hypocrisy. Only his mother has his back, seemingly for her own ends—her intentions are never made clear.

As the story progresses, Orgon’s son hides in a closet to overhear Tartuffe attempting to seduce the lady of the house, Elmire. The young man then confronts his father with evidence of the hypocrite’s ill will, only to be cast out of the house and, in effect, disinherited. Elmire (who is actually Orgon’s second wife, and thus the boy’s stepmother) then goes as far as possible in letting the impostor seduce her while her husband is watching from under a table. That finally gets Orgon to see reason, but by then it’s too late: Tartuffe already has the deed to the house.

The final act is all about this bit of trickery, and it ends with one of the most blatant uses of deus ex machina imaginable: a royal officer (this is pre-Revolution France, remember) stops the eviction of Orgon’s family, saying that the king himself saw through Tartuffe’s lies. Then follows a classic "no, you’re the one being arrested" scene and a bit of moralizing about moderation from Orgon’s son.

All in all, it’s a very modern tale for being 350 years old. The scenario of a hypocrite or just a stranger with ulterior motives enthralling someone beyond reason with his words is commonplace in modern books and movies. (The first example off the top of my head is the character of Gríma Wormtongue in Lord of the Rings, but others abound.) And the fact that Tartuffe is supposed to be a man of God only brings to mind the actual hypocrisy of so many evangelists.

But the comedic elements are what make the play shine even in written form. There’s this tension between wanting to be serious about the situation and wanting to tell it in a humorous way that just works and makes the whole thing a delightful read. It’s also pretty short—170 double-spaced screen pages on my ebook version—without a lot of digressions. Imagine it as a two-hour comedy movie, but one of those British-style comedies. While it goes for low blows on occasion, there’s a cerebral quality to it. Well worth checking out, if you ask me.

Summer Reading List 2023: First

I’ve had a hard time reading lately. My relationship took a disastrous turn last week, which put me behind even further than I’d like. But I’ve managed to push through the adversity and finish one of the goals I’d set for myself. Here we go.

Technology/History

Title: Now the Chips Are Down
Author: Alison Gazzard
Genre: Tech History
Year: 2016

Now the Chips Are Down is another entry in the MIT Press "Platform Studies" series. The series started in 2009 with Racing the Beam, a deep dive into the Atari 2600 and how its very peculiar implementation shaped the American video game market. Since then, a variety of authors have written about a variety of creative platforms. Most are game consoles, such as the NES (I Am Error) and the Wii (Codename Revolution), while some are home computers like the Amiga (The Future Was Here). A few don’t seem to fit in, such as Macromedia Flash (Building the Interactive Web) and the Amazon Kindle tablet (Four Shades of Gray), but there’s a cohesion to the series despite that.

This book falls into the "home computer" category, but it’s a very specific one that I’ve never used and never even seen in real life: the BBC Micro. As its name suggests, this was a computer built—well, contracted—by the British government.

Back in the late 70s and early 80s, the BBC was well-respected as an impartial presenter of the news. Today, of course, it’s a leftist propaganda outlet little different from the New York Times or Washington Post, but the Thatcher era was a different time. This was back when governments cared about building up their constituents, making them more informed, not less. As the UK was a technological backwater, missing out on many of the advances taking place in the US at the time, they needed something special to create the kind of digital literacy we now take for granted.

Their answer was the BBC Micro, a fairly large and expensive 8-bit home computer. Built by Acorn—the creators of other also-ran computers like the Atom and Archimedes—using the same 6502 processor that almost everyone else used, the BBC Micro had a few additions that made it unique to its time and place. Open, accessible expansion ports encouraged tinkering. Manuals described programming, an absolute necessity for computer owners in the years before I was born, in better detail than most of the competitors’ offerings, and the included dialect of BASIC is still regarded as one of the most advanced. The thing even had an adapter for Britain’s early attempt at a nationwide on-demand streaming service: Ceefax.

All this was part of the UK government’s attempt at getting its citizens, especially children, both interested in and comfortable with computers as tools. And that’s admirable. Too often today, we see the opposite: computers are expected to be black boxes, mere appliances that do whatever their creators tell them. The hacker spirit is actively discouraged through social and even legal means. But again, Britain circa 1981 was a different place. This was a country afraid of losing what little remained of its status on the global stage.

Gazzard harps on this point repeatedly in the book, always trying to paint the BBC Micro as innovative because of its intentions. It was used in education, for gaming, and as a way to connect people together. Okay, that’s great. The thing is, all that was happening with American home computers, too. And minicomputers in academia, and…well, you get the picture. The fact of the matter is that Britain really was behind the times, and no amount of praise for a government program can change that.

The book itself is light on details, and completely devoid of screenshots. The text has a few obvious typos, formatting errors, and grammatical mistakes. This is not the level of quality I expect from a Platform Studies book. The veritable fawning over the platform is a little over the top, though it is a welcome change from Super Power, Spoony Bards, and Silverware, which was written by an author who let his apparent hatred of the Super Nintendo shine through in his introduction and the tone of the book as a whole.

It’s good to be a fan of something. There’s nothing wrong with a nostalgic love letter. In this case, however, the nostalgia is just too thick. Any developer or even gamer who knows even the first thing about Elite knows it started on the BBC Micro, yet Gazzard feels the need to remind us of this on multiple occasions in the chapter about the game. She also dedicates full chapters to a low-budget educational adventure game and a Boulder Dash clone, acting as if these were innovative. But the truth is different. Oregon Trail came out years before Granny’s Garden, and it’s still played today. In the Repton chapter, she even admits that games with level editors already existed.

Overall, that’s the glaring flaw of Now the Chips Are Down. It’s actually too nostalgic, and that nostalgia gets in the way of the history. There aren’t enough whys or hows in the narrative, and I feel that’s where it falls short. Racing the Beam set the gold standard for the series. I Am Error and The Future Was Now both met it, and even exceeded it in places.

Here, there’s just no substance. The final chapter, for instance, combines Acorn’s future after the BBC Micro—they went on to create the ARM architecture, a curse for developers everywhere—and the Raspberry Pi, which started as an attempt at recreating the educational aspects of the platform. But the text is just so rushed. It feels like Gazzard is bored and wants to get through it so she can work on something else instead. And while this book, written in 2016 as it was, is mostly free of wokeness, there’s way too much emphasis on the sole female engineer on the Acorn team.

I did learn from this book. For that, I’m glad I read it. It makes me curious about a platform I’ve never used. I wonder why it was special, and why it’s so loved 40 years after its release. But Now the Chips Are Down doesn’t give me any answers except the author’s 200-page statement that boils down to, "I love it, and so should you."

Summer Reading List 2023

Here we go again. Sorry for being a little late on the post this year, but real life is increasingly becoming a factor. Once again, it’s time for my favorite annual tradition, the Summer Reading List challenge. I’m hoping to complete it for the 8th year in a row, and I’ll eventually get anyone else join in.

The rules haven’t changed from the beginning. They’re so unchanged, in fact, that I’m just going to copy them verbatim from last year’s post. The only added wrinkle for me is that I’m also doing my “Read 12 Great Books in 2023” challenge, so I’ll limit myself to only counting one of those for the Summer Reading List.

Really, they aren’t rules, but more like guidelines. This isn’t a competition. It’s a challenge. What’s important is that you’re honest with yourself.

  1. The goal is to read 3 new books between Memorial Day (May 29) and Labor Day (September 4) in the US, the traditional “unofficial” bounds of summer. (For those of you in the Southern Hemisphere reading this, it’s a winter reading list. If you’re in the tropics…I don’t know what to tell you.)
  2. A book is anything non-periodical, so no comics, graphic novels, or manga. Anything else works. If you’re not sure, just use common sense. Audiobooks are acceptable, but only if they’re books, not something like a podcast.
  3. One of the books should be of a genre you don’t normally read. For example, I’m big on fantasy and sci-fi, so I might read a romance, or a thriller, or something like that. Nonfiction, by the way, also works as a “new” genre, unless you do read it all the time.
  4. You can’t count books you wrote, because they obviously wouldn’t be new to you. (Yes, this rule exists solely to keep me from just rereading my books.)

As always, I’ll search for something new (at least to me!) and share it with you when I’ve finished reading it. I’ll post it over on the fediverse (mikey@freespeechextremist.com is my main account there for the time being) and in more depth here at PPC, but feel free to discuss your own reading adventures wherever you like.

Have fun, and keep reading!

Summer Reading List 2022: third

Coming in under the wire this time, but I have my reasons. See yesterday’s post if you’re wondering about those.

Business

Title: The Phoenix Project
Author: Gene Kim, Kevin Behr, George Spafford
Genre: Business/Fiction
Year: 2013

This one was, in a way, assigned. My predecessor as CTO, who is now an investor and board member, suggested I read it as part of training for a position that I will freely admit I am still unprepared to hold. That said, it wasn’t all bad. I could justify reading it during working hours if I had downtime, so there’s that.

The premise of the book is that it’s a guide to implementing DevOps practices, but disguised as a novel. The story follows Bill, an IT manager at an automotive corporation, as he attempts to right the sinking ship his company has become. Their latest creation, the titular Phoenix Project, is long overdue and far beyond its initial budget, but the company is in such disarray that they can’t make any headway on it. Instead, management pushes them through a disastrous deployment, and our hero is left to clean up the mess.

Yeah, I get that. And I get how it relates to my own position. We’re pretty close to that rollout right now, so the advice is…timely, I suppose.

As non-novel novels go, it’s not too bad. Characterization is scant, dialog sometimes feels forced, but the story progresses in a relatively normal manner. It reads like a novel, not a manual, although the manual qualities come out a lot more often than in other attempts at the format. (Is there a Manga Guide to DevOps yet? There should be. That might actually get me interested in the art style!)

If the book has any major failing, it’s that far too much of the “story” revolves around the Mary Sue character of Erik. He isn’t there to create or resolve conflict; his only purpose is to recite MBA mantras cloaked in mystical thinking. As you probably know, I detest mystical thinking. It’s why I couldn’t continue CBT. It’s why I tried to reinvent humanism. When people start blathering about threefold paths and pretending their way is the only way, that’s when I tune out.

So it was here. For the business improvement aspects of The Phoenix Project, I would rather read a bulleted list than the monologue of an author insert. At least then the lack of criticism and skepticism surrounding it would make sense.

Despite that, I consider this a good read, but only because it has useful information. Forget the story part. That’s nothing to write home about. But the business advice, even presented in this form, does have merit. And that’s not a bad way to end the summer.

Summer Reading List 2022: second

This one took a lot longer than I anticipated, due to all the upheaval in my life. I’ll have to rush to finish the third before Labor Day, but I think I can pull it off.

Nonfiction

Title: I, Citizen
Author: Tony Woodlief
Genre: Political Science
Year: 2021

“A blueprint for reclaiming American self-governance,” reads this book’s subtitle. Knowing me, you’d wonder how I managed to miss it until a fediverse friend posted about it a few months back. I’m glad he did, because it was an interesting read. Not great, mind you, but interesting.

Woodlief introduces the problem that we already know, but in more detail than anyone would think to provide: America is divided, almost irreconcilably so. Our hyperpartisan country is tearing itself apart before our very eyes, and everything the so-called elites do only seems to make things worse. Of course, that’s by design, which he explains fairly well.

This isn’t how America is supposed to be. Our founding documents make no mention of parties—except for a denunciation of them in Federalist #10—or lockdowns, or social justice, or any of the other problems plaguing the United States of today. We have, at some point, turned our collective backs on the guiding principles of our nation, and only a return to that tradition would stop the coming calamity. All that is well and good. When he sticks to the topic, the author does a good job laying out the reasons for our fall and the things we need to do to avert it.

Unfortunately, Woodlief spends far too much of this book getting off topic, or making illogical leaps that only serve to paint him as just another Washington hack trying to make a quick buck. His “solutions” are only found in the final chapter, and he spends most of that trying to convince people to join his network of do-nothing think tanks. Yes, this push is prefaced with some sensible advice about love and community, two things sorely lacking in modern society, but his only guidance to build those boils down to, “Join a church.” For the growing numbers of us who find Christianity (or religion in general) distasteful, that’s no help.

It gets worse than that. The author’s true colors can be seen throughout the book, in fact. Often, he falls victim to the fallacy of false equivalence, painting both major parties as equally responsible for the decline in community. But only one “side” is censoring its opponents. Only one party is sending jackbooted thugs after its political rivals. Woodlief wants us to reach across party lines, but who would extend a hand in friendship to those who have spent the past two years wishing death on us? The truth is, some very vocal people in America want nothing more than to destroy America. Yes, he’s right when he says these make up the minority, but they wield power far beyond their numbers, and he’s wrong not to call that out.

Likewise, the final chapter makes mention of the dictatorial edicts of state governors during the so-called pandemic, as this book was written in 2021. But Woodlief only calls out the most heinous offenders: Whitmer and Cuomo. Never mind that 49 governors (all but Kristi Noem of South Dakota) are culpable in this destruction of basic human rights. The author is a traditional conservative, so Republicans like Bill Lee and Greg Abbott were…just following orders?

My last gripe is much more minor, but it illustrates the underlying hypocrisy of the book. In every case, Woodlief refers to the “Founders”. The correct term, as any student of history knows, is “Founding Fathers”. They were all men, and there is nothing wrong with that. To use the politically correct phrasing shows the same spinelessness that is part and parcel of any conservative call to action.

To be sure, this is an informative book. It’s a good book. But it’s not a blueprint for regaining our rights. Nowhere in it does the author talk about, for example, how to get Critical Race Theory out of schools, or how to reform police departments so they can be held accountable. His advice can be summarized quite simply as, “But if we talked to each other…”

Maybe that made sense in 2021. Now, though, we may very well be past the point of talking.

Summer Reading List 2022: The beginning

One down, two more to go. I had started a couple of nonfiction books, but they just haven’t been holding my attention. So let’s go with a novel instead.

Fiction

Title: Blood of Empire
Author: Brian McClellan
Genre: Fantasy
Year: 2019

This is the culmination of the second trilogy in the Powder Mage universe, one of my absolute favorite fantasy settings ever. And that includes the ones I’ve made. (To be perfectly honest, at least one of them came about because of the original Powder Mage series.)

I’m just going to say this right now: I loved this book. It took four days to read, longer than its 650 pages would indicate, but that’s because I read it before going to bed each night, and work means I can’t do the eight-hour marathon reads anymore. But every minute was worth it. Every page was worth it.

With what’s effectively the sixth and final book in a series, you would expect a lot of action. And you certainly get it. This being epic fantasy with guns, you’d expect something climactic and almost apocalyptic. You get that, too. At no point did I feel like there was a wasted chapter. Some scenes did drag a little, but the pacing was relentless almost the whole time.

If anything suffered, it was the characters. Vlora, one of the three protagonists throughout this series, seemed a little dull. Part of this was because of her story arc, which involved recuperating from a near-mortal injury at the end of the previous book; that’s forgivable, though it was odd that she became the character I was least interested in reading. Of the other two, Styke was good at the beginning and end, but otherwise felt…impotent; Michel (note: he and I do not share a name!) actually grew on me. The rest of the cast, however, struck me as lackluster. They were there because of the action, rather than being the causes of it. In other words, this is very much a plot-focused novel, not a character-focused one. But that’s epic fantasy for you.

It’s a small price to pay, if I’m honest. It was good to let go for a change, to turn my mind off and get lost in a world again. And what I read felt like the end of an era. The storylines were resolved, although McClellan did leave a tantalizing hook for a future sequel; that annoyed me at first, because it seemed like the perfect excuse for a set piece. We also got an almost literal deus ex machina and a country full of ginger ninjas. I don’t know whether to count those as points for or against.

Most importantly for today’s world, I feel, is that Brian McClellan was able to write without getting bogged down in external politics. Yes, half of the Adran generals are women. Quite a few of the men are, to put it in internet parlance, cucked. Yet that never causes a problem. There’s a very, very oblique reference to one of the enemy leaders possibly being a lesbian, but even that’s more of a footnote, rather than the blazing neon sign some other authors would use. Nobody is going on about trans rights or other nonsense. The racial issues are handled very well. That’s refreshing to see, and I think it helped my enjoyment of the novel.

Riflepunk, like any other subgenre of fantasy, isn’t for everyone. But if you’re interested in mixing magic with firearms, the Powder Mage series is one of the best introductions. Start with Promise of Blood. By the time you get to Blood of Empire, you’ll be as hooked as I am.