[Elecraft] K3 Updates

[Brett Howard]

When we "attempt" to cut code loose it has to go through our software test
department.  That takes 2 weeks and if they find a bug you just get dumped
with the bugs returned.  Then once they are fixed you begin the 2 week
process all over again...  Very good incentive to make things as clean as
possible.

-----Original Message-----
From: elecraft-bounces at mailman.qth.net
[mailto:elecraft-bounces at mailman.qth.net] On Behalf Of G4ILO
Sent: Wednesday, March 05, 2008 1:17 AM
To: elecraft at mailman.qth.net
Subject: Re: [Elecraft] K3 Updates



Dave Martin-2 wrote:
> 
> I imagine so.  I've found that at my place it takes a long time even
> to produce buggy code.  You guys are writing good stuff.  You're "the
> berries".
> 
Having to go through that process every time they want to test it must be a
good incentive to write code that is *not* buggy. Though not quite as bad as
when I learned to program, when you had to get the code punched up on cards,
then take the deck down to the computer room and put it in the "in" tray,
then wait a couple of hours until they had time to run it.

-----
Julian, G4ILO  K3 s/n: 222 K2 s/n: 392
G4ILO's Shack: www.g4ilo.com
Zerobeat Ham Forums: www.zerobeat.net/smf
-- 
View this message in context:
http://www.nabble.com/K3-Updates-tp15834554p15846031.html
Sent from the Elecraft mailing list archive at Nabble.com.

_______________________________________________
Elecraft mailing list
Post to: Elecraft at mailman.qth.net
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft    

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com