But what is state of the art? My interviews since 2013 have let me know that Perl is not any good as a language. Perl is bad and programmers who use Perl are

But what is state of the art? My interviews since 2013 have let me know that Perl is not any good as a language. Perl is bad and programmers who use Perl are bad. If I describe my experience in the industry from 1993 to 2003 which involved lots of Perl in the abstract then it often sounds good in interviews, but if I describe that experience as having been steeped in Perl then it is a huge, useless turn off. The problem is that the state of the art in programming is whatever is shiny and new and often unnecessary. Lots of employers are hiring for Kubernetes experience when they absolutely do not have enough demand for their services to justify messing around with Kubernetes, but it doesn't matter. They also don't have the patience and depth to bother listening to some old person explain in detail why Kubernetes is the wrong tool for them and a waste of resources. Corporate programming has become all about idols and mystery such that Perl has been cast out and Kubernetes is pure awesome no matter how irrelevant. As long as some old person can suck up to confused young people about what counts as cool code and frameworks then they might count as up to date with the current state of the art. And with this the unfortunate reality emerges that for older and experienced contributors starting a company is becoming as easy or easier than actually getting a job.