Tag: nonfiction

Categories
Review

“Deep Work”

Cal Newport

I’m of a thoroughly mixed opinion about this book. It’s a mix of good examples and aged-like-milk references, useful thought technologies and toxic productivity. Many of the best ideas are things I already do, and have been doing for quite a while—but I suspect they trace back to this book, as filtered through some of the podcasts I was listening to around the time the book came out.

To try to pull out the most useful pieces:

  • Deep work, intense uninterrupted focus, is the productive part of the knowledge worker’s day. Shallow work—checking email, going to meetings, responding to Slack messages—will expand to fill as much space as you let it, and is more about performing productivity than actually producing value.
  • Focusing on doing more deep work than shallow can improve your career, productivity, et cetera et cetera. Take as a given that that’s a goal; the book explains why, but many of the examples are where those “aged-like-milk references” come in.
  • A few techniques for doing this:
    • Embrace boredom and practice the skill of not picking up your phone/going online whenever you feel like it. This is “calisthenics for the mind.”
    • Have a fixed productivity schedule. Make a hard line that you’re done with work at (suggested time) 5:30pm, and don’t even touch your work computer/phone after that. Now, backsolve how you spend the rest of your work hours to make that possible.
    • Consider simply… not answering emails. If you do answer an email, don’t jot out a quick response, drop a tactical nuke of focused response—basically, try to accomplish a week’s worth of back-and-forth in a single, cringe-inducingly-over-written email. It’ll save you time in the long run.
    • Try block scheduling! At the start of the day, fill out every single minute of your calendar with things you’ll be doing. It’s okay if your estimates are wrong, and if you’re doing the Deep Work Thing, just ignore the block scheduled things, go back and rebuild the schedule once the Deep Work Thing naturally ends.1

I’m not going to pretend that this is a 100% complete summary of the book, but I do think I’ve hit the key points here. Even knowing—and doing—most of this already, I still found it useful to read: it made me focus on these thought technologies, and re-evaluate my use of some of them.2

One last fun thought I had while reading: he’s got a description of a hub-and-spokes model for office design. The hub is a common shared space, room for those Steve Jobs-ian ‘serendipitous moments’ of collaboration. The spokes are individual office, ideally soundproofed, to which one can retreat for focused deep work sessions. And I thought about that, and thought about the current3 vogue of combining hybrid in-office/remote work schedules and cubicle-farms, and wondered: have companies accidentally arrived at this hub-and-spokes model, on the scale of the week? The hub is the office, a cubicle or open-plan hellscape, and the spokes are the home office? That sure is a cost-efficient way to do it. Insidious.

Anyhow, I did wind up enjoying the read, and thought it was a useful consolidation of a bunch of helpful techniques, so I’m quite comfortable recommending it. Give it a read.4

  1. Protip: any given calendar software will let you have multiple calendars, and these can often be color-coded. My work calendar has the actual Scheduled Things I Must Do in red, and I do the block scheduling in blue, so I can see at a glance if that upcoming event is a thing I actually need to interrupt my flow to do, or if I can ignore it. ↩
  2. I’ve got some thoughts about adjusting my email and Slack usage, for one. I may write myself a little utility to just quit out of both those apps outside of designated Communication Times. We’ll see. ↩
  3. As of this writing – who knows, maybe by the time this scheduled post goes up, the style will have changed! ↩
  4. 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

“Paved Paradise”

Henry Grabar

Be still, my urbanist heart.

I loved this book. Being me, I probably still would’ve enjoyed it even if it was textbook-dry, dully reciting the history of parking policy in the United States, breaking for the occasional multi-page table of data. But that’s not what this book was. This was a wonderfully well-written piece, going through the surprisingly entertaining history of parking policy and arriving at the current state of affairs. (In retrospect, it should’ve been obvious that parking lots were ripe for corruption — in the same way that the number of gym memberships sold has very little correlation with the occupancy of the gym, nobody knows the actual occupancy rate of a parking lot, so if it’s operating on cash… who’s to know that you pocketed half the day’s receipts?)

I’d actually listened to two different podcast episodes about this book before picking it up to read, so I was already filled in on the key points, but I don’t think the book lost anything for that. It was the details that really captivated me—little mentions of things like “UPS got a $6 million discount on their New York City parking tickets by agreeing to pay them in bulk instead of individually disputing each one,” which by the omission really emphasizes exactly how many parking citations UPS picks up in NYC in a given year.

And I actually came out of this one feeling particularly optimistic. Not only do I live in one of the places that’s making a fair amount of the right sorts of moves to undo all that historic damage, but I’m also at the right time. We just came out of the pandemic, and boy was that ever a time for people to learn that… we can be doing better things with all that space? Outdoor seating at restaurants is great! Pedestrianized streets are awesome!

So hey, go read this one, it was super interesting. Absolutely worth the 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

“How to Invent Everything”

Ryan North

It’s a popular science book! We’ve got some overviews of lots of technologies, presented from a very fun conceit—this is the repair manual for a time machine, which opens with “step 1: accept that the time machine cannot be repaired. step 2: rebuild civilization from scratch.” The tone throughout is educational, though written by an under-paid employee of the time machine rental company, with just enough “for which Chronotix cannot be held legally liable”s thrown in to really hit that “this is a corporate material” vibe.

And here’s the thing: it works super well. It’s answering an exact thought I have had many times: if I had a time machine, exactly how well would I do at surviving and then improving the past? The answer was, of course, “not great.” After reading the book, I’d say it has improved somewhat… but really, I’d want to keep the book with me. Preferably a few copies. Laminated. Maybe a set of the printing plates, too, since they’re tougher than paper. Belt and braces, over here.

So, all in all, I absolutely loved this book. It set out to do a specific thing, and did it incredibly well. 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

“Managing Humans”

Michael Lopp

This was an interesting read — it absolutely feels like each of the many chapters is a blog post that got repurposed into being a book chapter, in large part because that’s what it is; this is Rands in Repose, The Book. A few bits of this I felt like I was skimming past—I don’t have any interest in writing a CV right now, thanks—but a lot of it I at least jotted a couple notes on. I may not be a manager, but having a better idea of how management works can’t be a bad thing.

Compared to my other forays into the ‘management book’ genre, I found this more approachable. Lopp does a better job of establishing his bona fides, both as Someone Who Works In Tech, and as someone who’s got the same sort of internet brain I do.1 He’s part of the old guard of bloggers. His writing is, in a word, approachable to my inarguably-a-nerd self.

So, overall, a good read; the book club discussion ought to be interesting, as well. I look forward to finding out how many other folks read the glossary all the way through—it was, in fact, worth it. Check it out.2

  1. He calls it NADD, which works well enough. ↩
  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

“Build”

Tony Fadell

I was honestly expecting a lot more of this book to fill me with that specifically “you’re insufferable” kind of rage, but aside from a couple brief appearances, it really didn’t do that at all. Instead, it was an interesting overview, both of Fadell’s career, and of a big pile o’ advice. Mostly it was targeted at the founder/CEO folks, but a fair chunk of it is applicable to those of us who haven’t drunk the Silicon Valley kool-aid and are content to not be the face of the place we work.

One through line I felt was the connection to Steve Jobs. It wasn’t as devoted to the man as, say, Make Something Wonderful was, there were really only a couple anecdotes about him, but his influence, his style, felt like it permeated the book. You can really tell that Fadell thought of Jobs as a mentor, and learned a lot from working with him.

This was an excellent choice for the book club at work; I heartily enjoyed it in that context, and am looking forward to the discussion.1 I think it’ll be a similarly good fit for anyone that works in tech, or doing product design; check it out.2

  1. Well, I’m running these on a bit of a backlog, so by the time you’re reading it, I will have already had the discussion. ↩
  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 Big Roads”

Earl Swift

I have, of late, fallen down something of an urbanism and transit policy rabbit hole. Although, I suppose calling it “of late” isn’t all that accurate, it’s apparently been the last couple years. Regardless, I have a certain set of existing thoughts about the interstate highway system, and thus came into this book with a certain amount of skepticism. It felt poised to be a glorification of the “open road,” a paean to the greatest infrastructure project ever undertaken.

And, for a while, it was, but just as the public feeling on highway construction changed at a certain point, so too did the book’s. We were no longer following the early motorists and their obsession, and instead delving into the fight against the freeways. Suddenly, we were seeing some of the same arguments that urbanists are still making today:

In retrospect, the survey’s were self-fulfilling—their yardsticks were motorist safety, travel time, gasoline use, and incidence of repair, all facets of the driving experience. The effects on those not using the roads were neither as easily tallied nor as eagerly sought.

The final part of the book felt very “bittersweet Americana” to me; we saw the retirements, fading into obscurity, and obituaries of the men1 who built the interstate highways. And at the same time, we saw the dream fading into the reality we got, culminating in this description that felt truly, deeply tired:

Interchanges have more in common with each other than any one of them has with wherever it happens to be. The twain have met; exit a California interstate, and you’ll find what you left in Connecticut—and very little that you didn’t leave in Connecticut. The interstates take a distillation of the broad American culture—a one-size-fits-all, lowest-common-denominator reading of who we are and what we want—wherever they go.

All in all, I found this a fascinating history. How many people know that the interstate highway system is properly titled “The Dwight D. Eisenhower National System of Interstate and Defense Highways”—much less that he really had no idea what he was signing, and his design for the highway system had approximately nothing to do with what was in the bill, much less what was built? I knew the first part, but thought he’d actually been, at least in part, the architect of the thing. I bought the story that the system was created based on his experience of the Autobahn during the war, and of a horrible cross-country “road” trip prior to it, not that it was an existing plan written up a decade before by engineers. Seriously, there’s plenty of new information in here—and quite a few wild characters, because it starts back before the automobile was even around, and boy howdy were some of those early motorists bonkers. I would up enjoying the heck out of this book, and highly recommend it; check it out.2

  1. And yes, they were all men; the only women really making an appearance anywhere in this book were the wives. I thought the “secretary treated as right-hand woman” of The Chief was going to be an exception, but at some point they began an affair, and he apparently celebrated the loss of his job by asking her to marry him. ↩
  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

“Make Something Wonderful”

The Steve Jobs Archive

I’m really not sure why I bothered being surprised that this book is beautifully-typeset. The story about Steve taking the calligraphy class at Reed shows up a handful of times, it’s very clear that typography was important to him, so of course the definitive book about his life would put a great deal of care into that aspect.

Beyond the typography, though, it’s clear that a great deal of care went into everything, from the selection of photos to the editorial aspect of which quotes to use and in what order. There’s even a one more thing after the index, which is the sort of touch that made me think, this book really knows who’s going to be reading it. The audience of this book is the exact sort of people who are excited about One More Thing, who have fond memories of One More Thing, who dream about One More Thing.

When you’ve lived your life in as much of a spotlight as Steve Jobs did, it’s easy to be quotable. There’s a lot of material available, particularly when the person doing the picking is your official archivist with access to things like your email archive. But I remain impressed with how well-spoken Jobs was, and how poignant some of the quotes were. Hindsight is 20/20, and sure can make someone look prophetic about their own life.

How many of you have seen the birth of another human? It is a miracle. And how many of you have witnessed the death of a human? It is a mystery beyond our comprehension. No human alive knows what happens to “us” upon or after our death. Some believe this, others that, but no one really knows at all. Again, most people of your age have not thought about these events very much, and it’s as if we shelter you from them, afraid that the thought of mortality will somehow wound you. For me it’s the opposite: to know my arc will fall makes me want to blaze while I am in the sky. Not for others, but for myself, for the trail I know I am leaving.

Steve Jobs, speaking at the Palo Alto High School graduation in 1996

I like to think that I’m not all-in on the Cult of Jobs, but there’s no denying that the guy was interesting. The book is free to read online, in a very well-made ebook form, so go check it out.

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

“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. ↩
Categories
Review

“Bad Gays”

Huw Lemmey and Ben Miller

This is a fun concept for a book: take the concept of “let’s talk about the forgotten gays of history” and focusing, instead of on the heroic ones, the villainous ones. I thought the choice of Hadrian for the cover art was weird, but the chapter on him… sorta explained that, and sorta didn’t? Like, my reading is that he was definitely a toxic boyfriend, but not particularly a villain beyond that, unless you want to count the inherent villainy of being a Roman emperor. And even then, by Roman Emperor Standards, he wasn’t actually all that bad.1

I have, in the past, bounced off books for being too academic in style, and this feels like it’s right around the upper edge of what I can tolerate in that way. It’s an interesting telling of the history, with a fair amount of citations throughout, but where I started to lose interest was where it got deep into… queer theory? Historiography? Something like that. Not a book to read when your brain is tired and you just want to gently process words, there’s too many moments demanding of deep thought for that. But then, sometimes that’s what you’re in the mood for.

Overall, though, I enjoyed the read! It’s a fun, if sometimes disheartening and depressing, skim through a specific subset of history. Give it a go.2

  1. This is, admittedly, a pretty low bar. ↩
  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

“Thing Explainer”

Randall Munroe

This was a really interesting book to read. The quick summary is that it explains things! (It’s a well-chosen title.) The trick is that it does so using line art and the 1,000 most-common words, in the style of Simple English Wikipedia. It’s a mix of genuinely useful information, decontextualization that feels like Strange Planet, and a surprisingly similar feeling to trying to read a book in a language in which you are not fluent. For as short a book as it is, it took me a long time to read it; I could only get through a few pages at a time, and then I had to go take a break to let my brain recover.

It is, however, quite fun to read. You’ll learn some things, and at the same time you’ll have a few moments of feeling proud of yourself for figuring out what the heck it’s trying to convey. It’s an educational puzzler. I had a lot of fun with 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. ↩