rjd@occrsh.ATT.COM (12/04/87)
> Yes, I think the key idea here is the *overall* interface. For > example, three people were working on a software project under my > direction. One rm-ed an entire directory of source, and stammered > something about rm star, spaces, backslashes, and something else. He > was sweating profusely, and had something to say about the > inappropriate user interface that /bin/csh had, etc. > > Well, this has probably happened to some of you, and it's always "well, > we lost a day's worth of work, but we had really good backups, etc." > > Well, we hadn't done backups in about two months. > > So, I fired him. > > The other two saw the "big picture (or what I believe > dawn!stpeters refers to as "the overall interface") and got right on > that evolutionary path! Unless you have a very good reason for not doing backups more often (like twice a day), you probably should have been fired yourself, or was the guy you fired the one responsible for backups? Not backing up more often is pure stupidity. What do you do when the disk decides its useful has ended? Fire the disk? Lot of good that does. If it was his responsibility, maybe it would be possible to also sue him? Randy