Harry Bosch, Book 15

With the speed that I have been reading these Bosch books, you'd think that I really enjoy them. You'd be somewhat right, I do enjoy them, but not necessarily really enjoy them. They are entertaining, to be sure.

So, in this book, as in thirteen of the last fourteen books, someone dies and there are tunnels. I know, I know, you're expecting me to say, "AND A BAD COP DID IT." Well, sorta. Read the book to understand what I mean. The series definitely took a right turn in the middle of it to a point of complete "Wait, WTF. Did that just happen?" The emotional stuntness (is that a word? it's a word now) of Bosch (okay, of Connelly's portrayal of Bosch) is stunning. The man cannot describe emotions to save his life. There is a dark abyss of raw pain that people descend into at certain points of their lives. That Connelly was unable to describe it well leads me to believe that Bosch's "mission" is a cover for his sociopathy. Here, let's look at Wikipedia's definition:

Psychopathy (/saɪˈkɒpəθi/), also known as—though sometimes distinguished from—sociopathy (/ˈsoʊsiəˌpæθi/), is traditionally defined as a personality disorder characterized by enduring antisocial behavior, diminished empathy and remorse, and disinhibited or bold behavior.

Antisocial? Check!
Diminished remorse? In this book, check!
Bold behavior? Check!

I understand the plot minimized the time available for any kind of mourning in the book, but come on, Bosch does not do emotions (or Connelly can't write them, I don't know which, as I don't know if being emotionally stunted is a deliberate creative choice).

Look at me, finally analyzing the characters!

This is my review of the book for work:

Finished reading How to Transform Your Ideas into Software Products - it was a Shopify Montreal library book, and, I think, a great choice. I read it in about 3 days on the bus rides into work, so it's a quick read. It's a guidebook on how to build software from validating an idea before writing software, through user personas and stories, designing workflows with paper, prototyping guidelines, basic marketing strategies and metrics. The typography and copy-editing needs work; the book has no ISBN [edit: the copy I have doesn't, but the book does: 978-1-4951-4124-9], and is available at http://femgineer.com/transform-ideas/ and Amazon.

Okay, that's the blurb of it. The opinion of it: if you already know all of this information, if you already write code and know about full product life-cycles, then, sure, all you're going to get out of this book is how much it needed a copy-editor before publishing.

However, it is the PERFECT book to hand to someone who doesn't write software or is new to software development, and wants to take an idea through to project launch and growth. It's a great roadmap: it's not deep in any area, but points the reader in the right direction.

My new plan for people who approach me at conferences with ideas they want to build is now recommend this book and suggest they do the exercises through chapter 7, then come back and we'll talk.

I recommend this book for software people as a blueprint, it's an easy read and eye-opening to all the things you already know but everyone else doesn't. For non-software people, this is the perfect blueprint for building a software product.

Ignore the typos and the "you've gottas."