Skip to main content

Developer Skills: Listening

Most people have an agenda when they listen.  They aren't really listening, they're waiting for you to finish talking so they can tell you why you're wrong, or demonstrate their own brilliance.

It is hard to listen without an agenda.  Your mind jumps to how you will respond, or wanders off to what you're going to have for lunch.  Becoming good at this takes a lot of time and practice.

It's worth it because:
  • You learn more - a LOT more.
  • You will often change your point of view for the better.
  • People trust you more - and their trust is justified because you are open to changing your point of view.
  • You will make more connections with other experiences.
So how does one listen without an agenda?  The best advice I can give is to "Fake it until you make it."  Act like you don't have an agenda.  Your need to "own" the conversation will slowly fade away as you repeatedly experience the value of listening with an open mind.

If this doesn't work for you, you might want to try being less of a douchebag.  I recommend therapy and meditation.  I'm not longer a complete jerk thanks to both of those.

You can also apply "active listening" techniques.  One is to repeat what they told you in your own words.  This can very easily be overdone, so be careful that  you aren't substituting technique for genuine openness and curiosity.

The best way to demonstrate that you're interested and listening?  Draw it!   This not only clarifies concepts in your mind, it helps your conversation partner understand their own ideas better.  The best part:  It's easy to capture what you've drawn for later reference.  It's easy to forget the details of a conversation, but if you capture the salient points in a picture or a set of bullets, you can recapture most of what you were thinking.


Post a Comment

Popular posts from this blog

Agile Performance Management: Why Performance Reviews Suck

Many thanks to Mary Poppendieck, who wrote about this topic in 2004, and proposed a comprehensive solution.  She is the inspiration for much of my thinking on this subject.  She is also a better writer than I am a cartoonist.


Performance reviews suck.  I don't know of anyone who goes into their appraisal without some trepidation.  Your boss is guaranteed spring some surprise criticism on you that is ill-informed or misses the point as you see it.  It's a real challenge not to get defensive about that.

The only thing that makes your own performance review suck less is having to give them.  As a manager, I have dished out quite a few, and some of them went pretty badly.  (To the people at my first management job: Thanks for helping me learn how to get better at them.  Your sacrifice was not in vain.)  Since then, receiving one isn't nearly as gut-wrenching, if only because I try to make it easier for the guy on the other side of the desk.  I've been there, and I know how …

Do. Not. Optimize.

You've probably heard this quote before:
Premature optimization is the root of all evil.
 - Tony Hoare
Speculative optimization is always wasted time.  In the absence of an actual performance problem, you're just burning time that could be better spent on refactoring your code to make it clearer.  This is exacerbated because performance-optimized code is usually harder to read than code which hasn't received such treatment.

Here is what you're doing when you optimize:
Adding code that now must be maintained.Obfuscating the existing code.Spending time writing code that doesn't add value. But what's that you say?  You have the experience and know-how to decide when optimization is needed?  Maybe, but probably not.   The people at Sun and Oracle may or may not be smarter than  you or me, but they certainly know more about optimizing Java bytecode than we do.

For example, some people think that having a large number of classes is slower than the alternative.  This …

Showing Off: How to Do a User Demo

Rather than repeating what has been said elsewhere, here is a nice short post on agile-for-all that covers the basics.

Here are a few things for my own future reference and teams that I'm working with...

Try to keep each demo to 5 minutes or less.   If it's longer than that, it's possible that you should be demoing more than one story.  More likely, you're just being too wordy.

TALK LOUDLY.   No, louder than that.  Louder.  Do you feel like you're yelling?  OK, that's about right.  You need to put your voice in public-address mode for 5 minutes.

Focus on why your audience should care about the story  This is particularly important for back-end work.  For example: Your story generates a feed of XML that will be consumed by another application. Show the output, and point to a couple of salient features in it.  Then be done.

The important part of the above is "show the output."  Showing the end users how to interact with your service is a separate sit-d…