[Elecraft] Saving K2 VFO modes

[David Woolley (E.L)]

wayne burdick wrote:
> 
> Even though the code is well-documented, I'd want to create 
> theory-of-ops and maintenance documentation before I tried to hand it 
> off to another programmer. This is often necessary for projects where 
> you don't have the luxury of writing everything in an encapsulated, 
> object-oriented language, such as on a PC with virtually unlimited code 
> space.

In my experience, most open source software lacks this sort of 
documentation, so lack of documentation shouldn't be seen as a reason 
for not opening the source.  The only things that should take time are 
getting copyright clearances if anyone but Elecraft owns the copyright 
and making the business case for releasing it.

On the other hand, I'm a little concerned that such documentation 
doesn't already exist.  When I started in the software industry, one of 
the first things one was told was that one should document code as 
though one expected to be run over by a bus, the next day.

-- 
David Woolley
"The Elecraft list is a forum for the discussion of topics related to 
Elecraft products and more general topics related ham radio"
List Guidelines <http://www.elecraft.com/elecraft_list_guidelines.htm>