I think that it is safe to assume that code created from scratch that noone else has seen has had less viewing and use that code freely available off of the internet. A programmer that does not test any code that he writes or uses is a fool. If proper testing does not exist, write it, and post it for others to take advantage of.

> How do you know the author hasn't completely ignored
> all patches sent his way?

I don't. Such things are a shame, but do not detract from the usefullness of the code for the situation at hand.

> What if management won't let him release the source?

The programmer needs to talk it out with management. They like saving money, and it they don't than hey, no harm, no foul. Things are always flexible. Apple is doing a pretty good job of being an open-source contributor at the same time as they use that foundation to sell commercial software.

> Is allowing your employees to spend time improving
> their skills "pure folly?"

There are other ways to improve ones skills that writing yet another thing that does something that already exists. I think that one learns a heck of a lot by working within the confines of a larger whole: Teamwork.... managing and understanding large codebases... writing code that MUST play well with others. Tell me, who learns more: The guy who writes yet another 0.0.1a templating system, or the guy who makes a solid contribution to Axkit?

UPDATE: fixed a typo.

()-()
 \"/
  `