Jul 26, 2015 · 2 minute read
So I finally made the jump to a static blog.
I have been contemplating this move for quite some time now. Mostly it’s been a
consideration between Pelican (Python) and
Jekyll (Ruby). Where Jekyll has been more tempting with
the huge ecosystem around Octopress to benefit from.
The downside with Jekyll, and Octopress especially, is that I have to keep an
entire framework of blog generating software around. This was a lesser problem
with Pelican which was smaller, but still a limitation.
Enter Hugo. Hugo is (yet) another static blog generator,
this time written in Go. While I don’t have to touch any of the Go code myself
it has some benefits in being compiled and because of that it’s blazingly fast.
It also doesn’t enforce any directory structure or configuration formats (the
default being TOML).
Setting everything up has been a breeze. I write my posts in Markdown, commit
them to a GitHub repository which automatically notifies a build system which
downloads everything and generates the blog. It then uploads the generated blog
files to the web server and *bam*, we’re live.
I will keep this blog on a temporary domain until I have managed to migrate over
all my old posts. Or well, at least the ones I’d like to keep.
Update: I have finally begun migrating my old posts so this blog has replaced my
old one. A lot of old content has disappeared in the migration. I’ve kept what
little I liked as well as the posts that got a lot of traffic.
Jun 9, 2015 · 4 minute read
(Disclaimer: I am not a lawyer, everything in this post is probably wrong)
Too many times I’ve stumbled across a really useful library or framework that is ridiculously prohibitively licensed. The thing is that most people are simply oblivious to what the license entails and just slap on a GPLv3 (because everyone is using GPLv2, and of course you want the latest version.. right?).
The problem with GPL is that it includes a copyleft. This means that any distributed work that uses anything licensed under GPL is required to be released under a GPL license as well. The reason for this is to force organizations that are developing proprietary software to release their improvements back into the wild.
This is a really good thing in most cases. The Linux kernel use this license to make sure that any company using their code is required to release any bug fixes or features free for everyone. The thing with GPLv2 is that this only applies to your entire project if you include GPLv2 licensed code in your project code base. If you use a third party library or module which is distinct from your code you’re fine and are free to ignore the limitations of the license.
However, this was recognized by GNU and GPLv3 was soon released to fix this “problem”.
So when you license your new awesome library under GPLv3 you are essentially forcing everyone else that use your library to also license their code under the same license. And now nobody can use your code for anything without releasing all of their own code for free.
If you want to prevent people from profiting on (and using) your code you should go ahead with a GPL license. Otherwise pick something else, I explain some of the most common licenses below. Sorted from least to most complex.
This is “(Do) What The Fuck (You Want To) Public License” which is effectively the same as releasing your software under the public domain (which is useful in countries where that’s not a thing). By releasing your code under WTFPL you allow people to do anything they want with it.
The MIT license was developed at MIT (duh!) and is almost the same as WTFPL except that it includes two important points. The first is that the copyright notice must remain intact, i.e. they are not allowed to remove your license from your code. Note that this is not the same as giving any notable recognition for using your code in a released product.
The second point which is far more important is that it removes any liability from using your code. If your code accidentally deletes important files or causes a company financial losses they can’t claim any damages from you.
If you don’t know what license to pick. Pick this one.
Since MIT had their own license it was only a question of time before Berkeley created one of their own as well. The BSD license is almost identical to the MIT license except for one additional point.
This license explicitly prohibits the use of your name or your organization in endorsement of the end product. Anyone using your code is not allowed to claim that you are endorsing their product by letting them use your code.
A rather important thing about the BSD license is that there are two versions. One with four clauses and one with three. The three-clause version is the BSD license and the one you should use if you choose to use this license.
This is the most complex license and I admit that I don’t entirely understand what all of it means. Note that the Apache license is different from Apache (which is a web server) and Apache software foundation (that are maintaining the web server and this license, among other things).
What makes Apache different from the other licenses (apart from it’s far more complex legalese) is that it grants anyone using your code a patent license for any patents that cover your source code. Because copyright and patents are entirely different animals this protects the licensee from patent infringement which makes your code safer to use.
I hope that this gives some clarity in the jungle that is licensing and copyright.
Jan 21, 2015 · 2 minute read
I restarted work on one of my older hobby projects. Though I’m not really sure what my end goal is yet I got a vague idea of what I want to build and it’s nice to have something of my own to code on.
While setting this project up I took some extra time to make sure I got deployments automated from the start. Proper configuration and use of tools saves a lot of time but it also takes several hours to a day or two to set up, depending on the project of course.
There is a ton of guides on the web on how to do this so I won’t reiterate too much here. The project is version controlled with git which allows me to set up a repository directly on the server. In the post-receive hook I am able to add any commands necessary to properly manage the project.
As an added bonus I have fully integrated dependency management with Composer, automated asset optimization with Assetic and database migrations (that write themselves!) with Doctrine. The result is that I write some code, run a command to generate migrations if the code touches the database, and commit before pushing to live.
And that’s it.
Jan 13, 2014 · 1 minute read
I stumbled across this comment a while ago and though it was pretty funny, so I wrote a basic one liner to add the “feature” to my shell. Basically what it does is allowing you to write “fucking” instead of “sudo” for the humorous effect of it, example below.
$ make install
$ fucking make install
Here’s the code for setting it up. The specified configuration file needs to be changed for it to work in other shells than bash.
$ echo "alias fucking='sudo'" >> ~/.bashrc && . ~/.bashrc
Aug 23, 2013 · 1 minute read
Admittedly, it’s not a complete solution if you need it on a page with more than one textarea though. Then it goes from a one-liner to a three-liner.
Jul 26, 2013 · 2 minute read
Bootstrap is an extremely useful set of tools which, I personally believe, everyone should know about and use for their own internal projects. It’s ridiculous what a time saver it is, especially combined with Font Awesome to get over 360 free, scalable icons to use with Bootstrap.
However, they were all very involved to set up and configure, and was generally a lot more than I needed so I was hesitant to implementing them and looked a bit more until I stumbled across an issue on GitHub where someone proposed a better solution.
May 22, 2013 · 3 minute read
Possibly the most common sign of bad code is tight coupling, especially between logic and presentation. It might seem like a good idea to print out the HTML while the data is being generated, but it more often than not leads to a big incoherent mess of tangled code. It also causes other issues, like what happens if an unexpected error occurs in the middle of the page? By then half the page has already been outputted and it might be too late to handle the error nicely.
There are a lot of problems with mixing logic and presentation, but it’s actually very easily solved, especially in PHP. While PHP makes it unnecessarily easy to write shitty code it also provides a lot of ways to avoid it. I’ll use this post to show you how ridiculously easy it is to create a template engine in PHP in three easy steps.
So, we begin by setting up a simple class to wrap our template. The $template variable passed in the constructor is the relative path to our template, e.g. if the templates are in a folder called “views” you should pass “views/.php” to the constructor.
public function __construct($template)
$this->template = $template;
Then we add variables to it, we use magic getters and setters for this to make handling of our template a little more verbose, but you can of course use regular getters and setters if you prefer that.
protected $variables = array();
public function __construct($template)
$this->template = $template;
public function __get($key)
public function __set($key, $value)
$this->variables[$key] = $value;
Lastly we add the printing of the template, this abuses some pieces of PHP’s functionality. Partly that code can be included anywhere and that all the output can be stored and loaded into variables. We load all created variables into the functions variable scope with extract(), this has the nice side effect of not conflicting with variables created outside the function and limiting the template file’s access to variables created in the template. Also, by using chdir() before including the file, we change the working directory to the specified template directory (if any). This allows for including other templates within templates without having to concern ourselves with where the template will be loaded from.
public function __toString()
We can then use it anywhere we want like this. Of course, if you actually need functionality like this you might have more use for a template engine like Twig, which is a bit more extensible and comes with a ton of cool features.
$view = new Template("path/to/template.php");
$view->title = "Hello world!";
$view->description = "This is a ridiculously simple template";