Re: gEDA: PCB: Throw the Bugzilla out of window

[Daniel J Wisehart <dw-at-NOSPAMyankee_dot_us_dot_com>]

This might be true if you are solving a simple problem and knew in advance 
what all of the stumbling blocks will be.  But any hard design contains a few 
things that no one has ever done before in exactly the way you need to do 
them.  Good design is when you get something running quickly, learn what the 
unexpected problems are, improve the design and then try again.

It is very important to know what the requirements are--even though they will 
change once your solution is available--and to account for them in your 
design.  But if we waited for PCB to have every desirable feature and zero 
bugs before the first release, no one would be using it today.

Regards,
Daniel


On Saturday 20 November 2004 02:55, Bob Paddock wrote:
> Actually the number one cause of bugs, both hardware and software, is
> not understanding the requirements, long before the first line of code is
> ever written, or first part ever soldered.
>
> When more time is put in to requirements up front bugs go down, sometimes
> to zero.