Season of Storms: A Legend is Born by Andrzej Sapkowski, translated by David French, 3/5
On a scale of literary quality, this is much closer to Jim Butcher than J.R.R. Tolkien, but it is still good fun. In my opinion, the author writes violence much better than romance, so this book was an improvement on the previous one in the series and leaves me looking forward to the next one.
Why I read it: Working my way through the Witcher series after enjoying the Netflix TV adaptation.
Architecture in Photographs by Gordon Baldwin, 4/5
I enjoyed this little book, which contains a nice selection of photographs from the J. Paul Getty Museum along with a not-overwhelming amount of text about architectural photography’s venerable history. While a couple of the photographs left me shaking my head, completely unable to discern any artistic merit in them, the majority were inspiring and obviously captured with skill and care. In my experience, looking at good art is the easiest way to educate your eye as a photographer and this book provides plenty of inspiration. After reading it, I feel especially motivated to experiment with black and white photography, while not obsessing so much over cropping choices, lens distortion and making everything perfectly level.
Why I read it: I came across it while browsing in the library for light reading material to keep me entertained while cutting weight for an MMA fight two months ago.
The Best Life Stories: 150 Real-life tales of resilience, joy and hope–all 150 words or less! collected by Reader’s Digest, 5/5
I enjoyed the wide variety of writing styles, perspectives and meaningful experiences represented in this concise collection. The fact that these stories were collected from the general public via Facebook just goes to show that you don’t have to be a famous writer, poet or personality to express beautiful insights about the human experience.
Why I read it: found it while wandering through the library looking for something light and inspirational to read while cutting weight for my first MMA fight.
Recklessly funny, Inman doesn’t hold back at all in this collection of comics which tackles topics from commuting via polar bear to eating Play-Doh. This book is definitely not for the sensitive soul–while he considerately pixelates most of the cartoon privates, the author does somehow manage to invent euphemisms that are more offensive than the real thing.
[Why I read it: I’m on an Inman binge.]
This book contains only one comic, so it is more of a novelty than anything. However, it is still pretty cute and I recognise his cartoon dog’s infectious enthusiasm in my own mutt (though mine certainly uses fewer swearwords).
[Why I read it: ordered all of Inman’s stuff from the library at once, then read it in one sitting.]
This soporific book is a sort of spiritual antithesis to Brian Hayes’ Infrastructure: A Field Guide to the Industrial Landscape: while the latter opened my eyes to the surprising truth that good writing can make even the most seemingly boring topic an absolute delight, the former reveals that other styles of writing can make even the most interesting topic a dreary chore to read about. And the topic is interesting: who hasn’t felt like an idiot when struggling with an object that was created without regard to the principles of human-centered design (I’m thinking of you, shower faucets at a friend’s house)?
Following the author’s preface, which revels unbecomingly in the previous edition’s alleged popularity, influence and inspiring effect on readers, comes pages and pages of unmemorable text about the “seven stages” of this and “three levels” of that–a sort of flow-chart in prose (almost as tedious to read as you might imagine). Interesting examples of good and bad design feel few and Norman seems to spend more time criticizing designs than offering any creative solutions. For example, he repeatedly states that one human mistake should never be enough to cause a catastrophe in, say, a chemical processing plant, but he doesn’t give many realistic ideas for how a sufficiently complicated, resilient system, run by humans could actually live up to his criteria.
All in all, it is difficult to say what it is about Norman’s writing style that grates on me so strongly. He is the kind of author who briefly mentions a subject, then stops to tell you that more info can be found about it online (which is already reasonably obvious), then goes on to say that you could use Google to find the info (who doesn’t?), and then gives you the specific words you should use in Google to find the information, being sure to remind you to use quotation marks around your search phrase (we get it already! Google it!). In addition, I suspect that there is something about his general sentence formation that tends toward the mind-numbing. It’s not that he uses difficult words or concepts, it’s just that I seemed to lose interest about three-quarters through many of his sentences. I literally spaced out twice while reading the following gem and have still failed to process its main meaning: “Like prototyping, testing is done in the problem specification phase to ensure that the problem is well understood, then done again in the problem solution phase to ensure that the new design meets the needs and abilities of those who will use it” (229). There, I zoned out again, mid-sentence. It’s magical.
In the acknowledgments, Norman thanks his wife for telling him when he was “stupid, redundant, and overly wordy” (303). Ironically, two-thirds of those words are ones I would still use to describe the book (in case you’re curious which two words, please know that the author is definitely not stupid). Looks like Norman needs another wife or two.
[Why I read it: my friend, Joy, mentioned reading it in her book club and the topic sounded interesting so I ordered it from the library.]