• PixelsCamp, a hackathon is reborn

    11 Oct 2016

    Hackathon’s are pretty cool, but here in Portugal they’re also quite rare. For years we had Codebits, organized by the web dev arm of the biggest telecom provider in Portugal and it was sweet. Regretably though, 2014 was the last year it was organized. A €1B scandal and almost bankruptcy that forced the telecom provider to be sold to the highest bidder probably made sure Codebits would not return.
    Read full post...

  • AnsibleFest London 2016

    21 Feb 2016

    This year I attended AnsibleFest in London. I have been using Ansible extensively at work and a combination of very interesting talks, being somewhat nearby (read, not across an ocean) and not having a super expensive ticket price made it so that I could go. The conference itself started early in the morning and happened in a hotel very near the O2 Arena. It had a kind of lobby with about ~5 sponsor booths, and one very large conference room with a low stage.
    Read full post...

  • 2015 in review

    09 Jan 2016

    In December I decided that starting to write year in review posts each year would be a cool way to look back and check how productive I was during the year, and if I manage to do this for more than a year it’ll at least be fun to get a local perspective on the past when I’m older. The thing is that writing this in December seemed wrong so I left it to January, and then put it off without any reason. Anyway, let’s do this.
    Read full post...

  • Easily run python functions from the command line

    17 Nov 2015

    Let’s say you have a python file and you want to run some functions from it in the command line. You have a folder called:
    Read full post...

  • Pull requests without the messy commit history

    17 Oct 2015

    So you’re using some kind of configuration management system and you use a pull based deploy method where nodes pull configuration and set themselves up. Whenever you make changes to these configuration files you’re probably committing those changes and pushing them to the place where you keep these files so that you can test if your changes don’t break the machines. You’re probably doing this in a feature branch and eventually stuff will break, stuff will un-break and every time you’re committing and polluting this feature branch. When you’re done and want to merge things into master you’re going to have a pull request with a bunch of commits that are just experiments along the way. Now there’s a couple of reasons why having too many useless commits in a pull request aren’t ideal but the best one is that reviewers and yourself will have a much harder time understanding changes because the really useful commits might be hidden among the bug fixes and experiments. Let’s see how to prevent it.
    Read full post...