testing for corruption

[Fairlight]

On Tue, Feb 05, 2008 at 07:59:10PM -0800, Jeff Harrison, the prominent pundit,
witicized:
> Hi Nancy.  Thanks.  That it is still 2 votes to 1
> against my developing this though - wait make that 2
> to 2 as I would vote yes :-)

If you were counting mine as a vote against, don't.  I was simply exploring
the technical angles outloud that they might prompt further thought.

Whether you write or not is pretty much something I would -not- base
heavily on any input from the list.  I've had requested software ready to
go that never got taken up, I've come up with things that were supposed to
be one-offs that ended up doing (relatively, considering the size of the
market) nicely, and I've been inbetween the two extremes.   

This community is very hard to accurately guage no matter what's said,
and even harder to sell to.  Especially when people express needs, you
design to those needs, and then it sits for a year [or more] before doing
anything.  But hey...someone NEEEEEEDED it!  Right.  (My opinion there has
mostly become, "Wait for someone to commission the work, then make a deal
to retain the rights to the code if there's a decent probability of further
sales.")

Ultimately, I'd say if you mostly want it for your own use, do the project
strictly for your own purposes and to your own design sensibilities
initially.  If you can resell it thereafter, hey...nice bonus.  I wouldn't
do it on spec with the sole intent of marketing it, though.  The above
pretty much goes for most projects in this community, IMNSHO.

mark->