Subject: Re: AW: Reading code from stamp
Archiver
Posts: 46,084
I also make a living making products that are stamp based. Everything said
in these two e-mails is true and it is amazing what some competitors will
do to swipe a product.
In terms of back-up this is what I recommend for my clients that I develop
controller programs for:
a. one copy at the office that is accessible to anyone who needs to use the
code (operations, maintenance, engineering, etc.) - typically this is a read
only copy.
b. another copy at the site in a protected environment (fireproof safe)
c. a third copy off site in a very safe place (safety deposit box)
Whether they follow this or not is their business but I sleep a lot better
at night. The only hassle with this is when the software is upgraded, a
procedure has to be in place to insure all the copies are updated within
hours of each other.
____________________________________________________________________________
____________________
On the subject of reading the code on a stamp, don't forget that some of us
make a living using stamps. I manufacture a product that uses a stamp. If
someone could read my code that I have developed over several years, the
they
could easily bootleg my product and take food off my table. I know that I
have wished I could read a stamp sometimes, but in the wrong hands this is a
very bad idea. Please keep this in mind before anyone makes this ability
readily available. And yes I do have patent protection on my product, but
every bootleg sell hurts. Just because it's illegal doesn't stop people from
doing it. If you wrote it once you can write it again, it SUCKS but you can
do it.
Message: 13
Date: Thu, 7 Jun 2001 11:33:37 -0500
From: "John Ledford" <john@k...>
Subject: RE: Reading code from stamp
> It only takes a harddisk crash for most people to qualify "idiot" then ...
Well, I don't want to tread into this pissing match, but I did want to point
out that hard drives crash all the time. It's a fact of life. You have
several options:
1) Burn a CD
2) Print it out
3) Put on floppy
4) Jaz drive (or equiv)
5) Put it on another machine
6) Get a raid card with a mimimum of mirroring turned on
7) Pay for off site storage of backup tapes
8) Store it on an internet storage site (like maybe fusion one ????)
.... yada yada ....
You get the idea ... if you truly need to be able to find it, once done with
the project, put it in an "archive" directory. Then save this directory all
over the place in case one place dies. Consider off site storage as well in
case your house burns down.
I work from a laptop that get's lots of abuse. You can bet your rear I dump
things on the server often (actually, not often enough ... need to get one
of those background file sync programs that does it while I am not watching
[noparse]:)[/noparse] .... I've lost a full weeks worth of work and boy you can bet I was
pissed (and learned how to back things up often [noparse]:)[/noparse] ...
Take care!
John
in these two e-mails is true and it is amazing what some competitors will
do to swipe a product.
In terms of back-up this is what I recommend for my clients that I develop
controller programs for:
a. one copy at the office that is accessible to anyone who needs to use the
code (operations, maintenance, engineering, etc.) - typically this is a read
only copy.
b. another copy at the site in a protected environment (fireproof safe)
c. a third copy off site in a very safe place (safety deposit box)
Whether they follow this or not is their business but I sleep a lot better
at night. The only hassle with this is when the software is upgraded, a
procedure has to be in place to insure all the copies are updated within
hours of each other.
____________________________________________________________________________
____________________
On the subject of reading the code on a stamp, don't forget that some of us
make a living using stamps. I manufacture a product that uses a stamp. If
someone could read my code that I have developed over several years, the
they
could easily bootleg my product and take food off my table. I know that I
have wished I could read a stamp sometimes, but in the wrong hands this is a
very bad idea. Please keep this in mind before anyone makes this ability
readily available. And yes I do have patent protection on my product, but
every bootleg sell hurts. Just because it's illegal doesn't stop people from
doing it. If you wrote it once you can write it again, it SUCKS but you can
do it.
Message: 13
Date: Thu, 7 Jun 2001 11:33:37 -0500
From: "John Ledford" <john@k...>
Subject: RE: Reading code from stamp
> It only takes a harddisk crash for most people to qualify "idiot" then ...
Well, I don't want to tread into this pissing match, but I did want to point
out that hard drives crash all the time. It's a fact of life. You have
several options:
1) Burn a CD
2) Print it out
3) Put on floppy
4) Jaz drive (or equiv)
5) Put it on another machine
6) Get a raid card with a mimimum of mirroring turned on
7) Pay for off site storage of backup tapes
8) Store it on an internet storage site (like maybe fusion one ????)
.... yada yada ....
You get the idea ... if you truly need to be able to find it, once done with
the project, put it in an "archive" directory. Then save this directory all
over the place in case one place dies. Consider off site storage as well in
case your house burns down.
I work from a laptop that get's lots of abuse. You can bet your rear I dump
things on the server often (actually, not often enough ... need to get one
of those background file sync programs that does it while I am not watching
[noparse]:)[/noparse] .... I've lost a full weeks worth of work and boy you can bet I was
pissed (and learned how to back things up often [noparse]:)[/noparse] ...
Take care!
John
Comments
Ok, maybe not then !
Original Message
From: Shand, Gerry W., Celanese/CA [noparse]/noparse]mailto:[url=http://forums.parallaxinc.com/group/basicstamps/post?postID=LHXyB6WVWwf6yfQxf2WilD7dmZv2GsxxCoKpOCwsOQc8MoiJLUbIyWXRfuL3OJ17yuYW0r5F5VIgw5XM]gwshand@c...[/url
Sent: 08 June 2001 14:38
To: 'basicstamps@yahoogroups.com'
Subject: [noparse][[/noparse]basicstamps] RE: Subject: Re: AW: Reading code from stamp
[noparse][[/noparse]SNIP]
a. one copy at the office that is accessible to anyone who needs to use the
code (operations, maintenance, engineering, etc.) - typically this is a read
only copy.
b. another copy at the site in a protected environment (fireproof safe)
c. a third copy off site in a very safe place (safety deposit box)
[noparse][[/noparse]SNIP]