[Elecraft] Why so many problems with K3???

[Guy Olinger, K2AV]

Talk about a troll of a subject.  It states in the question that K3 has too 
many problems.  Really now....but everyone is entitled to their own opinion.

Beta code is beta code.  If one doesn't want to run into beta bugs, don't 
load beta firmware.  Gripe about problems in PRODUCTION firmware.

Not enough QA?  Have any idea of the complexity of the functions being done 
in the software defined radio that is most of the K3?  Really think that a 
3-4 kilobuck radio has the kind of margin that could hire 50-100 full-time 
paid testers to do the code testing that would be necessary to release a 
near production beta upgrade every couple of weeks?

Can do it the Ikensu way, take a year or two to develop a minimalist 
firmware on a model that never gets upgraded, and has only a few un-risky 
changes from the prior model.

What one has available with the K3, IF one wants to participate, and nobody 
is forcing that, is join in the beta testing and make war on the technical 
frontier in a radio one can actually afford to buy and still get upgrades.

And if someone DOESN'T want to beta test, no one is begrudging the benefit 
from OUR work.  But remember, criticise the Elecraft guys on Beta QA, and 
criticise us as well, because if the QA isn't there, the list of the hundred 
odd hams that do ALPHA and pre-Beta testing for Wayne et al and aren't on 
his payroll (unpaid volunteers) didn't catch the problem either. And also 
didn't find the problem in Beta testing soon enough to keep some folks 
happy.

Should not be too quick to think of those volunteer testers as slow and 
ineffective.  The number with professional software developerment experience 
in that list is impressive.  They are the kind of people who by nature like 
messing with software and can understand the kind of testing contribution 
they are making.

Interesting thing is that a lot of us would have done the same thing for 
Ikensu if they had Wayne's inclinations.  But Ikensu never asked   : >)

And if one thinks software should never have bugs, one is living on some 
other planet. Software ALWAYS goes out with bugs in it. There's just 
discovered bugs and undiscovered bugs. With some companies there's also 
fixed bugs that got fixed before the next model. But only God can write 
perfect software and hit a golf ball straight with a one iron.

Well....maybe Tiger Woods on the one iron....

73,  Guy.



----- Original Message ----- 
From: "JIM DAVIS" <nn6ee at astound.net>
To: <elecraft at mailman.qth.net>
Sent: Thursday, April 09, 2009 7:53 PM
Subject: [Elecraft] Why so many problems with K3???


> Our own K3 (s/n 2406) has been flying FB since it was ordered/built/ and 
> sent out in Dec. 2008!
> Maybe
> everybody are asking TOO MUCH of the "Elecraft Guys"? Our latest rev. 
> dwnload was #3.06, but with
> "Beta" there are always problems, so most of us SHOULD WAIT until the 
> gliches are worked through!
>
> Or on the other hand maybe it kinda makes you wonder if maybe the Q/A 
> isn't all it's supposed to
> be at "Elecraft"?
>
> THOUGH, our experience with the "TECH SUPPORT" (DALE) has been nothing 
> short of phenomenal
> especially
> since he's always been very patient with our pleas for help!
>
> Jim/nn6ee
>
> Note: Webmaster! Are you not going to publish this either?
>
> My gripes warrant note like everybody else out here!
>
> Jim/nn6ee
>
>
>
>
>
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>