Channels ▼


Making Software: What Really Works, and Why We Believe It

Many claims are made about how certain tools, technologies, and practices improve software development. Software application development methodologies continue to jostle for recognition (and ultimately adoption) among the programmer cognoscenti around the globe. When waterfall is out, Agile is in. When "lean scrum" clustering for application development is out, Rational Unified Process and more “systems level” architecting is in.

But which claims are verifiable and which are merely wishful thinking — and what really works?

In truth, we now have so much “information about information,” so much “data management” to help deal with our data that we sometimes appear to be at a tipping point when even meta-tagging and data optimization tools seem to lead us into brick walls.

In Making Software: What Really Works, and Why We Believe It (O'Reilly Media), contributors including Steve McConnell, Barry Boehm, Jorge Aranda, Andreas Zeller, and Barbara Kitchenham offer essays that uncover what they call the “truth" and "unmask myths” commonly held within the software development community.

The book is edited by Andy Oram and longtime Dr. Dobb's contributor Gregory V. Wilson.

According to the publishers, the insights collected in this book may surprise you:

  • Are some programmers really ten times more productive than others?
  • Does writing tests first help you develop better code faster?
  • Can code metrics predict the number of bugs in a piece of software?
  • Do design patterns actually make better software?
  • What effect does personality have on pair programming?
  • What matters more: How far apart people are geographically, or how far apart they are in the org chart?

"We call ourselves 'engineers', but programming processes are mostly dictated by comfort and momentum instead of being driven by data. With this wealth of empirical data about writing code, finally our processes can be as scientific as our personalities," said Jason Cohen, founder of Smart Bear & WPEngine and guest author in this book.

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.