FPGA Central - World's 1st FPGA / CPLD Portal

FPGA Central

World's 1st FPGA Portal

 

Go Back   FPGA Groups > NewsGroup > DSP

DSP comp.dsp newsgroup, mailing list

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 07-25-2005, 07:31 AM
John Larkin
Guest
 
Posts: n/a
Default Re: Best Practices to Manage Complexity in Hardward/Software Design?

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


Reply With Quote
  #2 (permalink)  
Old 07-25-2005, 03:16 PM
Bob Perlman
Guest
 
Posts: n/a
Default Re: Best Practices to Manage Complexity in Hardward/Software Design?

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

Reply With Quote
  #3 (permalink)  
Old 07-25-2005, 05:32 PM
Baxter
Guest
 
Posts: n/a
Default Re: Best Practices to Manage Complexity in Hardward/Software Design?

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.
>



Reply With Quote
  #4 (permalink)  
Old 07-25-2005, 05:33 PM
John Larkin
Guest
 
Posts: n/a
Default Re: Best Practices to Manage Complexity in Hardward/Software Design?

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

Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Best Practices to Manage Complexity in Hardward/Software Design? [email protected] FPGA 128 08-01-2005 07:26 PM
Re: Best Practices to Manage Complexity in Hardward/Software Design? xpyttl DSP 1 07-24-2005 07:07 AM
Re: Best Practices to Manage Complexity in Hardward/Software Design? Ben Bradley DSP 4 07-23-2005 07:16 PM
Re: Best Practices to Manage Complexity in Hardward/Software Design? Jacob Sparre Andersen DSP 1 07-23-2005 12:48 PM
Re: Best Practices to Manage Complexity in Hardward/Software Design? Matt Timmermans DSP 0 07-23-2005 05:49 AM


All times are GMT +1. The time now is 07:22 PM.


Powered by vBulletin® Version 3.8.0
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0
Copyright 2008 @ FPGA Central. All rights reserved