Channels ▼

Jolt Awards: The Best Books

, October 01, 2013 Five notable books every serious programmer should read.
  • E-mail
  • Print

Finalist: Team Geek

By Brian Fitzpatrick and Ben Collins-Sussman

One of the hardest aspects of a manager's job is building a team, keeping it on track, and helping it stay free of productivity-sapping dynamics. Likewise, for developers, the great challenge is how to work in a team and handle the inherent stresses and strains without becoming an impediment or drain on the collective effort. This book is very much oriented to explaining these dynamics and how teams can ideally be assembled, managed, and led towards productive results. In this sense, it is a modern-day version of the classic title Peopleware, but updated for today's teams.

This update is necessary because the culture of software development has changed so much. The authors, both presently at Google but earlier contributors to high-profile open-source projects, cast the necessary wisdom so that it's tailored to present needs. The latter include handling teams that comprise not only developers but designers, the current emphasis on agile and lean methods, and the expectation that team leaders will provide direction on the basis of more than just a hierarchical authority.

As such, the advice is supremely pragmatic and eschews philosophical views of management. For example, here are the suggestions on managing problems without drama:

• Reject behaviors, not people.
• Guard your team's attention and focus.
• Ignore trolls and stick to facts.
• Don't sacrifice long-term culture for short-term convenience.

All good advice that is elaborated with care and presented so as to be implemented immediately. The discussions of meetings and team communications are especially well thought out and clearly articulated. It's evident the authors have spent a lot of time thinking about the problems and testing solutions before formulating the counsel they present here.

This book is short and highly readable. Team Geek should be mandatory reading for most developers today.






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.