Midas van Oene

Two player IDs in an if statement

Thu, 23 Apr 2026 10:00:00 +0000

Somewhere in src/lib/scoring/engine.ts of my Big Five personality quiz that matches fans to NEC Nijmegen players, line 58 has an if block with two player IDs in it, multiplying their match score by 0.92. After weeks of per-player biographic research and three deep-research reports, that’s how I stopped Bryan Linssen and Dirk Proper from winning 14% of matches each.

if (player.id === 71 /* Dirk Proper */ || player.id === 30 /* Bryan Linssen */) {
  score *= 0.92; // 8% penalty
}

This is nec.quest.

The setup

NEC in the cup final, two weeks out. I’m a supporter, I’m a dev, the itch is real. Scope locked in an afternoon: a Big Five personality quiz that matches you to one of the 27 players in the squad. Dutch, English, Japanese. Ship before Sunday or don’t bother. Relevance drops to zero at the final whistle.

The research was thorough. The category error was still there.

I didn’t meet any of these guys. Nobody was letting me interview 27 footballers two weeks out from De Kuip. So Claude and Gemini deep research ran per-player biographic passes across Dutch newspapers, international press, Wikipedia, FotMob, WhoScored, Transfermarkt. The reports are published alongside this post.

Three examples.

Thomas Ouwejan, left-back, 29. On the pitch: high work rate, 0.41 assists per 90 from overlapping runs. Off the pitch: he and his girlfriend hand-renovated the upper floor of an old butcher’s shop in Westbeemster. Stripped six layers of wallpaper himself. There’s the Conscientiousness anchor. The Workhorse.

Dirk Proper, midfielder, 24. 167cm, 63kg, 81.7% pass accuracy. Active psychology student at Radboud, and the club reschedules his gym sessions around exams. Openness and Conscientiousness in one person.

Tjaronn Chery, 37, captain. His father left when he was three and never came back. His brother is his professional agent. He talks openly about being the father figure in the dressing room he never had at home. The Patriarch.

Research is real and deep. Here’s the thing: none of it fixes the fundamental mismatch. Big Five is a self-report instrument, built to measure how you describe yourself. I’m feeding it third-party biographic inference about them. No amount of newspaper reading bridges that gap. Still absurd. Just earned absurdity now.

Turning biographies into magic numbers

Research gives you anchors. It doesn’t give you a number between 0 and 100.

Ouwejan renovating a house, how high is his Conscientiousness? 75? 85? 92? No ground truth. Bryan Linssen sabotaging opposing goalkeeper interviews by lowering the mic stand: high Extraversion, or low Agreeableness through mischief? Pick your frame, get different numbers.

Reasonable mappings, I’d say. Accurate, I wouldn’t.

The scoring engine is 85 lines of literals

const weight = 1 + Math.pow(extremityRaw / 50, 2) * 3;
// ...
return Math.pow(similarity, 3);

As math, the weight function is:

\[W = 1 + 3 \left( \frac{E_{raw}}{50} \right)^2\]

And the similarity:

\[S = (1 - d_{norm})^3\]

Per-trait weighted squared distance, where players sitting at the extremes of a trait (close to 0 or 100) get up to 4× weight. Normalize, invert, cube it. Combine with trigger keyword overlap at 75/25. That’s the whole engine. Every weight is a bare literal. The 1, the 3, the 50, the cubing. No config, no admin panel, no A/B.

For a two-week fan project, a real weighting framework is overkill. A tuning constant is a hypothesis. Ship, measure, tune.

100k Monte Carlo runs and the Linssen problem

scripts/analyze.ts sweeps 100 → 1M runs and classifies players as “never matched”, “<1%”, or “>10%”. First pass: Linssen and Proper eating 14% each. Both sit near the median on nearly every trait, so everyone is vaguely close to them.

The right fix is a data-driven averageness metric: distance from the mean profile, penalize proportionally. The honest fix at midnight was if (player.id === 71 || player.id === 30) score *= 0.92. Two names in an if.

Here’s the one I’d argue against myself on. The calibration scripts reimplement the minigame scoring math instead of importing from the engine. They’ve drifted. analyze.ts uses + (score - 0.5) * 30. The real code uses pushVector(C, (score - 0.5) * 1.5). Different model. My calibration runs are against a version of the app that stopped existing two commits in. Real bug, not a cute tradeoff. One module from day one would’ve prevented it.

It had to run on a toaster

SvelteKit with adapter-static, ssr = false, prerender = true. nginx:alpine in Docker, Oracle OCI always-free VPS, Cloudflare in front caching everything except the Umami endpoint. 27 prerendered result pages for OG tags, hydrate client-side from there. Self-hosted Forgejo Actions pushes the image on every commit to main.

Shareable tactics URLs: formation index and player IDs joined by dots. No base64, no lz-string, no server state.

?t=0-1.4.3.14.11.6.23.25.30.10.18

33 characters of querystring. The full lineup a user shares is in the link itself, which means Cloudflare can cache it like any other URL. Zero DB rows.

If your app has no real server state, don’t build a backend. My origin barely noticed the launch because the CDN served nearly everything. There’s a comment above /_app/immutable/ in my nginx.conf telling future-me never to fall back to index.html on a miss: “If the file is missing the build is stale. Return 404 so Cloudflare doesn’t poison the JS URL with an HTML response.” Someone got burned. That someone was me.

Adding Japanese for a single striker

620 translation keys per locale, compiled into 625 Paraglide message modules. NL, EN, JA.

I didn’t plan Japanese. It happened because of Koki Ogawa, NEC’s Japanese striker. There’s a small J-league-tracking audience that follows him, and the research had surfaced real color: the Japanese trio at the club hire a chef from Amsterdam to cook for them, Ogawa once almost bought weed ice cream for his daughter because he didn’t recognize the smell. Adding Japanese meant those players got their own language in their own quiz. Mid-size Eredivisie club, 27 players, two weeks, three languages, one Japanese striker. Doing it anyway is the joke.

The tell that Japanese is second-class in my own codebase: the helper script add_new_strings.cjs hardcodes Dutch and English only. Every new Japanese string gets added by hand afterward. I never generalized it. Shipping beat elegance.

What I’d do differently

The date 🏆 19 april — NEC vs AZ — KNVB Bekerfinale — De Kuip is hardcoded into a Svelte component. It ships forever until I edit the file. Should’ve been a config value with a now > finalDate guard.

The calibration scripts should import from the engine, not reimplement it.

The 2200ms “calculating your result” spinner is pure theater. The match is deterministic the moment the screen mounts. The setTimeout is the only reason anyone feels like something is happening. I’d keep the drama. I’d just admit it. If your result is ready in 4ms, nobody believes you tried.

Zero tests. 113 commits. Fine for a two-week ship. Not fine for anything that stays alive, and this one is still live.

nec.quest. Take the quiz.

Git cheat sheet - most used commands

Fri, 26 Jan 2018 00:00:00 +0000

Git Cheat sheet

** Still a work in progress :-) **

Git Cheat sheet
- Customization
- Starter commands
  - Adding an existing remote to an existing project directory

Customization

Git repository:

Git username:

I did add the option to inputbind your Git password, but if you do not feel comfortable inputting passwords into this site I recommend copying the command into a text editor and adding it there. You can also use Github’s GUI to retrieve the SSH URL, how to do this is shown later.

Git password:

Starter commands

Adding an existing remote to an existing project directory

Initialize a git repository in the directory

git init

Add the git repository as origin

git remote add origin #@GITREPO@#

Set branch to master

git config branch.master.remote origin

git config branch.master.merge refs/heads/master

Pull any files from repository (like README or LICENSE files)

git pull

Create a push-helper

Instead of using the inputbinder on this site to generate the Git URL you can also use the GUI to find the SSH url. Go to your repositories’ page and click on SSH.

Copy the link to your clipboard

sudo nano push.sh

  #!/bin/bash
  echo "Pushing changes..."
  git push https://#@GITUSERNAME@#:#@GITPASSWORD@#@github.com/#@GITUSERNAME@#/#@GITREPO@#.git
  echo "Script finished"

Add the push.sh file to your .gitignore

echo '/push.sh' >> .gitignore

Make the push.sh file executable

sudo chmod +x push.sh

Add changed files to staging

git add .

Commit staged files

git commit -m "Initial commit"

Use push.sh to push changes

. push.sh

If you would like to use aliases for running the push command, check out my blog post about bash here.

However great using the Git command line is, there are plenty of other ways to work with the Git protocol. The, in my opinion, two greatest candidates are GitKraken (cross-platform) and SourceTree (Windows).

App: HTML / CSS / JS starters boilerplates

Sat, 20 Jan 2018 01:39:50 +0000

I often start side projects and every time I have to google standard HTML5 boilerplates. I might as well put some extra time into it and expose a few of my custom boilerplates.

For now I have added three types: basic, styled, and interactive (html/html+css/html+css+js). Everyone is free to use the app and request pulls.

App website: starters.apps.midasvo.nl
Github repository: midasvo/starters

Enjoy! :)

Bash

Sat, 28 Oct 2017 00:45:50 +0000

Useful Bash!

Useful Bash!
Requirements
- Customization
Basics

Requirements

The tutorials assumes:

Ubuntu 16.04

Customization

Pathname:

Alias:

Scriptname:

Basics

This chapter shows you the basics of how to move around a terminal, how to create a bash script, how to run a bash script, and how to alias the bash script (first temporarily, and then permanently).

How to move around

Use cd to get back to your root directory

Use cd .. to traverse one directory back

Use cd DIRECTORYNAME to enter that directory

Use ls or ls -l to display the directory content

Use cd DIRECTORYNAME/SUBDIRECTORYNAME to traverse to a specific directory from the current working directory

Use cd /ROOTDIRECTORYNAME/DIRECTORYNAME/SUBDIRECTORYNAME to traverse to a specific directory from the root directory

How to get your current directory

pwd

Creating a script

sudo nano /#@PATHNAME@#/#@SCRIPT@#

After running the nano command we can start editing our script.

The script

A simple script to start with is outputting some text, let’s start by echoing ‘Hello World!’

Before we get to that we need to fulfill a requirement of any bash script, the #!/bin/bash at the start of the script.

Add #!/bin/bash to the top of the file.
Add echo "Hello World!" to the second line.

Hit CTRL+X, Y, and ENTER to save the script.

Download the script here

Making the script executable

chmod +x /#@PATHNAME@#/#@SCRIPT@#

Running the script

. /#@PATHNAME@#/#@SCRIPT@#

Making aliases

alias #@ALIAS@#='. /#@PATHNAME@#/#@SCRIPT@#'

The “.” marks the script for execution.

By running that in the command line we create the ‘#@ALIAS@#’ alias which will execute the #@SCRIPT@# via its’ full path.

Using the alias

#@ALIAS@#

Using command-line parameters

User input typed after the script call can be accessed by the dollar sign, an example:

We create the following script:

#!/bin/bash
echo "The answer to the question of $2 is $1."

Which will output “The answer to the question life is 42.” if called as follows:

#@ALIAS@# 42 life

Download the script here

Making the alias permanent

Once you terminate your SSH session your alias is lost. The alias can be made permanent by altering the “bashrc” file.

The file is located at ~/.bashrc, you can edit it using any text editor.

sudo nano ~/.bashrc

Here is a link to a default bashrc file as example

As you can see in the example aliases are defined on a new line, regardless the place.

  # some more ls aliases
  alias ll='ls -alF'
  alias la='ls -A'
  alias l='ls -CF'

So if we want to make our alias persistent we need to add

alias #@ALIAS@#='. /#@PATHNAME@#/#@SCRIPT@#'

anywhere in the file - as long as it is on a new line.

After saving the file using CTRL+X Y ENTER we need to run our bashrc file

. ~/.bashrc

Which finalizes our changes without having to terminate and reconnect our session.

A better way!

So now we have seen how to add the alias to the bashrc file, however it would be better to keep these aliases in a seperate file. Firstly because it is easier to edit, and secondly because it is awesome for portability. If you have certain aliases you use a lot, push the file to version control and keep access to it even on other systems.

We need to uncomment or add the following code to reference our not-yet-created bash_aliases file.

  if [ -f ~/.bash_aliases ]; then
  . ~/.bash_aliases
  fi

Which simply states that if the bash_aliases file is found, run the bash_aliases file - effectively including aliases created in the bash_aliases file.

Create the bash_aliases file

sudo nano ~/.bash_aliases

Copy the following code block (when in clipboard, rightclick on terminal editor window) and save the file (CTRL+X, Y, ENTER).

  # Bash alias definitions
  alias #@ALIAS@#='. /#@PATHNAME@#/#@SCRIPT@#'

After adding an alias we need to run the bashrc file.

. ~/.bashrc

From now on aliases defined in the bash_aliases file are permanent.

A good alias to add secondly is the one for rerunning the bashrc file

sudo nano ~/.bash_aliases

Add the following line:

alias updatealiases='. ~/.bashrc'

Save the file (CTRL+X, Y, ENTER).

Use . ~/.bashrc for the last time and you are ready to add more aliases.

Now, when you add a new alias you only have to run the updatealiases command.

Executing aliases periodically

Sometimes you want a script to run at certain times, in this case we do not even have to reference the script - but simply use the alias.

CRON

Start editing your cron configuration by running crontab -e.

  The time and date fields are:

         field          allowed values
         -----          --------------
         minute         0-59
         hour           0-23
         day of month   1-31
         month          1-12 (or names, see below)
         day of week    0-7 (0 or 7 is Sunday, or use names)

An example cron command would be:

0 1 * * * . /#@PATHNAME@#/#@SCRIPT@#

(remember the . is part of the command because it says execute the script at the following path.)

<minute> <hour> <day_of_month> <month> <day_of_week> <command>

  0                                   |                minute
  1                                   |                hour
  *                                   |                any
  *                                   |                any
  *                                   |                any
  /#@PATHNAME@#/#@SCRIPT@#          |                command

This script runs on the 0th minute, every 1 hour, on any day, any month, and any day of the week. In other words, every hour, forever.

Setting up Letsencrypt on Ubuntu 16.04

Mon, 16 Oct 2017 01:39:50 +0000

Updated: 19-01-2018 - bug prevents requesting cert, added webroot method which still works

Customization

You can customize the guide by altering the desired website name in the text box below, the guide will use that instead of the example.

Website:

Intro

Easily setup HTTPS on your websites by using Letsencrypt with Apache2 on Ubuntu 16.04!

Quick-guide

Add the cerbot repository

sudo add-apt-repository ppa:certbot/certbot

Update

sudo apt-get update

Install certbot

sudo apt-get install python-certbot-apache -y

~~sudo certbot --apache -d #@WEBSITE@#~~

^above command no longer functioning (19-01-2018), will be fixed in future.

However, there is another way to do this: webroot. You point certbot at your sites folder

/var/www/#@WEBSITE@#

You will have to answer a couple of questions (like do you want to force https) and it will be done!

certbot --authenticator webroot --installer apache -d #@WEBSITE@#

Setup renewal

sudo crontab -e

Add the following and save:

0 * * * * /usr/bin/certbot renew --quiet

This runs the ‘certbot renew –quit’ command every 0th minute, aka every hour. You can change the time here.

Apache2 Virtual Hosts with Ubuntu 16.04

Mon, 16 Oct 2017 01:39:50 +0000

Work in progress (update/expansion) since 20-01-2018

Intro

Before we can complete this:

We will first configure the server so we can create one Virtual Host directed at a DocumentRoot. After that you will find a small section with the commands to quickly create new Virtual Hosts knowing that the server is fully configured. However, the DocumentRoot method is not the only way to setup Virtual Hosts. Sometimes you have an application running on a specific port - think of Python and Node.js applications.

You will find that when you play around a lot with these Virtual Hosts (maybe you have a ton of side-projects…) that there is a need to automate this process using scripting. I do recommend you do not skip ahead to that section but try to understand what you are doing. If you are new to Linux (server) administration make sure you get a good grasp of the commands and terminology that is used. I try to include in-depth sources, but that is still a work in progress.

Do not worry about not understanding everything when you start out, you can practically copy paste through the steps and you will have a working Virtual Host.

Lastly there is a reference to a different article on how to setup encryption (TLS/SSL) using LetsEncrypt.

Customization

You can customize the guide by altering the desired website name in the text box below, the guide will use that instead of the example.

Website:

Installation & configuration

Update the repositories and install apache2 (some may prefer nginx, but this guide focuses on apache2 - beware there are definitive differences between the two).

sudo apt-get update

sudo apt-get install apache2 -y

It is common practice to place the DocumentRoot of apache2 website in the /var/www/ directory. Within that directory you create separate directories for the different Virtual Hosts you intend to create.

sudo mkdir -p /var/www/#@WEBSITE@#

We change the ownership and permissions using chown and chmod.

sudo chown -R $USER:$USER /var/www/#@WEBSITE@#

sudo chmod -R 755 /var/www

Since this is our first website, we will add a simple index.html file to our DocumentRoot.

sudo nano /var/www/#@WEBSITE@#/index.html

If you do not have nano you can install it using apt sudo apt-get install nano but you can use any editor you like.

index.html

<html>
  <body>
    <div>#@WEBSITE@#!</div>
  </body>
</html>

In order to activate apache2 sites we need to add a .conf file to the sites-available directory. We can make a copy of the default .conf file and rename it using the following command.

sudo cp /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/#@WEBSITE@#.conf

Before we can activate the .conf file we need to amend some variables, open the file using nano.

sudo nano /etc/apache2/sites-available/#@WEBSITE@#.conf

    ServerAdmin admin@#@WEBSITE@#
    ServerName #@WEBSITE@#
    ServerAlias www.#@WEBSITE@#
    DocumentRoot /var/www/#@WEBSITE@#

The ServerName, ServerAlias, and DocumentRoot variables are the most important. Apply changes and hit CTRL+X enter Y and hit return. The file is saved and we can activate the site using a2ensite.

sudo a2ensite #@WEBSITE@#.conf

Remove the default .conf using the a2dissite command.

sudo a2dissite 000-default.conf

Restart apache2 and the Virtual Host is running!

sudo systemctl restart apache2

Browse to #@WEBSITE@# and lo and behold, we have a Virtual Host.

Quickly adding new Virtual Hosts

We have now setup apache2 and added our first Virtual Host, the next one will be much easier!

Second website:

Generating creation scripts

If you have a bunch of Virtual Hosts to create, it would be much easier to generate the scripts. You can write these scripts yourself using bash, or you can use a small utility I have created. Click here to open the ‘VHGenerator’. I plan to create an article detailing the process, for now the Github repo will have to do.

Quick commands

Coming ASAP.

AUTOCSV2SSIS

Wed, 25 Nov 2015 12:39:50 +0000

The setting

During the Minor Business Intelligence I worked for a company which has a number of testing machines with flat file logging enabled. These files are in CSV format.

The problem

When the operator spots a problem on the realtime logging system an employee transfers the logfiles with a USB stick to the office environment. In the office environment (Excel) they create graphs to analyze the problem. This is a very costly procedure which our project group was tasked to remedy.

We chose to use SSIS to load the data into a Data Vault and use Qlikview to create the analysis. Seems great right? However, there are still a couple of steps here that can get automated. This script tackles the problem of manually loading up the CSV files in SSIS.

The solution

Because the files are dropped at undetermined times I created a script that monitors a directory for new files. The PowerShell script:

Registers an ObjectEvent (FileSystemWatcher)
User drops one or more CSV files into the directory
The FileSystemWatcher uses a timer to establish whether or not we have a record of all the added files. It does this by turning off the Timer at the start of the function and enabling it at the end. By this logic once the timer runs out we have a record of all the added files. Each ObjectEvent adds the name of the file to an Array.
When the Timer runs out, copy each file to the SSIS working directory and rename it to the name given in the SSIS package for the Flat File Source. This name is taken from the CSV file.
When all files are copied and renamed we call the SSIS package using DTEXEC
Check if SSIS package executed succesfully, relay this information to the user
Remove all files from the SSIS working directory
Clear the Array
Done. Waits for new files to be dropped into the monitoring folder

The code

The code might change before the article changes so keep up with the current version on Github. Or just download the zip.

$package = "\path\to\Package.dtsx"

$SSISWorkingDirectory = "\path\to\SSISWorkingDirectory"
$MonitoringDirectory = '\path\to\MonitoringDirectory'

$filter = '*.*'  # Wildcard filter                        
$fsw = New-Object IO.FileSystemWatcher $MonitoringDirectory, $filter -Property @{IncludeSubdirectories = $false;NotifyFilter = [IO.NotifyFilters]'FileName, LastWrite'} 

$timer = New-Object timers.timer
$timer.Interval = 5000

$global:files=@()

Write-Host "Starting script" -fore green

function Run-SSIS-Package {
    dtexec /f $package # Execute SSIS Package
    Write-Host $LASTEXITCODE
    if($LASTEXITCODE -eq 0) {
        Write-Host 'Executed SSIS package succesfully. Time for cleanup...' -fore green

        Write-Host 'Removing files from SSIS Staging folder' -fore green
        Remove-Item $SSISWorkingDirectory\*
        
        Write-Host 'Clearing files array' -fore green
        $global:files = @()
    } else { # add error handling for the other error codes
        Write-Host "Encountered an error ('$LASTEXITCODE') while executing SSIS package.. " -fore red
        Write-Host 'Removing files from SSIS Staging folder'
        Remove-Item $SSISWorkingDirectory\*
        
        Write-Host 'Clearing files array'
        $global:files = @()
    }
}

function Get-Machine-Name($logfilename) {

    Write-Host $MonitoringDirectory\$logfilename -foreground Green
    $data = Import-CSV $MonitoringDirectory\$logfilename -Delimiter ';'
    $machinename = $data[0].Machine # Assume a file is for one machine, so only need first element

    return $machinename
}

Register-ObjectEvent -InputObject $timer -EventName Elapsed -SourceIdentifier Timer.Output -Action {
    $timer.Enabled = $False
    foreach ($name in $global:files) {
        $machinename = Get-Machine-Name($name)
        Write-Host 'Machinename: ' $machinename #change to $extractedname for clarity
        Write-Host 'Copying ' $name 'to SSIS location and renaming'
        Copy-Item $MonitoringDirectory\$name -Destination $SSISWorkingDirectory\$machinename'.csv'
    }
    Write-Host 'Start SSIS package now' -fore green
    Run-SSIS-Package
}

Register-ObjectEvent $fsw Created -SourceIdentifier FileCreated -Action { 
    $timer.Enabled = $False

    $name = $Event.SourceEventArgs.Name # change to $filename for clarity
    $timeStamp = $Event.TimeGenerated 

    Write-Host "Detected new file '$name' on $timeStamp" -fore green 

    Write-Host 'File: '$MonitoringDirectory\$name -foreground Green    
    
    $global:files+=$name
    $timer.Enabled = $True
} 

A Practical Introduction to Git

Sun, 28 Jun 2015 01:39:50 +0000

So you have heard about Git, but you still need to start somewhere? Let’s do that together by building a simple portfolio website. We will be using the Ruby gem Jekyll which takes Markdown and generates the static HTML pages which can be hosted on Github Pages for free.

You can use whatever operating system you like but I’ll be noting the instructions down for the big 3: Ubuntu, OSX and Windows.

If you and your computer are up for it and you don’t already run Linux or OSX, consider running a development machine with VirtualBox and Ubuntu 14.04.2 LTS or dual-booting.

If you want you can try out Portable Jekyll for Windows which allegedly contains all the things you need to run it on Windows. Or check out this website for a Windows tutorial. After you’ve got Jekyll installed you can come back and join us for the Git part.

Installing Git
- Ubuntu
- OSX
- Windows
Setting up Git
Installing Ruby
- Ubuntu & OSX
- Windows
Installing Jekyll
- Ubuntu & OSX & Windows
What’s Git again?
- [Video] A Quick Introduction to the Git VCS
Github
Putting Jekyll and Git to use
- Ubuntu sidenote (nodejs)
- Creating the website
Connect Github
Linking a Domain

Installing Git

To install Git you can use the package manager or the website. For Debian derivatives that is apt, OSX uses homebrew.

Ubuntu

Open the terminal and install git

sudo apt-get install git

OSX

Open the terminal and install git

brew install git

Windows

Download the installer from the git-scm website.

Setting up Git

We will only need to setup Git on our machine once. Use the git config command to set your name and email. These are the credentials that will be used to commit to github, make sure you use your primary Github email and correct name.

Open either your terminal or Git Bash if you’re on Windows.

user.name sets your name:

git config –global user.name “Midas van Oene”

user.email sets your email:

git config –global user.email “Midas.van.Oene@gmail.com”

And we’re all done here.

Installing Ruby

Jekyll is a Ruby gem. If you don’t have Ruby yet, we will use the Ruby Version Manager to install it.

Ubuntu & OSX

Use the terminal to add the key

gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3

If you do not have cURL

sudo apt-get install curl

Paste this in the terminal to install RVM with ruby

\curl -sSL https://get.rvm.io | bash -s stable

The RVM installer will remind you that you need to run the source command before being able to use RVM and Ruby. Replace username with your own. It’s best to just copy the outputted text.

source /home/username/.rvm/scripts/rvm

After that command worked its magic, check if RVM is installed.

rvm --version

And you will get back something like:

"rvm 1.26.11 (master) by Wayne E. Seguin <wayneeseguin@gmail.com>, Michal Papis <mpapis@gmail.com> [https://rvm.io/]"

Install the latest:

rvm install ruby --latest

Windows

Windows users can install the RubyInstaller and the Ruby DevKit from this page in order to use gems.

Installing Jekyll

To install Jekyll we will use a nifty Ruby feature, the RubyGems. RubyGems is a package manager for the Ruby programming language that provides a standard format for distributing Ruby programs and libraries (in a self-contained format called a “gem”). You can find more about gems here.

I added the ‘- -no-rdoc’ flag because of an install error, if you really want it you can install it manually later. It’s not required.

Ubuntu & OSX & Windows

gem install jekyll --no-rdoc

What’s Git again?

Git is a Version Control System, version control is a system that records changes to a file or set of files over time so that you can recall specific versions later.

Git is not Github. Git is the protocol and Github is one of many sites where you can host remotely. The reason we’re going with Github and not something like Bitbucket is the free hosting of Jekyll pages.

Here are a couple commands to give you an idea and reference. We will run through them as well when we upload the Jekyll site to our github. Oh and Here’s a handy Git cheatsheet from Atlassian.

Add all the files in the current directory to the staging area.

git add .

Commit the added files and add a message

git commit -m "your message"

Push the commited changes to your remote repositories’ master branch

git push -u origin master

[Video] A Quick Introduction to the Git VCS

Github

If you do not have a github account yet, go to github.com and create one.

Make sure you pay attention to your organization name as that will also be your sites name. For example, my organization name is MidasVO thus my github URL is https://github.com/MidasVO and my eventual website name will be MidasVO.github.io.

Go to the top right corner and click on create a new repository:

The name of your repository has to be username.github.io otherwise it will not work. You can also add a .gitignore file with the name Jekyll. The files and folders marked in the .gitignore file will not be uploaded to your repository. I’ll be using my own name and repository in the examples, you will simply need to substitute my name with your own to make those commands work. I think that will be more clear than constantly saying username.github.io.

Here’s an example:

The default .gitignore for Jekyll consists of

_site/
.sass-cache/

Both are folders we don’t need. _site/ carries the generated content, which Github Pages will regenerate somewhere else so it’s just clutter. And .sass-cache is not useful either.

Putting Jekyll and Git to use

We’ve arrived at the fun part; open a terminal in the folder where your projects reside. If you want the same setup as me:

Change Directory to your home folder

cd ~

Create a Projects folder

sudo mkdir Projects

Change Directory to Projects folder

cd Projects

Ubuntu sidenote (nodejs)

In order for Jekyll to run you need nodejs. Update the package list and install

sudo apt-get update && sudo apt-get install nodejs -y

Creating the website

To create a new Jekyll website all we need to do is enter (in your Projects folder)

jekyll new username.github.io

If this succeeded we can run the website locally to edit and test. Go into your website directory

cd username.github.io

And start the Jekyll server

jekyll s

Open your browser and browse to localhost:4000

Welcome to Jekyll!

What you are seeing now when you browse to your locahosts’ port 4000 is the default installation of Jekyll. A short explanation is in order.

The following are all the files generated by Jekyll:

about.md

_config.yml

css

feed.xml

_includes

index.html

_layouts

_posts

_sass

Connect Github

Configure our Name and Email

git config --global user.name "Midas van Oene"
git config --global user.email "midas.van.oene@gmail.com"

To be able to use our Git repository we need to clone it and work from the cloned directory

cd Projects

git clone https://github.com/username/username.github.io.git

Linking a Domain

If visit go to midasvo.github.io you’ll be immediately redirected to midasvo.nl. This is a result of the CNAME file and DNS records. If you have registered a Top-Level Domain Name or created a subdomain, you will need to create 2 A records and a CNAME record. You can do this in your registrars control panel.

DNS

I’m registered at transip and my DNS records look like this:

The two A records are a requisite of Github Pages in order for them to route to your page properly. The CNAME record should be username.github.io. for everthing to work. Don’t forget naming them @ and www. The TXT record is for Google analytics.

CNAME file

Create a new file in the root of your Jekyll application named CNAME. The only content this file has is the domain name associated with your page. You can only have one domain name in this file. Use the version without the www. because we’ve already dealt with that on the registrars part.

In my case my /midasvo.github.io/CNAME file contains this:

midasvo.nl

Add the file to your repository

git add .	
git commit -m "Added CNAME file"
git push -u origin master

DNS Propegation

It is going to take a while before visiting your domain will show the correct page. This is because only every so many hours the world’s DNS servers get updated with the new listings.

Basically, when you go to http://midasvo.nl your web-browser asks your DNS server where to find midasvo.nl. The DNS server will respond with the correct IP address and your browser will be able to download the website and display it.

It can take up to 24 hours to for the DNS server to propegate fully.

HUSACCT

Sun, 28 Jun 2015 01:39:50 +0000

I worked on HUSACCT with a group during an 8 week project in the semester Object Oriented Software Engineering. HUSACCT is a Software Architecture Checking Tool, which in short, analyzes source code and compares it to the intended architecture.

Since the application was already very far in development we were given the task of implementing 2 design patterns (MVC, BlackBoard) plus the possibility of adding more patterns and altering existing ones.

The code was developed via Stash on a school server, I do not have the code available.

o Java, Spring Roo, Glassfish o Research into SOAP o Functional design and technical design documents o Version control o UML (class, sequence, domain)

Test App

Mon, 01 Jun 2015 01:39:50 +0000

Type: I worked on this project individually during the CRIA course.

Description

I created a Single Page Application with the MEAN stack with the purpose of testing RESTful API’s. I used the mean.js framework to kickstart my project because I the vertical structure is very intuitive. There are still plenty of things missing and I intend to remedy them when I have the time to do so.

The app is based on the popular Chrome extension Postman, with the major difference being scenarios.

A request is a HTTP ‘GET’ or ‘POST’ request to a URL with optional parameters. What you get back is the Status Code, headers, and the response.

A test is an assertion coupled with a request. Say for instance you want to check if the URL returns the ‘OK’ Status Code the assertion will be ‘statusCode===200’.

A scenario is a list of tests that have to be run consecutively, optionally with the output of the first test being the input for the next request and so on.

How

The core of the application is making requests and handling the response. For the purpose I used the q promise library and request. There are still some remnants in the code from when I tried to do requests with plain JS, but I found the request library to be much smoother to work with.

Midas van Oene

Two player IDs in an if statement

The setup

The research was thorough. The category error was still there.

Turning biographies into magic numbers

The scoring engine is 85 lines of literals

100k Monte Carlo runs and the Linssen problem

It had to run on a toaster

Adding Japanese for a single striker

What I’d do differently

Git cheat sheet - most used commands

Git Cheat sheet

Customization

Starter commands

Adding an existing remote to an existing project directory

App: HTML / CSS / JS starters boilerplates

Bash

Useful Bash!

Requirements

Customization

Basics

How to move around

How to get your current directory

Creating a script

The script

Making the script executable

Running the script

Making aliases

Using the alias

Using command-line parameters

Making the alias permanent

A better way!

Executing aliases periodically

CRON

Setting up Letsencrypt on Ubuntu 16.04

Customization

Intro

Quick-guide

Apache2 Virtual Hosts with Ubuntu 16.04

Intro

Customization

Installation & configuration

index.html

Quickly adding new Virtual Hosts

Generating creation scripts

Quick commands

AUTOCSV2SSIS

The setting

The problem

The solution

The code

A Practical Introduction to Git

Installing Git

Ubuntu

OSX

Windows

Setting up Git

Installing Ruby

Ubuntu & OSX

Windows

Installing Jekyll

Ubuntu & OSX & Windows

What’s Git again?

[Video] A Quick Introduction to the Git VCS

Github

Putting Jekyll and Git to use

Ubuntu sidenote (nodejs)

Creating the website

Connect Github

Linking a Domain

DNS

CNAME file

DNS Propegation

HUSACCT

Test App

Description

How

Creating a request

Creating a test

Creating a scenario