Why read Peopleware?I’m not a manager and I have no intension of becoming a manager any time soon, so why read this book? Firstly, it’s incredibly interesting. Secondly, it’s relevant to all software developers, not just managers. For example there is advice on overtime, office environment, innovation, hiring staff, meetings, leadership, making change possible and email. And this is just scratching the surface.
What did I learn?There’s a huge amount to learn by reading this book but a few parts stood out to me.
- The flight from excellence. The authors talk about the friction between the client’s desire for quality and the builder’s desire for quality. The client often isn’t concerned about code quality, they just want a finished product for their consumers. Builders (developers) on the other hand get a deep sense of pride from achieving high quality code. We’ve all been there
- Making change possible. The insight in this chapter about why people resist change really hits the nail on the head. It’s argued that the resistance comes from emotion, not logic and I can’t help but agree. There’s also some good suggestions on how to make change easier
- Productivity. This is a theme covered by a number of chapters. Flow is highlighted as being essential for productivity, as is quiet and the avoidance of distractions like email, telephone and multi-tasking
Some quotesI know quotes like this don’t really mean much out of context, but I still like them, so here’s are some of my favourites.
“The trade-off between price and quality does not exist in Japan. Rather, the idea that high quality brings on cost reduction is widely accepted”
“The fundamental response to change is not logical, but emotional”
“Change won’t even get started if people feel safe”
“The managers function is not to make people work, but to make it possible for people to work”
“People under time pressure don’t work better, they just work faster”
“Innovation is all about leadership, and leadership is all about innovation”