Tag: book review
-
Book Review: The Psychology of Software Teams by Cat Hicks
I read the first half of this book all in one sitting, and then the second half the same way. Which is a lot of psychology all at once, but it flowed so naturally and logically together that I never really felt like there was a hard stop between thoughts. And there were thoughts, so…
-
Book Review: Hivestruck, by Vincent Toro
A review of Vincent Toro’s book Hivestuck. “An app that rots or riots / on command. An app that / functions without a thumb / to guide it. An app to eliminate undesireable / scents. An app that shakes / the sand from your bathing suit / while checking your father’s / cholesterol. An app…
-
Book review: Kill It With Fire, by Marianne Belotti
I read this book slowly, not because it is long, or difficult, but because it is incredibly thought-provoking. Belotti has spent time doing the grinding work of upgrading the brownest of fields, and has managed to retain a sense of curiosity and fresh thinking that comes through in every example. The book’s layout is clear,…
-
Book Review: Strategic Writing for UX by Torrey Podmajersky
Disclosure: I got a review copy of this book. Further disclosure: Torrey is part of the pink-haired tech people. We are legion. This book is a snappy and sharply-focused exploration of the words that make the magic happen in user interfaces. Podmajersky accurately identifies places that more needs to be said, and then avoids them,…
-
Book Review: Academic Slide Design by Ann E. Fandrey
This book says “Academic”, but it’s also an excellent resource for the person writing technical/software presentations. We often face the problem of trying to convey really important concepts in a way that serves people who are primarily listening to us as well as people who are reading the slides, either because they don’t speak the…
-
Response to: Modern Technical Writing, by Andrew Etter
I’ll be honest. I’m a little mad I didn’t write this book. It’s clear, lucid, and pithy. I agree with much of the philosophy of minimal tooling and semantic separation of form and content. Etter says, Great documentation makes new hires productive in days instead of weeks, prevents thousands of calls to customer support, is…
