4 ms·
It's not like when you are constructing a house and a tornado happens to knock out months of your hard work. Programming is less like laboriously laying thousa
by jeff18 15y ago
It's not like when you are constructing a house and a tornado happens to knock out months of your hard work. Programming is less like laboriously laying thousands of bricks, but more like very carefully laying a small handful of bricks in just the right places after a lot of thought.
I have a feeling that as they start re-developing what they have lost, they will find that the work goes 1-2 orders of magnitude faster than it went when they originally did it and in just a few weeks they will be caught up.
I think the way that they are handling it (treating it as pretty much a project ending blow) is pretty questionable.
- kabdib 15y agoI once lost two weeks of work with an "rm -rf" typo. No backups, just gone. It was the 80s, and I had been careless. Took me about a day and a half to re-create the work, and it was /better/. I'm not saying it's a good thing to lose work this way. But it's seldom utterly catastrophic. (Exceptions like "the SourceSafe database and build machine start pushing up daisies the night before Final" . . . well, for one thing: Don't use SourceSafe, and for Pete's sake, make sure your backups actually work).