One thing that has baffled me about the Perl ecosystem is the apparent lack of commercial offerings to both developers and the companies that have Perl as a part of their operation. In fact, when doing some digging to find examples of actual and existing businesses offerings all I could find were the odd recruiters here or there, some training / lecturers and the ActiveState Perl tools / services. Shouldn’t there be more?
As you will probably agree Vagrant is an absolutely fantastic tool for everything from bringing up a single simple dev-machine, to creating complex multi-node clusters for distributed load-testing. With the addition of plugins like vagrant-digitalocean, vagrant-aws and vagrant-hostmanager you can do some pretty cool stuff.
If you have been programming Perl for a while you might be familiar with CPAN, the large repository of every module conceivable. It is a great source for ready made Perl module that can solve almost every problem you are working on, but it is also always changing due to the dilligence of the maintainers of various modules. This post is meant to be a gentle introduction to one way you can do some simple dependency management and add module stability to your Perl projects. As always in Perl: TIMTOWTDI.
Previously I wrote a post on our companys move from Github to self hosted Gitlab. As mentioned in the post we were fairly happy with the move at the time, and this post is an attempt at summarize our experience with it now that we’ve had it running for well over 8 months.
Transitioning from a workflow where I do almost all of my work directly on a pc, to one where I do some of my absolutely non-critical work from my cellphone has been a goal for some time. Here is an update on where I am at now.
For the past few years the company I run has been a paying customer at Github. Generally we’ve been very satisfied with the service, but we have come to realize that it might be time to move on. If our decision has moved us to greener pastures remains to be seen.
For many years I have been running a blog on Wordpress and it has worked pretty well up until now. I guess there has been a gradual change in how I use tech, and this brought me to the realization that for me using Wordpress is kind of cumbersome. Some might find that a mighty odd statement considering the amazing effort the Wordpress core team and contributors have commited, so I’ll try to elaborate.
So today I had to compile Perl 5.14.4 on a new box running Ubuntu 14.10. Followed the normal procedures for getting Perlbrew installed, updated patchperl and installed the Perlbrew cpanm. Then went ahead to install perl 5.14.4.
I was called today by a very helpful KLM representative. He admitted that the experience I had was not one that should occur, and apologized for the inconvenience. After talking a bit about the details we were able to put this matter behind us and I am yet again a happy KLM customer. Thank you KLM for resolving this in such a nice manner.