Channels ▼
RSS

Jolt Awards

The 14th Annual Software Development Jolt and Productivity Awards


BOOKS: GENERAL INTEREST

Waltzing with Bears
Tom DeMarco and Timothy Lister
(Dorset House, 2003)


“We hope that winning will help us get the buzz going about risk management at all those sleepy software organizations out there.”

—Tom DeMarco and Timothy Lister

If you’re the only person in the known universe working on a software project that has absolutely no risk, you don’t need this book. For the rest of us, Waltzing with Bears explains how to deal with risk and the mindset of risk management, detailing problems that are all too realistic and familiar. Waltzing with Bears will raise your awareness of possible project obstacles and pitfalls, and the need to plan for them up-front. Although developers often view technical obstacles as unexpected interruptions, they’re inherent in the nature of our work and should be anticipated as opportunities to evolve.

Waltzing with Bears will help even novices quantify uncertainty in their projects. Waltzing with Bears should be on the shelves of not only your project and program managers, but every member of your team.

—Sue Spielman

The Art of Unix Programming
Eric S. Raymond (Addison-Wesley, 2003)

GNU, famously, is Not Unix, and Linux isn’t, either (certain stock-inflating courtroom rants notwithstanding). Darwin evolved from FreeBSD. What these legendarily solid, adaptable and long-lived operating systems do share is a design philosophy dating back to 1969. Eric S. Raymond elucidates the implications of those simple yet profound design decisions for today’s programmers in a readable book that tells you a lot about how to program in Unix-like environments—but also explains the why. Yes, Raymond takes a few dutiful swipes at other operating systems, but it’s clear his heart isn’t in casting slings and arrows. Instead, he’s bursting to tell you why Unix programming is so great, exploring the ramifications of cheap process-spawning, the “everything’s-a-file” landscape and the rest of the Unix world. Along the way, Raymond gives plenty of good advice on programming itself—derived from the Unix philosophy, but applicable anywhere.

—Rick Wayne

Lean Software Development: An Agile Toolkit
Mary Poppendieck and Tom Poppendieck (Addison-Wesley, 2003)

Lean Software Development cuts to the chase: If it’s not about analysis and coding, and if it doesn’t matter to the client, it’s fat. Procedural fat clogs the arteries of otherwise productive development teams, leaving them panting beneath the excessive weight of obligatory documentation and approvals. Instead of spending their time jumping technical hurdles, developers slog through requirements collection while packing on the pounds. Excess weight translates into projects over budget and schedule while beet-faced staffers feel the burn.

Mary and Tom Poppendieck are master chefs offering a seven-ingredient slimming solution: Eliminate waste, amplify learning, decide as late as possible, deliver as quickly as possible, empower the team, build integrity in and see the whole. Lean Software Development may be the diet developers have been craving: It’s good for you and tastes great, too.

—Donna Davis

The Pragmatic Starter Kit
Dave Thomas and Andy Hunt
(The Pragmatic Programmers, 2003)

After giving us The Pragmatic Programmer: From Journeyman to Master (Addison-Wesley, 1999), those galloping gurus of pragmatism, David Thomas and Andrew Hunt, have pragmatically decided to not only write, but publish a three-volume series of best practices guides, The Pragmatic Starter Kit. The first two volumes are Pragmatic Version Control Using CVS and Pragmatic Unit Testing in Java with JUnit (the third volume will deal with automation). As one Jolt judge said, these lean and focused books get straight to the point, and hopefully represent a coming trend to save the forests required to print 400-plus-page tomes that throw in everything including the history of mankind. What Thomas and Hunt do throw in is an explanation of version control and unit testing, and how to utilize the headlined tools to achieve these best practices.

—Warren Keuffel



Related Reading


More Insights






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.
 

Video