Those habitual mitigations go a long way. Just like there is defensive programming, there is defensive usage.
Under Windows: Don't put your files into "My Documents" or similar folder hierarchies; you never know if old software will correctly deal with the abstraction.
Working with files in general: Avoid nonstandard unicode names or long paths so your external hard drive doesn't choke on them. Avoid case sensitivity even when it is allowed on Unix systems, since you can't assume Windows won't ever touch them. Avoid whitespaces in names because sooner or later, some script won't escape them.
On the internet: Never draft long comments in the browser; always use a local text file. Anything can happen in the browser.
In games: Never save your game during what looks like a complex scripted scene even if the game does allow saving.
Using search engines: Avoid keywords that are likely to confuse/distract the search.
With dropbox-likes: Give it some time to sync even after the icon is green; god knows what is being predictively shortcutted under the hood.
Everywhere: Restart the program or system if certain signs of corruption appear. You don't know what's going wrong, but you know something is, and barring some unusually careful compartmentalization, a piece of software is still a state machine which, once it has strayed from the right path, cannot be trusted at all. OSes nowadays are adapted to this, but much of software is not, and you do not want to have it corrupt your file.
Under Windows: Don't put your files into "My Documents" or similar folder hierarchies; you never know if old software will correctly deal with the abstraction.
Working with files in general: Avoid nonstandard unicode names or long paths so your external hard drive doesn't choke on them. Avoid case sensitivity even when it is allowed on Unix systems, since you can't assume Windows won't ever touch them. Avoid whitespaces in names because sooner or later, some script won't escape them.
On the internet: Never draft long comments in the browser; always use a local text file. Anything can happen in the browser.
In games: Never save your game during what looks like a complex scripted scene even if the game does allow saving.
Using search engines: Avoid keywords that are likely to confuse/distract the search.
With dropbox-likes: Give it some time to sync even after the icon is green; god knows what is being predictively shortcutted under the hood.
Everywhere: Restart the program or system if certain signs of corruption appear. You don't know what's going wrong, but you know something is, and barring some unusually careful compartmentalization, a piece of software is still a state machine which, once it has strayed from the right path, cannot be trusted at all. OSes nowadays are adapted to this, but much of software is not, and you do not want to have it corrupt your file.