Skip to content

Instantly share code, notes, and snippets.

View svengerlach's full-sized avatar

Sven Gerlach svengerlach

8 followers · 0 following
  • Vorwerk Digital
  • Bochum, Germany
View GitHub Profile
@svengerlach
svengerlach / gist:069a8998ded975808787c7f8428ad55a
Created October 15, 2016 07:45
refresh
# im <head> von seite1.html
<meta http-equiv="refresh" content="60; URL=/seite2.html">
# im <head> von seite2.html
<meta http-equiv="refresh" content="60; URL=/seite3.html">
# im <head> von seite3.html
<meta http-equiv="refresh" content="60; URL=/seite1.html">
@svengerlach
svengerlach / prepare-pwned-passwords.sh
Last active December 29, 2017 08:27
Prepare Troy Hunt's >300 million password list for a binary search operation
#!/bin/bash
# this script helps to prepare Troy Hunt's password list for a binary search operation
#
# see https://haveibeenpwned.com/Passwords for more informations
#
# place this file into your home directory, e.g. called prepare-pwned-passwords.sh and
# execute it using bash:
#
# nohup bash prepare-pwned-passwords.sh 1>prepare-pwned-passwords.log 2>prepare-pwned-passwords.err &
@svengerlach
svengerlach / Vagrantfile
Created May 7, 2018 07:52 — forked from gabrielelana/Vagrantfile
How to create a VirtualBox machine with encrypted storage with Vagrant
# -*- mode: ruby -*-
# vi: set ft=ruby :
PASSWORD_PATH = ".password"
PASSWORD_ID_PATH = ".password_id"
# Make sure to have installed vagrant-triggers plugin
# > vagrant plugin install vagrant-triggers
# After the first `vagrant up` stop the VM and execute the following steps
@svengerlach
svengerlach / what-hiring-should-look-like.md
Created August 15, 2020 19:16 — forked from getify/what-hiring-should-look-like.md

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.