Hello! I'm a senior software developer looking for a role where I can help users succeed. I have 17 years of experience running the gamut from #Perl to #Python to #Ruby to #Go. I love to make relational databases sit up and dance. I've been in the financial and fintech space recently, as well as devprod/infra.
I'm open to full time W-2 or short term consulting.
Email me: pete@petekeen.net or DM me here if you'd to chat about how I can help.
it is perfectly possible to write absolute shit code in #rust or #haskell and it is perfectly possible to write excellent code in #javascript or #perl and shellscripts can be super awesome and lisp doesn't make you a better man and millions of businesses live just fine on mysql and php.
Early #Perl luminary and author (#OReilly camel and llama books, many magazine articles, etc.) Randal Schwartz, a/k/a merlyn, is in dire financial straits.
He needs gainful #employment NOW of any kind, and although his #programming language of choice now is #Dart and the #Flutter framework, he’s willing to fall back on his @Perl chops.
Hello there, I was recently laid off from my 10-year job as a Software Engineer. I'm looking for another Software Engineer position.
At my former position, I worked as a backend developer who managed data and made reports using Perl. I am also familiar with Lisp because I used it as a web scraper turned Perl script. I also familiar with Java since I'm the owner of @morobot
I'm familiar with Python since my blog uses it.
Dear world, I need to hire someone expert in installing & configuring some open-source software on MacOS. Currently my blogging system breaks every time I type "brew upgrade" and I am out of patience. [EDIT: Problem solved.]
Tl;dr: I need to arrange that this 2-line Perl program works and survives updates:
use DBI;
use DBD::mysql;
Will pay an appropriate hourly rate. Private-message or email me.
As a #Perl programmer I find it interesting when people say they hate the sigils in the language… then use phrases like ‘$work’ or ‘$dayjob’ in a social media post concisely showing the value of a sigil.
You run a #Perl script to generate an #SQLite database with an index of all the #HTML files, publish it, and then embed some #JavaScript which uses sql.js to query the contents of the database and display search results.
I mentioned the other day about finding #Perl developers. We're still looking. If you fancy working for one of the oldest Tech news sites in the world why not take a look?
(Maybe if we get enough people we might get some kind of ActivityPub integration in place. It's not high on the ToDo list just yet).
v1.0 then:
“Perl is kind of designed to make #awk and #sed semi-obsolete […] The language is intended to be practical (easy to use, efficient, complete) rather than beautiful (tiny, elegant, minimal).” https://github.com/Perl/perl5/releases/tag/perl-1.0
Why does #Python code from a few weeks ago throw an exception when run with a new version of the language, but #Perl code found in excavations of ancient Roman monuments still runs in newest #Perl?
In a +1 score to #Perl's great back-compatibility, I've had a script called from procmail that's been 100% reliable for the past 15 years maintaining my email, over many years of regular Perl updates.
How... had I never realized that "perldoc -f <builtin-function>” is a thing? Game changer!
I realized this as I'm poking around to find out if there is /any/ way (documented or not) to substitute the current program/topic in the =pod section, so I can copy a script template around and require fewer changes to get up and running.
If anyone has an answer to that (which may be of the form "Nope, no dice”), I would appreciate it.
The most base-level thing that #Perl does is that Perl ensures "you can always update to a later perl"
So if there's newer features in newer perls that you want to use, you should always be able to update to it, and not really break anything because of the high level of attention that we give to backwards compatibility.
I don't think we, as the Perl development core, shout about that anywhere near enough to really drum it in to people's heads.
Today I attended the second meeting of the CPAN Security Group. Lots of interesting discussion. People are thinking deep thoughts about supply chain security and keeping your systems safe. We are always happy to get more interested people involved.
Ever been staying at a hotel and gotten annoyed that you always have to open a browser to log in for wireless access? Yup, me too. A recent instance was particularly frustrating and I had to pull out my favourite Swiss Army chainsaw in order to make my life a bit easier.