93% of Paint Splatters Are Valid Perl Programs

First, "valid" and "correct" are different things. A syntax checker only asks "can I read this?" It never asks "does this do anything useful?" A splatter of slashes might be accepted, yet do nothing at all.

Second, reading code takes most of a developer's day. Hours go into fixing a script that looks like static. After that, you have to fix it again, because the person who wrote it didn't leave a note.

And this hits your money. Slow fixes cost more, and hiring gets harder when a codebase is written as a puzzle. New staff take longer to get useful, and every typo takes longer to spot.

The bigger picture: readable code won

Perl's old motto was "there's more than one way to do it." Python pushed the opposite idea: one obvious way, easy to read. For new projects, the readable camp won.

That shift came from pain, not taste. Software gets handed between people and rewritten years later. A language's tolerance for mess becomes a tax on whoever maintains it next.

So don't read the paint-splatter joke as "Perl is bad." Plenty of billing systems and log crunchers still run on Perl every day. Read it as a reminder that clever and clear are not the same.

What to watch next

The punchline is getting automated. Code assistants now generate thousands of lines a day, and some review tools rank code by whether it runs. If a program passes, it can slip through review while still being junk.

You can borrow the same filter. When someone shows you a clever one-liner, ask what it does, not whether it compiles.

Key Takeaways

• The 93% claim is a joke, but the underlying quirk is real: Perl accepts messy symbol soup.
• Valid code only means the computer can read it, not that it does anything useful.
• Unreadable code costs real time and money when bugs appear or staff change.
• Modern languages and style guides trade clever tricks for clearer, longer names.

Frequently Asked Questions