Category: Articles

Categories
Review

“Cosmic Cats and Fantastic Furballs”

Mary A. Turzillo

In general, I enjoy anthologies; it’s a whole bunch of little things, so generally, even if one of them is bad, the next one won’t be. That said, on the occasions where I consistently don’t like them, they’re an edge case in the way I think about books. In general, my rule is that I have to get something like 10-20% of the way through a book before I can determine that I just don’t like it and won’t be finishing it. With an anthology, I instead feel like I have to give each story a shot… and then the stories themselves are, almost always, too short to be worth skipping once I’m partially through.

Which is a long-winded way of saying that I didn’t really enjoy this one. There’s just something about the way that Turzillo thinks, or writes, that didn’t click with me. Oh well, it wasn’t terribly long; on to the next book.

Categories
Review

“Shards of Honor”

Lois McMaster Bujold

Somehow I had mixed this up in my head with the Honor Harrington books. Which isn’t much of a mystery; it’s space combat sci-fi, it’s got “Honor” in the name, easy enough to conflate.

That said, “Shards of Honor” was a good read; it’s got some Star Trek vibes in the beginning, but getting into the actual Space Combat Sci-Fi parts, it has a whole bunch of different vibes to it. The latter story arc got surprisingly comedic; I think it’s just the protagonist having a solid sense of humor as she faces adversity.

All in all, I enjoyed the read! Give it a go.1

  1. This is an Amazon affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I prefer Bookshop affiliate links to Amazon when possible, but in this case, the book wasn’t available there, so it’ll have to do. ↩
Categories
Review

“The Silences of Ararat”

L. Timmel Duchamp

This was an interesting little story; I see now why the collection it’s part of is titled “conversation pieces.” I quite enjoyed the process of piecing together the setting; vaguely in the future, definitely post-United States, with just a touch of magic. It reminds me of a book I didn’t finish, actually – The Fever King had a similar “the USA collapsed, here’s what it is now” kind of vibe going on, although that one was a lot more fantasy-forward.

An interesting read; I’d say it’s worth checking out.1

  1. This is an Amazon affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I prefer Bookshop affiliate links to Amazon when possible, but in this case, the book wasn’t available there, so it’ll have to do. ↩
Categories
Review

“That Wild Country”

Mark Kenyon

I went in with the wrong expectations here—I was expecting a purely-history book, and so the opening chapters being entirely autobiographical about this guy’s experience of going on hikes felt very weird. Over the course of the book, though, I adjusted to it being a split of history and autobiography, and I think Kenyon did as well, striking a better balance by the end.

It was nice that the book had, in essence, a thesis throughout: our public lands are the thing that truly makes America great, and we should be defending them against the predations of… industry and development, basically. And, as a bonus, this is something that we can build a bipartisan coalition around: “Cabela’s and REI” both agree that these public lands should be preserved for public use, if for slightly different reasons. But that’s the beauty of a multiple-use land arrangement; all the outdoorsy folks can do their thing.

Overall, I found this book quite enjoyable, and heartily recommend it. Check it out.1

  1. This is a Bookshop affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I use Bookshop affiliate links instead of Amazon because they distribute a significant chunk of their profits to small, local book stores. ↩
Categories
Review

“Queer Weird West Tales”

ed. Julie Bozza

“Queer science fiction anthology” might be my favorite genre, at this point. Save a couple creepy ones, the stories are almost all hopeful, and the last one in the collection was an excellent anchor to end on, a nice little redemption story. Definitely a bit predictable in what the twist was going to be, but it’s a 40-page short story, there isn’t that much room for surprise.

The ‘wild west’ framing is also a fun one, particularly in the handful of cases where the authors decided to twist what that actually meant. Really it’s more of a “frontier” collection than anything else, it’s just that “western” is the genre we think of for that concept.

Overall, quite enjoyable; give it a read.1

  1. This is a Bookshop affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I use Bookshop affiliate links instead of Amazon because they distribute a significant chunk of their profits to small, local book stores. ↩
Categories
Review

“Debunked”

Dito Abbott

Something like 100 pages in to this book I looked over at my sister and said “I can’t tell if I like this book or not, but hopefully I’ll figure it out by the end.” Here I am at the end of the book, and I’ve concluded that I did like it, although I don’t know if I liked it enough to go looking for the sequel.1

There’s parts of the writing that remind me of Terry Pratchett’s works for younger readers; the footnoting style is very reminiscent of that, really, but you can feel the different age group as the target demographic. I think the part I struggled with the most was the plot; the book feels less like A Story and more like a collection of setpieces strung together. A ramshackle lighthouse under siege during a storm! An airship full of strange creatures! A flying city next to a desert hurricane! A fortress library, suspended above the caldera of an active volcano! And, honestly, any one of these makes for a fun setting for some scenes, and a good little vignette, but piecing them all together into a coherent whole is… challenging.

That said, if you just want to settle in for a quick read with some solid comedy, this was a pretty good book. Go in with the right expectations, and have fun!2

  1. The book is very clear throughout that it is Book One of the series, it really wants you to know that it’s part of a series and there’s more books to read. ↩
  2. This is a Bookshop affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I use Bookshop affiliate links instead of Amazon because they distribute a significant chunk of their profits to small, local book stores. ↩
Categories
Review

“A Thousand Recipes for Revenge”

Beth Cato

Once again, a really interesting magic system—this time, focused entirely on food, although with a fun theological twist to how it works. In short, anyone can be a cook, but to make truly good food, you have to be a Chef: someone in possession of a tongue blessed by the five gods. Add to that the existence of magical ingredients, and the requirement that they only work when used by a Chef and blessed by the gods, and you’ve got a recipe for a very different course of history than we had.

And, wonder of wonder, this is an author that actually followed that. Some of the different cultures of continental Europe are vaguely recognizable, but which countries actually exist and what they’re called, entirely different. Which is very fitting, honestly; given how much of our history has been driven by arguing about capital-g God, if we had very clear miracles happening all the time, a whole lot of things would’ve gone very differently. There’s no need for converting people when the extremely-active deities are out there doing it themselves.

Wrapped up in that setting, there’s a very interesting story: a former military Chef, now in hiding for leaving military service.1 And, separately, a foreign princess, freshly arrived in this vaguely-France-inspired country to be married to their crown prince, sealing an alliance of their kingdoms. Where it gets fun is finding all the places their stories intersect; early on, it’s just a brief flash of “based on timing, I think that coach the Chef saw go by was taking the princess to the ball!” But as the story goes, you can find more and more moments like that.

Towards the end, the plot gets absolutely wild. Somewhere between an M. Night Shyamalan twist and a well-done Marvel story, in how it feels, but that’s all the spoilers you’ll get from me. Go read the book!2

  1. And, for reference on what time period we’re vaguely in, several of the chapter-start quotes pull from regulations and other materials that very clearly state that a Chef is the property of the Crown. ↩
  2. This is a Bookshop affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I use Bookshop affiliate links instead of Amazon because they distribute a significant chunk of their profits to small, local book stores. ↩
Categories
Review

“The Alchemist”

Paolo Bacigalupi

A sequel to The Executioness, and one that answered some of the questions I wondered about in that one! (If it seems convenient that I read them in this order, it’s because I read the jacket and decided to start with The Executioness so that I could end on the, presumably, happier note of someone figuring this out.)

Because of course bramble, even magical bramble, can’t be the end state. It’s too complex; entropy always wins in the end. And here, someone figured out the proper way to burn it so that it truly dies.

Unfortunately for me, that happened far too early in the story for it to be a happy ending just like that. Looking at how many pages you have left is a great way to stress yourself out about a book.1 Still, figuring out just what would go wrong, and how the protagonist would get out of it, made this one more of a fun read than the first. Check it out.2

As a fun follow-on, after I went to post this review: I have, in fact, read this before, and even posted a review here! It’s been long enough that I had no memory of that, so I’m posting a new one as well. I suppose you can compare Past Grey’s thoughts, if you’d like.

  1. I’ve got another one I’m working on that I’ve had to take a break from for a month or so, because everything is going great for the protagonist… and I’m just barely halfway through. Something is about to go horribly wrong. ↩
  2. This is an Amazon affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I prefer Bookshop affiliate links to Amazon when possible, but in this case, the book wasn’t available there, so it’ll have to do. ↩
Categories
Review

“The Executioness”

Tobias S. Buckell

This is one of those stories where the worldbuilding is executed incredibly well, and it leaves me with so many interesting questions. The short version: magic exists! But using it generates bramble—a plant that you apparently can’t kill, and whose thorns, in a very fairy tale fashion, make you fall asleep. I, of course, immediately start wondering about the sort of ecosystem this implies—because, given something like that, surely something has evolved a way to eat it, right?1

The story itself is… not fun, really, but an interesting read, at least. Worth giving it a go, as it was a pretty quick one.2

  1. Or, also a fun concept, maybe not yet! Which does imply that the combination of magic and bramble is, on an evolutionary timescale, pretty recent. And that puts me back into my common thought “how can I explain this magic system as actually being some kind of advanced technology from right before the sci-fi civilization collapsed back to these dark ages?” ↩
  2. This is an Amazon affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I prefer Bookshop affiliate links to Amazon when possible, but in this case, the book wasn’t available there, so it’ll have to do. ↩
Categories
Review

“First Test”

Tamora Pierce; graphic novel adaptation by Devin Grayson and Becca Farrow

I somehow missed that this was going to be a thing until the day before it was released. It took me something like ten seconds between finding out it was up for preorder and actually putting in the preorder; I consider it a testament to my willpower that I made it days after it was delivered before I finally let it jump the queue and be my next thing to read.

Keladry of Mindelan is my comfort reading. The visual treatment here brought me so much joy; it’s quicker to read than the original novel is, and I suspect I’m going to wind up rereading it quite often as a result. Sitting down to reread the Protector of the Small quartet is an investment, it’s what I’m doing with my reading time for a while. This, I can get through in something like an hour.

There’s a couple places where I could feel the edits, but for the most part, everything felt natural; sure, the story was abridged some, but all of it made sense.1

Two thoughts on this visual treatment, specific to that: my immediate thought upon seeing Neal was “he looks like Sokka!” and I sorta held on to that feeling throughout.2

And, even more so in this visual treatment where the words stand alone more, one of my favorite quotes jumped out at me. I was glad it made it in:

The short sword is the sword of law. Without it, we are only animals. The long sword is the sword of duty. It is the terrible sword, the killing sword.

It should surprise precisely nobody that I’m going to recommend this book. I grabbed the paperback—I think I already knew that this was going to be an oft-reread comfort book for me, and wanted the comfortable feel of a paperback to match that. Please, vote with your wallet; get them to do the rest of the series, too.3 I really want to see a baby griffin. And, weirdly, one of the killing machines.

  1. Well, okay, the fact that the Gift was shown (only twice) and was the same vague sparkles each time instead of being the color of each person’s magic, that bugged me a bit. ↩
  2. Hakuin Seastone also sorta reminded me of Zuko, although I think he’s a bit more Live Action TV Series Zuko than Animated Series Zuko. ↩
  3. This is a Bookshop affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I use Bookshop affiliate links instead of Amazon because they distribute a significant chunk of their profits to small, local book stores. ↩
Categories
Review

“The Silk Roads”

Peter Frankopan

Just like my last book review, I’ve got two thoughts; apparently it’s always two things with me. This time, it was two things that I actually did learn about in history class that this book helped me understand better than the classes ever did.

First, the American Revolution. As the output of the American education system, I’m well aware that it, basically, got started because Britain raised taxes on the colonies in what would become the US, and we all got mad about it.1 What this book pointed out is why Britain increased taxes — because, of course, they had to know it wouldn’t be popular, so it wouldn’t have been just for funsies, there had to be a reason. The reason, it turns out, was that they had just bailed out the British East India Company, and big bailouts require funding. Why did they bail out the British East India Company? Because the BEIC’s revenues from India had suddenly collapsed! Why did those revenues suddenly collapse? To summarize, because the company realized that, thanks to the magic of colonialism, the could just… not pay a living wage! To anyone! And so they didn’t. And then millions of people starved. (To those following along at home, the moral of the story is that you should pay people a living wage. And also, y’know, not do coercive labor practices in any way, shape, or form.)

Secondly, and let’s just go ahead and say right now that it’s not gonna get lighter in tone, was World War II. I very specifically remember thinking, in not only high school but also college-level history classes, “how did Hitler think invading Russia was going to go well, it’s like the canonical way to end a European empire.” It was never really explained, the best I ever got was mumbling about his egomaniacal tendencies and the need for “Lebensraum.” Which, to be fair, were factors. But this book did a lot better a job explaining a key thing: crops. The goal wasn’t to invade Russia, it was to take Ukraine—the bread basket of the USSR. And the issue wasn’t egonomanicism or greed, it was that Germany didn’t have enough food. Also on the list of things that can cause massive starvation: declaring war on everyone, dumping your entire economy into war matériel, and conscripting every farm worker with a Y chromosome. Plants may generally be able to grow themselves, but they don’t harvest themselves.

The book had a whole lot of other interesting stuff. I knew (and, let’s be real, still know) very little about Asian history, so a whole heck of a lot of this was new to me. The bits above are what I called out because they were revelatory moments about things I already knew about. A different form of learning to “this is brand new information” types of things. I found the book quite approachable, and the chapters were broken up fairly well—not tiny chunks, each one is still gonna take some time to get through, but reasonable enough. The naming pattern definitely got stretched thin after a while, but that’s probably less of an issue if you’re reading a print copy instead of the ebook where the chapter title is always visible at the top of the screen.

All in all, a good read, and I recommend it, Check it out!2

  1. “No taxation without representation” does point out that the lack of representation was also a key issue, but it’s not as relevant to my realization here. ↩
  2. This is a Bookshop affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I use Bookshop affiliate links instead of Amazon because they distribute a significant chunk of their profits to small, local book stores. ↩
Categories
Review

“Modern Software Engineering”

David Farley

Over the course of reading this book, I kept coming back to two thoughts.

Firstly, I think Farley undersells the advances that programming languages have made. He has a point that the level of bikeshedding about languages that programmers are capable of is too much, but treating it as completely nothing is throwing the baby out with the bathwater. Take an example close to my heart: comparing Objective-C and Swift, there have been some significant advances. The introduction, and use throughout the language and libraries, of optionals has functionally eliminated null-pointer exceptions. Memory management bugs are a massive category of problems, across all sorts of software. Look at Heartbleed, for example. If you’re using Swift idiomatically, and avoiding the (hilariously named) UnsafePointer stuff, this sort of problem cannot happen.1

Secondly, this book felt like the moment where in my mind I went “oh, we are getting there.” He makes a point early on that software engineering as a field has different standards of success than other engineering disciplines. Again, an example: this morning, I woke up to a truly terrible software bug in an app I use that had deleted several years worth of data. This is a bad bug, and I’m personally quite upset about that loss, but it’s not as bad as, say, the Tacoma Narrows bridge collapse. Subjectively, it feels like software as a whole has a lower bar for “is this okay to produce” than the other, physical engineering disciplines.

Where this book changed my opinion is in starting to feel like the field is beginning to coalesce around some standards. We’re nowhere near the level of “you have to use these techniques, and if you don’t you can lose your Software Engineering License and be prohibited from working professionally in the field,” but some of those techniques are taking shape.2 Farley’s argument is that the core of it is fast feedback, allowing for tight iteration loops, and from that it logically follows that test-driven development is the best option.

And yes, I’m sold! Just the other day, while doing some tinkering on a personal project, I found several bugs I’d created — because the tests I wrote before I started writing the code failed. That’s such a nice way to do things. And now, having written both the code and the tests, I feel much more comfortable with the idea of “oh, I’m going to need to reuse some of this logic somewhere else, I’ll just pull it out into a separate chunk.” I don’t have to spend an hour thinking through “what might break from this,” or testing things out. I just do it, run the tests, and know that I’m good.

As to the book itself: he’s hammering the same points over and over, as these sorts of books tend to do. I found it a generally good read, and took many notes for the book club discussion, but I don’t know that it was particularly world-changing… or if anyone else will have the same “eureka” feeling from it that I did. That moment came with a very clear sense of “all the other stuff I’ve read and done leading up to now came together into this idea.” It’s not a bad book, though, and could be a pretty good starting point if you’re just getting into the “read about the field” kind of thing, so check it out.3

  1. And I’m also setting aside the type checker, which is, for all intents and purposes, a form of mandatory unit testing imposed at compile time. Writing Swift, you don’t have to safety-check your inputs to make sure they’re the right types; the language does it for you. ↩
  2. I do absolutely believe that software engineers should be forming some kind of industry group and establishing shared standards for what “software engineering” actually means. ↩
  3. This is a Bookshop affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I use Bookshop affiliate links instead of Amazon because they distribute a significant chunk of their profits to small, local book stores. ↩
Categories
Review

“The Blindspots Between Us”

Gleb Tsipursky

This is one of those books where I wind up with a whole bunch of notes. Cognitive science: it’s neat stuff!

As with most of my reading, I have no idea when, where, or why I got this book; based on the title, I wasn’t quite expecting cognitive psychology, particularly not in a self-help sort of manner. Broadly, each segment is “here’s this problem that you have, because you’re a human and that’s just how human brains work; here’s some approaches you can take to mitigate that problem.”

The word ‘mitigate’ is important in there, though: there’s not a magic solution to any of these biases.1 The best you can do is be aware of these evolutionary foibles and try to catch yourself when they’re happening.

A thought that kept coming to mind, all the way through this book, was how much it reminded me of some of the excerpts of Tim Urban’s What’s Our Problem? that I’ve read. In his case, he uses a division between a Scientist Brain and a Caveman Brain, roughly; here, it’s the Autopilot System and the Intentional System. I tend to think of it as a three-part split, between lizard brain, monkey brain, and person brain, although that does present the issue of the person brain being outnumbered by the other two. On the other hand, maybe you should feel a bit outnumbered; the person brain is the slow one, whereas monkey and lizard brain are progressively faster.

Regardless, there’s a split between your higher-order thinking, stuff that makes it possible for us to, y’know, gestures at modern civilization, and the lower-order stuff that kept us alive through the majority of human history, before all the conveniences of modern life. Evolution is slow to change, and hasn’t even begun to catch up to what life is like now; and, back in the caveman days, the caveman who stopped to contemplate the social implications of running from the oncoming lion had lower odds of survival than the one who was in a dead sprint before the expensive, slow higher-order consciousness had even parsed that particular blur as “lion.”

This book is basically a list of ways that those monkey-brain reflexes trip us up in modern life, and hints for helping your person-brain deal with it. Which is, overall, quite a useful thing to be able to do! As a book, I mostly enjoyed reading it—it does have Self-Help Book Syndrome, wherein it provides a bunch of examples that are occasionally useful but mostly just come across as stilted and unhelpful—and recommend it. Check it out.2

  1. Well, as of this writing there isn’t. By the time you’re reading this, maybe we figured out some kind of brain implant technology that makes us all better at thinking about stuff. I can dream. ↩
  2. This is a Bookshop affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I use Bookshop affiliate links instead of Amazon because they distribute a significant chunk of their profits to small, local book stores. ↩
Categories
Review

“How to Read Literature Like a Professor”

Thomas C. Foster

If you pay attention to my reviews, you may notice a dearth of “literature” as a genre. This was my attempt to begin working on rectifying that; sadly, I don’t think it will have worked. This sort of literary analysis, tearing apart every decision the author made to try to find the symbolism behind it, just isn’t my cup of tea.

Which isn’t to say that this wasn’t a good book! I quite liked the way it served as an overview of the topic, to begin with. Beyond that, there were a couple things that really stood out to me as something of throughlines to the book.

First, that, roughly put, meaning is in the eye of the beholder. We each bring our own personal history, our own preconceptions and biases, to our reading. The things that strike me as meaningful are going to be different than the things that strike my sister as meaningful, but the two of us are likely to have more overlap than I would with someone reading the same thing in their home in Hong Kong.

Secondly, a professorial reiteration of the idea that there’s nothing new. It’s one big melting pot; in the same way that each reader has their own approach to the same book, each other has their own approach to the same ur-story underneath everything.1

So, overall, a useful introduction to/reminder of literary analysis as a concept. I remain… not sold on the whole field, but to each their own! If it’s of interest to you, this is a pretty good place to start.2

  1. This also, I felt, made an excellent addition to the arguments in favor of transformative works as a thing. If all of fiction is just remixes of earlier fiction, then what difference is there, really, between a fanfic and Dante’s Inferno? One is older, is all, and has attained respectability over time. ↩
  2. This is a Bookshop affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I use Bookshop affiliate links instead of Amazon because they distribute a significant chunk of their profits to small, local book stores. ↩
Categories
Review

“Perfect Software And Other Illusions About Testing”

Gerald M. Weinberg

Another book club entry, and a shorter one than usual, it feels like. I think the core concept is a good one to hold on to: testing everything is impossible, so you should be aware of what tradeoffs you’re choosing, and pick the ones that best meet your needs.

There’s some places in the book where, coming at it with Programmer Brain, I was annoyed at how long it took to explain something. Like yes, of course, you can’t test every possible system state, even just looking at a single small program there’s likely to be thousands of possible states, and that’s without addressing all the additional states created by the fact that programs don’t exist in isolation. The system they’re running on can impact them; the person using them can have a varying level of knowledge on using the program or the system; the program can be left continuously running for a long time, getting into ever more-complex possible states; heck, even cosmic radiation can impact program state.1

That complaint aside, there’s still a lot of useful ideas in there. Remember, the testers are not the enemy! But neither are they infallible. They are, in point of fact, people. Have empathy for them.

In all, a good, and reasonably quick, read about the software development process. Give it a go if that’s your type of thing.2

  1. Seriously, cosmic rays flipping bits inside RAM (or on various forms of longer-term storage media) is a real problem! ↩
  2. This is an Amazon affiliate link – if you buy it from here, I get a little bit of commission. It won’t hurt my feelings if you buy it elsewhere; honestly, I’d rather you check it out from your local library, or go to a local book store. I prefer Bookshop affiliate links to Amazon when possible, but in this case, the book wasn’t available there, so it’ll have to do. ↩