Back to Perl after 5 years, they found Claude remarkably good at it
They needed tooling to spawn a Go proxy and run integration tests, using only Perl's standard library. Claude Code wrote most of it, and it beat their usual shell scripts for stability.
Done withClaude CodeSpotted· by HN user dillon· Oct 15, 2026
Result More stable than their usual shell scripts
“I used Claude Code to write the bulk of it and found Claude to be remarkable good at Perl.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
Wanted a simple way to spawn a proxy they were building in Go and to write integration tests for it. Had Claude Code write the bulk of it in Perl, told to use only what’s built into Perl’s standard library and nothing from CPAN.
How it went
HTTP clients, TLS and JSON all turned out to be built in, which made it a stable, easy replacement for what they’d normally write as shell scripts. Their theory: Perl has changed little and has lots of training data.
Try it yourself with Claude Code
Write a Perl script that [starts my service and runs these integration tests: describe them]. Use only modules from Perl's core standard library, nothing from CPAN. Include HTTP requests, JSON parsing and TLS where needed, clear error messages, and a short usage section at the top.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.
Markdown files should just open, so they asked Claude Code for a viewer. It opens instantly: faster, they say, than any other macOS app, and faster than Bitwarden's Chrome extension shows its fill menu.
Migrating a password reset flow, Claude Code and Opus produced code on par with a mid level developer. It needed close supervision throughout, and cost roughly 2 months of Pro subscription for about half a day's work.
A URL shortener side project ran on AWS. Claude Code wrote the GitHub Actions workflows for the move and fixed each failure as it came up. The writer reports zero downtime.
A 7-app monorepo needed an 8 GB memory setting and 25 seconds to typecheck. Claude Code made the changes for the move to oxlint, oxfmt and tsgo, and the team validated each step.
Turning plan files into Claude Code workflows took 5-6 hours each. A script that converts them deterministically, and flags what can move out of the LLM, cut that to 20-30 minutes at about 20% of the tokens.
An inherited app on Azure, an error, and a hunt that could easily take 1-2 days by hand. With CLI access to Azure and the repo, Claude Code ran the config and network checks and found the root cause in about 45 minutes.