Normal error message in Perl:<p><pre><code> $ perl -Mstrict -e 'say $x'
Global symbol "$x" requires explicit package name (did you forget to declare "my $x"?) at -e line 1.
Execution of -e aborted due to compilation errors.
</code></pre>
With the addition of `Coy` module [1]:<p><pre><code> $ perl -Mstrict -MCoy -e 'say $x'
-----
Gautama dies near
a monastry. Two woodpeckers
fly over the lake.
-----
Or Wunt's commentary...
Global symbol "$x" requires explicit package name (did you
forget to declare "my $x"?)
(Analects of -e: line 1.
Execution of -e aborted due to compilation
errors.)
</code></pre>
[1]: <a href="https://metacpan.org/pod/Coy" rel="nofollow">https://metacpan.org/pod/Coy</a>
A few times a month/year I'll get some email because the sender made a typo of the domain they wanted. Postmaster notifies them with:<p><pre><code> your mistake not mine
email sent to wrong address
retry with more care</code></pre>
The old Net+ errors[1] are still golden. My favorite:<p><pre><code> A file that big?
It might be very useful
But now it is gone.
</code></pre>
[1] <a href="https://8325.org/haiku/" rel="nofollow">https://8325.org/haiku/</a>
Juniper networking equipment has a hidden CLI command that spits out a nerdy or sleep deprived haiku:<p>E.G<p><pre><code> Juniper> show version and haiku;
IS-IS Screams,
BGP peer flapping;
I want my mommy!
TTL down one
the end nearer with each hop
little packet, poof.
Amazing photons
Carry our data worldwide
Never seem to stop
My session is dead:
Forgot to commit confirm.
Where are my car keys?
</code></pre>
For some reason, it’s hard to find all of them compiled in one place. I think it changes over time depending on the version of JUNOS and the hardware platform.<p>It was always a little uplifting when you had an incident occurring and you needed a little something—anything—to keep you going (:
What is it with Haiku? The whole 5-7-5 structure just doesn't ring true with me at all. I mean, I get that it is enigmatic, but it just seems like it's enigmatic purely by virtue of not having any other redeeming quality.
<i>Yesterday it worked / Today it is not working / Windows is like that</i><p>Reflecting an understanding of the state of computing usability last updated in the early 90s.
The greatest error message in Haiku ever was:<p>I am so sorry.<p>Something struck me in the rear.<p>I just ... wound up ... here.<p><a href="https://avatar.fandom.com/wiki/Transcript:The_Tales_of_Ba_Sing_Se" rel="nofollow">https://avatar.fandom.com/wiki/Transcript:The_Tales_of_Ba_Si...</a>
These are lovely and lighthearted with a 5-7-5 structure, but for anyone interested in how English might actually express the spirit and content and structure of haiku, here's a nice article.[1] Or, of course, WP as a jumping off point.[2]<p>But long live creativity in constrained form, whatever the label!<p>[1] <a href="http://britishhaikusociety.org.uk/2011/02/english-haiku-a-composite-view/" rel="nofollow">http://britishhaikusociety.org.uk/2011/02/english-haiku-a-co...</a><p>[2] <a href="https://en.wikipedia.org/wiki/Haiku_in_English" rel="nofollow">https://en.wikipedia.org/wiki/Haiku_in_English</a>
Reminds me of The Tao of Programming.<p><a href="https://www.mit.edu/~xela/tao.html" rel="nofollow">https://www.mit.edu/~xela/tao.html</a><p>Huge pearls of wisdom.