Debugging the Development Process: Practical Strategies for Staying Focused, Hitting Ship Dates, and Building Solid Teams (Paperback)

~ (Author) "Have you ever stopped to consider what makes one project lead or programmer more effective than another?..." (more)
Key Phrases: Writing Solid Code, Microsoft Excel, Microsoft Press (more...)

Editorial Reviews

Product Description

Author of Writing Solid Code tells what worked and didn't work at Microsoft. This book is a practical guide to staying focused, hitting ship dates and building solid programming teams. You don't have to be a manager to appreciate this book; anyone involved in programming will appreciate the humor and practical advice it contains.

Product Details

• Paperback: 183 pages
• Publisher: Microsoft Press (August 1994)
• Language: English
• ISBN-10: 1556156502
• ISBN-13: 978-1556156502
• Product Dimensions: 9.2 x 7.4 x 0.7 inches
• Shipping Weight: 1.2 pounds
• Average Customer Review: 4.2 out of 5 stars  See all reviews (29 customer reviews)
• Amazon.com Sales Rank: #418,461 in Books (See Bestsellers in Books)

  Popular in these categories: (What's this?)

  #27 in	Books > Computers & Internet > Programming > Languages & Tools > Debugging
  #100 in	Books > Computers & Internet > Computer Science > Software Engineering > Design Tools & Techniques

Customer Reviews

Most Helpful Customer Reviews

40 of 41 people found the following review helpful:

3.0 out of 5 stars Smooth reading but simplistic, November 6, 1999

By	Tom O Bjorkholm (Stockholm, Sweden) - See all my reviews

The language is easy to read and the style contributes to fast and smooth reading. The book can also be read very fast because there is not enough new facts in the book to slow you down.

The book mainly explains the obvious (although too often ignored) practices that helps your development project: stay focused, avoid distractions, avoid interruptions, avoid wasting time, avoid unnecessary meetings (meetings are interruptions and far too often a waste of time), fix bugs early. The book has some stories to explain the above practices. But, the book has no hard facts to help you fight for the above practices in case you have a "pointy haired" boss.

In my opinion "Rapid Development" by Steve McConnel is a far better book. "Rapid development" has all the hard facts that "Debugging the development process" lacks. "Rapid development" also describes more practices and has a broader view of the development project that "Debugging the development process".

14 of 18 people found the following review helpful:

3.0 out of 5 stars Definitely worth reading, but not awesome., June 3, 2000

By	From_Plano_TX "a_customer_from_plano" (Plano, TX USA) - See all my reviews

This book is NOT about project management, it is about 1st line supervision. Of course, 1st line supervisors interface with management and this book addresses that some, but that doesn't address project management from a manager's view, just a supervisor's. You need to know who this book is for. It is for an experienced supervisor, someone who can spot the occasional errors. In this case the errors are strongly held but misplaced opinions. One error the author made was to call programmers lazy who read source code as part of a job (p. 50). That's a foolish statement. If you've ever debugged someone else's undocumented code, you have to read the source to even figure out what the code is supposed to do. He praises people who make snap decisions (p. 20). That's silly. It's better than no decision, but certainly not praiseworthy. And on pp. 113-115 he says to "Give Experts the Boot." Here he's parroting the "we need generalists" mantra that became popular about 5 or 6 or 7 years ago. I've seen a very noticible drop in quality all over the industry. One example, when one company I worked at got rid of their Ph.D. from MIT who did thermal analysis and replaced him with a non-degreed mechanical designer who was trying to run thermal analysis software, not even having a clue on the intricacies of thermal analysis and design. At this point the thermal design of their computers became a joke. Maybe it would work and maybe it wouldn't. Don't get me wrong. The author has a number of good points. E.g., fix bugs ASAP (p. 128), don't let them pile up for later. Set your coding priorities (pp. 17-19), and do proper postmortems (pp. 78-80). Very good book, but you must beware of his errors. If you are young, read this again after 10 to 15 years.

4 of 4 people found the following review helpful:

5.0 out of 5 stars Absolutely Wonderful, May 13, 1999

By A Customer

Steve talks about all of the problems I've found common in the software development industry that stress out the development team. His discussions of problems he has faced in his own development efforts provide valuable tips on handling the pressures from management, staff and deadlines. I highly recommend this book for anyone who assumes a leadership role, not just in the software industry, but in all industries where pressure and deadlines exist.