There’s a good list of references at the end!
Often, when I’m working locally I like to bounce right over to a GitHub repository url to check something. I ended up writing a bit of code to make this easier. While I was at it, I decided it would be nice to have the same thing for Travis URLs. So, I’ve released this as part of Git::Helpers.
I have checked like a dozen explanations for Python Decorators. Some of them are good. But this Stack Overflow answer just beats them all. Such an awesome answer. It is a bit long as it has built the theory step by step.
Saw this video the other day that, for the first time, explained how quaternions work in a way that I understood. Highly recommended, as I know that for a lot of people they’re a magical black box.
When writing perl modules, more often than not a few dependencies creep in … which makes it a wee bit awkward when developing the module, because I then have to somehow install these dependencies, and I would rather not get them all over the place but neatly in the module directory so that I have at least a semblance of a stable development environment.
So here goes my solution: A little postamble method for my Makefile.PL.
We recently came across Pegex and found it to be an interesting module for parsing text data. Instead of using regular expressions directly, the user can write a grammar for the data to be parsed. The data can be automatically converted to a native Perl object or, if the user desires, it’s possible to use actions to handle the grammar while parsing using a Pegex::Receiver class.
I was reviewing my emacs dot files organization, which at the moment I did it served me well, but I want to know if there are any other better ways to organize your dot files.
Mine just loads a bunch of .el files stored in the inits/ directory in the order the prefixed number in file name states. It also uses use-package to better management.