Great suggestions. For developers, I think there are a few additional things to consider. While I completely agree that a file service backup and encryption a

Great suggestions. For developers, I think there are a few additional things to consider. While I completely agree that a file service backup and encryption are a good idea, I think it's important for developers to be able to recover quickly even without these things. 1. Yes, use backup, but also use version control. Keep your commits sufficiently up to date that you will able to get back to work quickly with a fresh new computer. Consider it a bad sign if you have to get your new computer restored to exactly the same state as your old computer to resume developing. 2. Encrypt, but just don't keep highly sensitive files on a laptop. I read that 1 in 10 laptop are stolen, and keep in mind that many aren't stolen because they never leave someone's apartment. If you travel around with your laptop, you're in a higher risk group. Use dummy data and dummy databases. Don't store external passwords to real systems on your laptop. Consider it a bad sign if you can't develop to a local database populated with inconsequential data. 3. Definitely buy the insurance policy, if you'd have trouble coming up with the money for a replacement. But they key here is to make sure that it's just money we're talking about. Try to set up your development environment such that the cost to you of a stolen laptop is the replacement cost of the laptop. I'm a little worried this comes off as overly judgemental, so I just want to be clear that I understand this may not all be within the control of the developer. However, I think that an IT setup that requires people to carry highly sensitive information or passwords on portable devices that are frequently and easily stolen is a sign of a badly broken system, even with encryption.