SoftwareQuotes.com

Daily quote: : Anonymous

When you spend time to find & fix all the bugs in your project, you can't complete the project in your life time. -Anonymous , Ignore some bugs

To see quotes by Anonymous visit: Anonymous

Daily quote: : Jim McCarthy

Don't pre-announce. Although you'll be tempted to brag about software you haven't shipped in order to salve your pride and give your customers a ray of hope, don't do it. Pre-announcing is a treacherous game to play. Inevitably, it takes the bang out of your launch and the sizzle out of your product. -Jim McCarthy, "Dynamics of Software Development" by Jim McCarthy, Denis Gilbert, ISBN: 1556158238
This book is available from Amazon.com

To see quotes by Jim McCarthy visit: Jim McCarthy

Daily quote: : P. J. Plauger

Let the data structure the program. -P. J. Plauger, Kernighan and Plauger - Chapter 4 , "The Elements of Programming Style" by Brian W. Kernighan, P. J. Plauger , ISBN: 0070342075
This book is available from Amazon.com

To see quotes by P. J. Plauger visit: P. J. Plauger

Daily quote: : Jim McCarthy

Trying to build configurability into either the software tool or an application to compensate for individual variation can complicate the software beyond the acceptable range for large numbers of people... There is a natural tension between ease of use on the one hand and ease of changing use on the other. Usually you can reach a broader market by tacking the ease of use problem. Ease of use is a hard problem, but it's substantially simpler than the problem of dynamic adaption. -Jim McCarthy, "Dynamics of Software Development" by Jim McCarthy, Denis Gilbert, ISBN: 1556158238
This book is available from Amazon.com

To see quotes by Jim McCarthy visit: Jim McCarthy

Daily quote: : Donald E. Knuth

You're bound to be unhappy if you optimize everything. -Donald E. Knuth

To see quotes by Donald E. Knuth visit: Donald E. Knuth

Daily quote: : Bill Gates

Most companies have an inefficient chain of people and paper between customers and the people who can make major improvements. When the customer data finally reaches the product design group, it often isn't easy for the team to digest its significance and prioritieze it accordingly. All of the delays taken together mean that improvements don't happen as fast as they should.

I recomend the following approach to integrating customer complains and whish list into product and service development.

1. Focus on your most unhappy customers.

2. Use the technology to gather rich information on their unhappy experiences with your product and to find out what they want you to put into the product.

3. Use technology to drive the news to the right people in hurry.
If you use these three things, you'll turn those draining, bad news experiences into an exhilarating process of improving your product or service. Unhappy customers are always concern. They're also your greatest opportunity. Adopting a learning posture rather than a negative defensive posture can make customer complaints your best source of significant quality improvements... -Bill Gates, "Business @ the Speed of Thought : Using a Digital Nervous System" by Bill Gates, Collins Hemingway (Contributor) , ISBN: 0446525685
This book is available from Amazon.com

To see quotes by Bill Gates visit: Bill Gates

Daily quote: : Boris Beizer

Programmers are responsible for software quality - quality in their own work, quality in the products that incorporate their work, and quality at the interfaces between components. Quality has never been and will never be tested in. The responsibility is both moral and professional. -Boris Beizer, Chapter 13: Implementation, Section 3.1. , "Software testing techniques" by Boris Beizer , ISBN: 0442206720
This book is available from Amazon.com

To see quotes by Boris Beizer visit: Boris Beizer

Daily quote: : Anonymous

Projects without clear goals will not achieve their goals clearly. -Anonymous , - Gilb's Principle of Fuzzy Targets. As quoted in Software Metrics: A Rigorous and Practical Approach, page 10.

To see quotes by Anonymous visit: Anonymous

Daily quote: : T. DeMarco and T. Lister

Since the days when computers first came into common use, there must have been tens of thousands of accounts receivable programs written. There are probably a dozen or more accounts receivable projects underway as you read these words. And somewhere today, one of them is failing. Imagine that! A project requiring no real technical innovation is going down the tubes. Accounts receivable is a wheel that's been reinvented so often that many veteran developers could stumble through such projects with their eyes closed. Yet these efforts sometimes still manage to fail. -T. DeMarco and T. Lister , "Peopleware : Productive Projects and Teams, 2nd Ed. " by Tom Demarco, Timothy R. Lister, ISBN: 0932633439
This book is available from Amazon.com

To see quotes by T. DeMarco and T. Lister visit: T. DeMarco and T. Lister

Daily quote: : C. A. R. Hoare

Inside every well-written large program is a well-written small program. -C. A. R. Hoare

To see quotes by C. A. R. Hoare visit: C. A. R. Hoare

Daily quote: : Boris Beizer

Flowcharts have been falling out of favor for over a decade, and before another decade passes they'll be regarded as curious, archaic relics of a bygone programming era. -Boris Beizer, Flowcharts are essentially equivalent to UML's activity diagrams , "Software testing techniques" by Boris Beizer , ISBN: 0442206720
This book is available from Amazon.com

To see quotes by Boris Beizer visit: Boris Beizer

Daily quote: : Boris Beizer

Extra features were once considered desirable. We now recognize that 'free' features are rarely free. Any increase in generality that does not contribute to reliability, modularity, maintainability, and robustness should be suspected. -Boris Beizer, Chapter 2, Section 3.2.2. , "Software testing techniques" by Boris Beizer , ISBN: 0442206720
This book is available from Amazon.com

To see quotes by Boris Beizer visit: Boris Beizer