FPGA Central

On 22 Jul 2005 06:01:19 -0700, "steve" <[email protected]>
wrote:


>a prototype can quickly confirm the robustness of a design

Does this imply that the best way to find bugs is to test a prototype?

That's the Bill Gates methodology.


John

On Sun, 24 Jul 2005 22:31:38 -0700, John Larkin
<[email protected]> wrote:

>On 22 Jul 2005 06:01:19 -0700, "steve" <[email protected]>
>wrote:
>
>
>>a prototype can quickly confirm the robustness of a design
>
>Does this imply that the best way to find bugs is to test a prototype?
>
>That's the Bill Gates methodology.

The Bill Gates methodology is to get someone else to pay you for the
privilege of testing your prototype.

Bob Perlman
Cambrian Design Works

I see the Design as a "paper prototype". It's to test the design and see
if the design is coherent. Looking for bugs comes at the code level.

--
---------------------------------------------------------------------
DataGet & PocketLog www.dataget.com
Data Collectors www.baxcode.com
--------------------------------------------------------------------


"John Larkin" <[email protected]> wrote in message
news:[email protected]..
> On 22 Jul 2005 06:01:19 -0700, "steve" <[email protected]>
> wrote:
>
>
> >a prototype can quickly confirm the robustness of a design
>
> Does this imply that the best way to find bugs is to test a prototype?
>
> That's the Bill Gates methodology.
>

On Mon, 25 Jul 2005 13:16:34 GMT, Bob Perlman
<[email protected]> wrote:

>On Sun, 24 Jul 2005 22:31:38 -0700, John Larkin
><[email protected]> wrote:
>
>>On 22 Jul 2005 06:01:19 -0700, "steve" <[email protected]>
>>wrote:
>>
>>
>>>a prototype can quickly confirm the robustness of a design
>>
>>Does this imply that the best way to find bugs is to test a prototype?
>>
>>That's the Bill Gates methodology.
>
>The Bill Gates methodology is to get someone else to pay you for the
>privilege of testing your prototype.
>


And to get rich off of selling failure. Few of us have that option.

John