Re: Filtering a tachometer generator


Jerry Avins wrote:

> As for documentation, it has been my practice to write down what needs
> to be done, how I do it, why I do it that way*, and a description of
> algorithms and optimizations. If a competent programmer/engineer can't
> produce working code from it, I haven't written enough. I was trained in
> that art by years of writing code for other people with the clear
> understanding that, once delivered and accepted, it was no longer my
> concern (consultation time charged for). Otherwise, my career would have
> changed from creation to maintenance after a few major projects.

We live in different worlds... both in time and place. When I was hired

to my last position at a university, I found out that it was "expected"
of me to run and maintain a couple of PCs. It was not in my contract
but still. It has been common practice in the places I have worked not
to document anything, as there is no costs -- at least not visible on
the balance sheets -- in having PhDs and researchers doing technicians
jobs.

> Jerry
> __________________________________
> * "It seemed like a good idea at the time" is often all I can write.

I know that one just all too well... ;)

Rune

.

Relevant Pages

  • Re: The Schneider Scam
    ... You can't fail somebody for driving, ... him the practice time, or you don't allow him to complete the course. ... I don't know about a dumbell, since I asked you to e-mail me documentation. ... First of all Schneider training isn't free, ...
    (misc.transport.trucking)
  • Re: relative-to-source file names (was: Small, understandable Forth)
    ... Zero existing practice, and no user demand. ... And: Code breaker. ... various operating systems. ... you certainly cannot expect me to read 323 pages of documentation ...
    (comp.lang.forth)
  • Re: My first C# project
    ... With practice, I found that I could write easily understandable code in only 10% more time than rushing and writing code 'normally'. ... High-level documentation is stored elsewhere and documentation saying what a few lines of code do is redundent if you make sure that those lines express what you're doing in a *clear* way. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: unittest: Calling tests in liner number order
    ... For my major project I've got my own test case extraction ... freedom to be quite useful in thinking about the test case. ... signal that it's good practice to allow dependencies between tests. ... documentation with a caveat that it's not good practice, ...
    (comp.lang.python)
  • Re: frequency modulation
    ... Jerry Avins wrote: ... practice is very different from unlicensed baby monitors. ... when I was stuck in the shack at W2HJ and the ...
    (comp.dsp)