My new rules of work backup

First rule, always backup your work..
Second rule, follow rule number one..

As programmer, anything can be happen to your machine/pc/notebook but the worst is lost of your code.. SO, when the time is come, your backup will help you to the safe side..

Backup your work mean backup all your coding (php, c, jar, html, etc OR you need to code it back), your reference (ebook, pdf, txt, browser bookmark, bla2 OR you need to google back all it), application environment(.bash_profile, lib, inc, bla3 OR you need to read a lot again), installer(rpm, src, etc OR you need to download it back) for your app and documents on how to setup and install back your work and application environment (OR you need that readme and try n eror session) .. And don't forget to always manage, documented and commented all your code and work properly..

You can backup into second/external hardisk or CD or usbdisk or web space or tape depend on which backup device you have.. and you can make it autobackup if you wish..

And as always, don't "dah terantuk baru nak mengadah" like me.. My history can be your history.. You should not trust your hardware especially the hardisk.. Yes, you can setup it back from scratch or you may be can recover/repair the hardisk but it will be lots of easy and time/energy/mind/bandwith saving if you have backup..

Add another rule, make sure your backup is safe (don't depend on one backup source only)..

OR you can follow my friend suggestion, "When the time come, resign if you don't have the backup.."

This post is to remind me to always backup my work if i dont want to have the hard time again when my pc hardisk is stop functional and cannot be recover/repair on last week..