On Thu, 11 Dec 2003, H. S. wrote:
> Paul E Condon wrote: > > > Documenting software is like writing a good text book. The author must get > > in touch with his "inner Dummy" and speak to his needs. Some geeks have this > > ability, but many do not. > > This is *so* true!! And the troubling part is they simply refuse to > understand this. people will do what they want ... you cannot force/encourage anything upon them ... they will either quit working there or ignore the one asking for "jump over this hoop and that hoop" for free in the case of gpl let the coders hack away ..and let them be happy .. -- thats how GPL works ... people just write code till the wee hours of the night in their spare time .. let the english majors do the sw documentation and let them be happy that they can make lots of contributions and make tons of $$$ selling their nicely documented books get a translator if the tech writer doesnt understand source code i dont see too many tech writers trying to understand all the whacky nuiances of writing "good code" in C and C++ and other languages but hackers have to understand and do the "unmentionables" for "good documentation" dont impose the others rules and philosophy upon the other that dont want to learn the others whacky ideas or dont have the time to do it their way - most of us cant even agree upon what "good documentation" is let alone how it should be written and organized ... - i want coders to hack away ... ( bug free of course :-) c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]