Home > Articles > Programming

Quality By Design, Part 1: Avoiding Rotten Code

  • Print
  • + Share This
We all have to face the fact that some software stinks; it doesn't work right or it just plain feels wrong. Fixing these problems is simple, but may not be easy. We have to understand the nature of software development and make sure that we allow ourselves enough time to do a good job.
Pete McBreen is the author of Software Craftsmanship: The New Imperative (Addison-Wesley, 2001, ISBN 0-201-73386-2). Software Craftsmanship is a Productivity Award winner in Software Development magazine's 12th Annual Jolt Product Excellence Awards.
From the author of

Introduction

Despite all of the innumerable books and articles written about risk and software development practices, I think that there are only two real problems in software development: haste and ignorance. Somehow we always manage to convince ourselves that we can develop the software in a very short time, even when we don't have a clue about what the users really want.

To be politically correct, I probably should say partial knowledge rather than ignorance, but I've grown tired of people calling a spade "a manual earthmoving implement." Although sometimes I can manage to remain amused when people crash and burn their projects, lately I've become less tolerant, as I've had to put up with more and more really rotten software. It's all so unnecessary!

  • + Share This
  • 🔖 Save To Your Account