Patrick Wieschollek PatWie

NB: This document describles a 'Old-School' way of using Yubikey with SSH

Modern OpenSSH has native support for FIDO Authentication. Its much simpler and should also be more stable with less moving parts. OpenSSH also now has support for signing arbitary files witch can be used as replacement of gnupg. Git also supports signing commits/tags with ssh keys.

Pros of FIDO

Simpler stack / less moving parts
Works directly with ssh, ssh-add and ssh-keygen on most computers
Simpler
Private key can never leave the FIDO device

Cons of FIDO

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

Effective Modern CMake

Getting Started

For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.

After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft

Sublime Text 2 - Useful Shortcuts

Tested in Mac OS X: super == command

Open/Goto

super+t: go to file
super+ctrl+p: go to project
super+r: go to methods

	#!/usr/bin/env python

	#
	# Usage: python extract_scene.py -p [filename] [classname]
	# eg: python extract_scene.py -p examples.py DrawCircle
	#

	import math
	import numpy as np

	# [<tag>] (If applied, this commit will...) <subject> (Max 72 char)
	# \|<---- Preferably using up to 50 chars --->\|<------------------->\|
	# Example:
	# [feat] Implement automated commit messages

	# (Optional) Explain why this change is being made
	# \|<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->\|

	# (Optional) Provide links or keys to any relevant tickets, articles or other resources
	# Example: Github issue #23

	#!/bin/bash
	# Patrick Wieschollek

	# =============================================================
	# UPDATE SOURCE
	# =============================================================
	git checkout -- .
	git pull origin master

	package main

	import (
	"encoding/json"
	"fmt"
	"net/http"
	)

	type test_struct struct {
	Test string

	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
	<plist version="1.0">
	<dict>
	<key>name</key>
	<string>Indentation Rules</string>
	<key>scope</key>
	<string>text.tex, sources.bib</string>
	<key>settings</key>
	<dict>

	#include <stdlib.h>
	#include <stdio.h>
	#include <glpk.h>

	/*
	Maximize
	obj: x1 + 2 x2 + 3 x3 + x4
	Subject To
	c1: - x1 + x2 + x3 + 10 x4 <= 20
	c2: x1 - 3 x2 + x3 <= 30