I’ve been trying to track down a copy of this for ages. It’s impossible to buy.
Updated link to point to youtube rather than a dead-link MP3.
In Why we Love Helen Fisher looks at love from an evolutionary perspective. It’s all about reproduction. Helen breaks this down further into three distinct types of love that are driven by different hormones.
Testosterone causes lust. We need to want to have sex in order to reproduce.
Romantic love is associated with dopamine and, interesting, low serotonin levels. Dopamine makes you happy. Whilst low serotonin can be associated with depression, it is also associated with obsessive compulsive disorder and this may explain why people in love focus on their loved one and nothing else. This feeling can last months or years.
Attachment on the other hand comes from the hormones vasopressin and oxytocin. These are responsible for the contentment we feel from long-term relationships and also the rush of love mothers feel for their newborn children.
These chemicals and feelings interact in interesting ways. Lust can lead to love and vice-versa.
Why we Love gives a biological basis for the complexities of love and love relationships. Fisher’s model explains how someone could be in a committed relationship, whilst in love with someone else and at the same time have sexual fantasies about a third person.
Helen Fisher also gave a great talk on the topic at TED.
I finished David Platt’s Why Software Sucks…and What You Can Do About It. Software does indeed suck, but this book doesn’t do a great deal to help solve the problem.
The main thesis of the book is that software developers are not their users and look at interface design from a completely different perspective. “You are not your user!” Platt implores repeatedly.
Unfortunately for Platt he, as authour, is not the reader of his book. The book fails because Platt seems to be confused about whom he is writing for.
On the one hand, for software developers, Platt provides little guidance for better design. “Think about what your users want” and “choose sensible defaults” seems to sum it up.
Platt could defend himself by saying that this book is targeted at end users. He fails as well though. He repeatedly says that users aren’t interested in the software, they just want to get their task done. By his analogy: people aren’t interested in drills, they want to put holes in things. Why would he think that a book on “Why drills suck” would be of interest?
Ultimately, I think that Platt’s book is a trojan horse designed to lure software users into reading it. In between the early chapters on “why software sucks” and the final chapter of “what you can do about it” he dumps a lot of computer nerd information on to his users. Things “ever user should know” about security, privacy, geek culture and Microsoft. For the computer professional this information is too basic. For the computer user it’s too boring. “Know your user/book reader” indeed.
Oh, and the final chapter that tells the end user what they can do about bad software? Well you can complain! Despite giving examples of how hard it is to find feedback forms on the web, this is what Platt encourages users to do. Then, despite a chapter explaining why Microsoft rules the software world, he advises people to look at (admittedly inferior) alternatives. Why would users care?