
SOFTWARE QUALITY BOOK EXCERPTS
Dreaming in Code -- Chapter 1, Doomed
Scott Rosenberg 02.12.2007
Rating: --- (out of 5)




As a registered member of SearchSoftwareQuality.com, you're entitled to a complimentary copy of Chapter 1 of Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software written by Scott Rosenberg and published by Crown Publishing Group.
Dreaming in Code tells the hidden story of the making of software -- specifically Mitch Kapor's Chandler. In "Chapter 1, Doomed," provides a peek into the bug repairs for the Chandler project and how the team handles getting all its work done in the little amount of time left.
[IMAGE]
Book description:
Our civilization runs on software. Far more than most people understand, it has seeped into every cranny of our lives. It is in our kitchen gadgets and cars, toys and buildings. Our national defense, our businesses and banks, our elections and our news media, our movies and our transportation networks--the stuff of our daily existence hangs from fragile threads of computer code.
And we pay for that fragility. The FBI, the FAA, the IRS -- each has crash
To continue reading for free, register below or login
To read more you must become a member of SearchSoftwareQuality.com
');
// -->
 |
 |
|  |
RELATED CONTENT
 |
Software Quality Book Excerpts |
 |
Perfect Software, Ch. 8: What Makes a Good Test
|
 |
Seven Steps to Mastering Business Analysis, Ch. 1
|
 |
Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?
|
 |
The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management
|
 |
Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software
|
 |
Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management
|
 |
Implementing ITIL Configuration Management: Chapter 3, Determining Scope, Span and Granularity
|
 |
Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams
|
 |
Inherent Quality Simplicity, Section V: The Evolution
|
 |
Managing the Test People, Chapter 6: Keeping Your Beast Effective
|
 |
Project Management |
 |
The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management
|
 |
Implementing ITIL Configuration Management: Chapter 3, Determining Scope, Span and Granularity
|
 |
Geekonomics: The Real Cost of Insecure Software -- Chapter 1, The Foundation of Civilization
|
 |
Treasure Chest of Six Sigma Growth Methods, Tools, and Best Practices -- Section 1, Define-Measure-Analyze-Improve-Control (DMAIC)
|
 |
Surprise! Now You're a Software Project Manager -- Chapter 1
|
 |
Jumpstart CMM/CMMI Software Process Improvements: Using IEEE Software Engineering Standards -- Chapter 1
|
 |
Essentials of Lean Six Sigma -- Chapters 1 and 4, Introduction and Improvement
|
 |
CMMI: Guidelines for Process Integration and Product Improvement, Second Edition -- Chapter 1, About CMMI for Development
|
 |
Six Forms of Software Cost Estimation -- Chapter 3, Estimating Software Costs, Second Edition
|
|

ed on the rocks as it has tried to build new software systems. The private sector doesn't do much better. Software errors cost the U.S. economy about $59.5 billion annually, according to one study. Never in history have we depended so completely on a product that so few know how to make well. We can't guarantee that we will produce it on time or on budget. We can't guarantee that it will work reliably. We can't even guarantee that it will do what we want it to do. Yet we can't give it up, either: The software that frustrates and hogties us also enthralls us with promises of more, faster, better ways to work and live.
Why can't we build computer programs the way we build bridges? Is this work art or science? Why is the meeting of human mind and machine logic so treacherous? Dreaming in Code seeks to answer those questions. Combining fly-on-the-wall reporting, research, and in-depth explanatory journalism, Dreaming in Code tells the hidden story of the making of software -- specifically Mitch Kapor's Chandler -- its frustrations and intoxications.
>> Read Chapter 1: Doomed.
>> Get more information and buy the book
 |

|
|
 |
|
 |