Platform engineering ·
Where Perl still belongs next to Kubernetes and OCI
Perl is still a practical language on a hosting platform that has been running for years. A lot of the estate was built in Perl and PHP. Replacing it for its own sake does not make a migration. Replacing it where it blocks availability, testing, or a cleaner boundary does.
The notes on this site, many of them from 2013 to 2016, are from that earlier practice: arrays, hashes, dates, and the small programs that show up inside larger systems. They are still accurate as language notes. They are not a description of the current job. The current job is platform engineering: architecture, automation, and the move from older hosting setups toward Kubernetes and OCI.
Those layers fit together. A Perl or PHP service can sit behind a newer delivery path. The container, the pipeline, and the cloud infrastructure do not require the application language to change on day one. They do require the service to have a clear build, a clear configuration, and a way to tell whether it is healthy.
I still use Perl and PHP. I also spend the lead work on the platform around them. The old notes stay up because they are useful. The newer notes are here so the site describes the work as it is now.