Recently I was this close to uploading an "edgy" picture to an imaging application I help develop to test a new deployment under the test user. I was so sick of

Recently I was this close to uploading an "edgy" picture to an imaging application I help develop to test a new deployment under the test user. I was so sick of seeing that same innocuous test image, and after all, it was under the test user and no one would ever see it, right? I resisted and uploaded the test image again. Later that day, I was called and informed that a recent change to one of the server components was mixing up sessions and the client was seeing the test image instead of the image they expected. Needless to say, I was grateful for the restraint earlier that day. I probably would have been fired if the client had seen what I had almost put up instead of the test image. I have also accidentally overwritten a whole column in a development database with a comment about skateboards. This was obviously not a big deal since it was a dev db, but it's just more reinforcement that as boring as it gets to write completely innocuous, repetitive stuff in fields while testing, it is much better than letting something slip through in frustration and getting fired and/or losing customers over it. Like hard drive failure and other inevitabilities, it's not a question of if your dummy data will eventually be exposed to people not meant to see it, but when.