Dimitris Paxinos

.net and other programming stories

Book Review - Don't make me think



An easy-to-read book with a wide target audience covering the core aspects of web usability, describing the complete process of usability testing and providing stimulation for further reading.

Why this book?

Steve Krug’s Don’t make me think (Revisited) is among the most popular books regarding web usability. It has been on my to-read list for quite some time. After reading Steve Job’s biography*, it was simply the only book I could think of as my next read.

General Feeling

I will start with its size (approximately 200 pages) which is a huge plus for me since I generally do not like long books. If we now proceed to the book’s content, it is absolutely obvious that the author generally knows what usability means since he wrote a really usable book!

It is easy to read without getting tiring at any point. It uses a lot of tables, diagrams and pictures in order to visualize a lot of information making the whole reading experience really pleasant.


The flow of the book is easy to follow. It is divided into four sections covering:

  1. The basic guiding usability principles according to the user’s usual behavior and expectations.
  2. The things that definitely have to be done right when creating a web site like navigation and right positioning of information within the page.
  3. Usability Testing by describing the complete process.
  4. Mobile usability, accessibility and ways of convincing upper management to invest in usability testing.

What I think…

As said earlier, this book is a nice read. It talks about and analyzes aspects of web design and usability that people often miss or neglect despite the fact that they are so obvious. I have already found some improvements that can be done in this blog as well.

It also talks you through the process of usability testing and how you can do it with minimal cost without having to outsource it. This might be extremely useful for companies with limited financial resources like startups.

The only part of the book that did not come up to my expectations was the mobile usability chapter which was really short and only scratched the surface of the topic.

To sum up, in my humble opinion, the book’s main goal is to give you an overview of web usability and the basic rules that have to be followed in order to have an acceptably usable web site. The author keeps stimulating the reader and recommending books for digging deeper into specific aspects of usability.

Who should read it?

The beauty of this book is that, thanks to the way it was written, has a really wide target audience like product managers, web designers and developers. Therefore, anyone professionally involved in UI development from any position and anyone with an affinity for user interface design and usability would definitely benefit from reading this book.

*Usability and perfect user experience were two of the core passions of Steve Jobs throughout his life and also two of the core characteristics of all the products he introduced.


Soft skills matter

Normal people go out, normal people meet new people.
I am (trying to be) normal too, so I go out and meet new people as well.

And after a while, these new people ask me:

Rebase And then they say… “I would never have guessed it. You don’t talk like one.” And they consider this a compliment! Well I never get flattered!

What do people think of developers?

I think that one picture might suffice:


That’s what people think. That we sit in our cave talking gibberish and scratching our heads while doing stuff with our laptop that no one understands. And when it comes to interacting with other people… well our reputation is not the best in this case…

What is the truth about us?

The truth is that they are right up to a point. Communication usually does not belong to our strengths. Programmers like coding not talking. We put on our favorite music and start coding. It’s a different world of creativity where you do not need to talk.

What happens when we do have to talk?

  • We sometimes find it hard to communicate with people in general.
  • And when we do, we sometimes have a problem expressing ourselves in plain English.
  • We don’t like meetings.
  • We speak very technical not able to translate what we want to say to the business or normal language.

Why do soft skills matter?

Professional developers write code for a living, they write code to fulfill requirements created by people in order to solve problems that other people have. Building software is a complex iterative process that requires a lot of human interaction and communication. Poor communication makes this whole process more difficult and makes you less productive.

By being a good communicator you:

  • Can back up your proposed solutions to technical problems with convincing arguments.
  • Can get your work noticed more.
  • Can be the guy that people turn too in case of a problem because you can understand what they need.
  • Can make the business people treat you as a business person since you can speak their “language”.
  • Can get you promoted since lead positions require such skills.
  • Make generally a difference since you can both code and talk!

And don’t forget…
There are many programmers
There are fewer good programmers
There are fewer good programmers that have some kind of soft skills.
There are only a bunch of good programmers that also have good soft skills.
Be one of them and make a difference!

Stop talking Assembly or Java!
Try plain English and be nice to other people!