However, I also feel that accurate information
can never hinder you.
Generally true, though I could probably construct a contrived
counterexample (think needle in a haystack).
OK, I guess 'information overload' can occur. But I don;t think this
applies here.
Put it this way. I would never complain if I was given the source code
(or PLD equations or...) for something I was using or repairing. I can
always stick it on the shelf (or on a disk) until I need it.
(Based on
the resulting code quality, it seems to be a relatively
poor one in many cases, but that doesn't make it evil.)
I am not convicned
it;'s a motivator at all, at least not for the
better programmerns (and hardware designers) that Iv'e worked with.
Such people always turn out the best code/circuitry that they can.
Hmm. You may be right that it's not a motiviator to turn out good code
instead of crappy code, but I think it is, or at least can be, a
motivator to create code instead of, oh, say, going rockclimbing - or
to create code for the product in question instead of creating code for
something completely different.
Yes, that seems reasonable. However code written simply becuase you're
being paid for it may well not be teh best code. Whereas if you're doing
something because you enjoy it it's likely you will take pride in your
work and want to do the best you can. Of course 'the best you can' may be
inferior to what others can do.
I will admit I've seen soem well-designed, elegant commerical code and
circuitry. I've also seen some well-designed, elegant open-source and
circuitry. I can't say whether 'the bvest' that I've ever seen was
commerical or open-soruce. What I do feel is that it's incorrect to say
that one is always better than the other, and in particualr that becuase
a piece of code is commerical means it will be good.
-tony