On a very old website..
We had a search page which took some time after submitting to produce results, so in the C apache handler (I told you it was old), we would write out part of the page, with a message saying that the search was happening and please wait a little while, and then follow on with the rest of the page redirecting to the results once they were actually ready (this was the "solution" to just waiting until the results were ready and displaying them, which left the user on the search page and able to keep hitting the search button and submitting multiple requests).
And then came IE 4, which refused to display our message. It turned out that it was waiting for at least 8kb of content to be sent from the server before it would start rendering the content on the screen. My solution to that as an eager young developer, 6 months on the job, was to put the script to the Monty Python "spam" script in to an HTML comment, followed by variations of the word "spam" in capitalisation and geekcode - 5p4m sPAm $pAM
etc. Worked perfectly, everyone's a winner.
10 years later*, I get an email "We've been hacked" and "Tom, CVS says you made this commit..". A client had got fed up with waiting for their search and hit stop in a way that had exposed the python's skit in full
It got replaced with the rather dull but less prone to inflame excitable clients "Padding for Internet Explorer" repeated a thousand odd times.
* Which goes to show, the shiny bits of the website had been rewritten several times in to python, then python + javascript, (its now react I think), but the boring functional part still uses that original search code in C - too scary to update, too reliable to warrant replacement.