05 Feb 2015
During the last few months, I had several job interviews with different prospective employers. A few weeks ago a working colleague pointed me to four questions that I could ask my prospective employer that would tell me a lot about the working culture I’d join. As my experience with asking these questions was very positive, I thought I publish them here in my blog. To the best of my knowledge, the original (German) version comes from a guy called Lars Vollmer. What follows is nothing but a translation from German to English.
04 Feb 2015
Recently, I created a simple database management system including user rights management relying on GitHub, Jekyll, Prose, Heroku and a few other open source products. The basic idea is to store all data inside a _data directory in a GitHub repository. A user can access this data through a website (Prose) and manipulate it through a HTML form (JSONForm), but she needs to be authorized to do so (Jekyll-Auth). The solution also offers a simple, yet functional search functionality. Here is a list of products I relied upon:
27 Jan 2015
In one of my last posts I was not sure how R’s different ADF test functions worked in detail. So, based on this discussion thread I set up a simple test. I created four time series:
- flat0: stationary with mean 0,
- flat20: stationary with mean 20,
- trend0: trend stationary with “trend mean” crossing through (0, 0) - i.e. without intercept,
- trend20: trend stationary with “trend mean” crossing through (0, 20) - i.e. with intercept 20.
16 Jan 2015
In an earlier post I explained how to install Jekyll-Auth. In GitHub, every team (and organization and user) receives a six to seven digits integer number as an ID like 1234567. There are cases where you might need access to this information, for instance during the installation of Jekyll-Auth. Unfortunately, there is no easy way to find out a team’s ID. I could not find it anywhere published at the official GitHub website. You can however access this information through the GitHub API.
