If dummy data ever proposes a "technical risk" to your projects, I might argue you're using the term wrong.
Variable names are different, and I'll give you that, but creating humorous dummy data in lower environments shouldn't ever be an issue. Injecting a little fun legitimately helps overcome despair, and the harder and more difficult your project/company is, the more it needs a dose of lightheartedness.
No matter what the scrum boards that reduce us to story points say, we're all human beings. When everything is very high stakes, you're in a perpetual state of fight or flight. It's literally physiologically bad for you. Blowing off steam helps.
As a test of our new Sev1 alerting system, I created a phony alert "The hordes of Mordor are descending upon our data center".
I read the comment to mean that we have enough technical risk that we don't need more general risk. This stuff adds risk. As I have heard: "do you want to read your joke in a courtroom for a non technical audience?" - in some fields more so than others, but there is always a risk that something will go horribly wrong, your system will be involved and your code shows up either directly or as a side effect of discovery.
Variable names are different, and I'll give you that, but creating humorous dummy data in lower environments shouldn't ever be an issue. Injecting a little fun legitimately helps overcome despair, and the harder and more difficult your project/company is, the more it needs a dose of lightheartedness.
No matter what the scrum boards that reduce us to story points say, we're all human beings. When everything is very high stakes, you're in a perpetual state of fight or flight. It's literally physiologically bad for you. Blowing off steam helps.
As a test of our new Sev1 alerting system, I created a phony alert "The hordes of Mordor are descending upon our data center".
It was well received by the team.