Skip to main content

Zen of Listening (Book Review)

Listening is an often undervalued skill. Often you can do a better job of communicating what you want other to know by listening better to your audience. The Zen of Listening: Mindful Communication in the Age of Distraction is a very practical guide to understanding impediments to listening better, and improving your listening skills.

This is not a typical communications book full of techniques to help you convince others that you are listening. This book focuses on techniques to help you build a mindset to listen better. You'll learn how you think about interactions, and how that thinking affects how you respond.

This was a deceptively simple read. The book was easy to get through, but after you read each chapter you are left with a lot to think about. The book will leave you with insights that will help you to understand and improve your interactions with others. As you read, you'll understand both about how you listen, and why some interactions might bother you. With this information you can start figuring out how much you can change your approach to an interaction to get the most out of it.

In addition to stories, examples, and advice, each chapter ends with a few simple exercises to help you practice what the chapter discusses. In spite of the title, the explicit references to Zen philosophy and techniques are few. The importance of meditation as a way to help you learn to reduce distractions is a recurring theme. This is a very practical book with advice that you can start using immediately.

My one minor complaint about the book is that a brief discussion in the last chapter about the negative effects of online interactions seemed to be a missed opportunity. While it is good to keep challenges of various media in mind, it would have been a pleasant surprise to see a discussion of how the lessons in the book could be applied to make all interactions more effective. This  does not take away the value of the book, and perhaps applying the techniques to other forms of communication can be an exercise for the reader. This is worth a read if you are interested in learning more about how you can listen and communicate better.


Popular posts from this blog

Continuous Integration of Python Code with Unit Tests and Maven

My main development language is Java, but I also some work in Python for deployment and related tools. Being a big fan of unit testing I write unit tests in Python using PyUnit. Being a big fan of Maven and Continuous Integration, I really want the  Python unit tests to run as part of the build. I wanted to have a solution that met the following criteria:
Used commonly available pluginsKeep the maven structure of test and src files in the appropriate directories.Have the tests run in the test phase and fail the build when the tests fail.
The simplest approach I came up with to do this was to use the Exec Maven Plugin by adding the following configuration to your (python) project's POM.

<plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <executions> <execution> <configuration> <executable>python</executable> <workingDirectory>src/test/python</workingDirect…

Displaying Build Numbers in Grails Apps

Being a fan of Continuous Delivery, identifiable builds, and Continuous Integration: I like to deploy web apps with a visible build number, or some other way of identifying the version. For example, having the build number on the login screen for example. In the Maven/Java world, this is straightforward. Or at least I know the idioms. I struggled with this a bit while working on a Grails app,  and wanted to share my solution. There may be other, better, solutions, but the ones I found approaches that didn't quite work they way that I'd hoped.

My requirements were:
To display a build number from my CI tool, where the number was passed in on the command line. In Bamboo, for example you might configure a grails build as
-Dbuild.number=${bamboo.buildNumber} warTo only change build artifacts and not any source files.To not misuse the app version, or change the names of any artifacts.To be simple and idiomatic.I realized that that Grails itself changes the application metadata (appl…

Motivation Visibility, and Unit Testing

I've always been interested in organizational patterns (such as those in Organizational Patterns of Agile Software Development). I've recently found myself thinking a lot about motivation. I'm now reading Drive: The Surprising Truth About What Motivates Us and just finished Rob Austin's book on performance measurement. Being the parent of a three year old, I'm finding more and more that "because I said so, and I'm right" isn't too effective at home. My interests in motivation are closely related to my interest in writing software effectively. Writing software is partially a technical problem about frameworks, coding, and the like, but the harder (and perhaps more interesting) problem is how to get a group of people working together towards a common goal. Agile practices, both technical and organizational, build a framework which makes having the right amount of collaboration and feedback possible. But there's a bootstrapping process: How do yo…