Ways for a developer to keep it friendly
When I was doing embedded systems work, I
occasionally had to deal with bug reports.
Invariably, the first bug report I would receive (from
a technically competent engineer) would be along
the lines of, "I plugged it in, and it doesn't work
Stage 1 was to find out what the setup was, and try
and duplicate it.
Stage 2 was to get the engineer to talk me through
the problem, until I duplicated it, or he spotted a
mistake. If I duplicated it, the immediate reaction from
me was "OK, I see the bug here now. I'll try and find
it". This is the hardest stage, as slight differences
can cause problems.
Stage 3 was to find the bug, or a workaround.
Immediately I had done so, I e-mailed the engineer
concerned and either just told him I knew what was
wrong, or give him the workaround.
Stage 4 was to fix it, and issue the new software *to
the engineer concerned*. This ensured that the bug
was fixed; if it wasn't, go back to Stage 1
Stage 5 was to pass the new version past QC. If
they were happy, issue the version to the factory. If
not, go back to Stage 1.
In the end, I rarely got an irate engineer the second
time he found a bug, and I usually got the bug fixed.
Re: Cracking in general
> The point is that honest people will
> pay for what they really value, just as
> consumers are still snapping up real
> DVDs for 40 dollars when they could,
> with a little effort, get a MPEG version
> on the internet... they'd rather pay $40
> than the (albeit reasonably small)
> effort it takes to download the pirate
> version, because they get better product
> / manuals / supporting materials /
Agreed; I bought a CD of music I'd downloaded
illegally, just because I listened to it a lot. I felt that if
the music had that much value to me, I should show
my appreciation in a material fashion.
OTOH, I have access to a lot of illegal music via
fileshares on the campus network. I listen to some of
it from time to time, but no more so than I would if I
listened to the radio.