Hampus Persson hmps

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.

Kontrakt

Senast uppdaterad: 2013-02-20

Mellan mig, [MITT NAMN] och er [KUNDENS NAMN], [KUNDENS ADRESS]

Sammanfattning:

Jag kommer alltid att göra mitt absolut yttersta för att tillfredsställa era önskemål och behov, men det är ändå för allas bästa att ha några rader nedskrivna om vad som är vad, vem som ska göra vad och vad som händer om något inte skulle gå som planerat. I det här kontraktet finns inga komplicerade juridiska termer eller långa stycken av oläslig text och jag har ingen önskan att få er att skriva på något som ni kan komma att ångra i framtiden. Detta är helt enkelt för bägge parters säkerhet, nu och i framtiden.

	'use strict';
	/globals ebml /

	if ( !window.ebml ) window.ebml = {};

	ebml.EbmlDecoder = function EbmlDecoder( options ) {


	var schema = {
	"80": {

	javascript: (function() {

	var root = $(document.getElementsByTagName('html'));
	var watchers = [];
	var attributes = [];
	var attributes_with_values = [];
	var elements = [];
	var elements_per_attr = [];
	var scopes = [];

	/* http://meyerweb.com/eric/tools/css/reset/
	v2.0 \| 20110126
	License: none (public domain)
	*/

	html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video {
	margin: 0;
	padding: 0;
	border: 0;
	font-size: 100%;

	<?php
	function is_blog () {
	global $post;
	$posttype = get_post_type($post );
	return ( ((is_archive()) \|\| (is_author()) \|\| (is_category()) \|\| (is_home()) \|\| (is_single()) \|\| (is_tag())) && ( $posttype == 'post') ) ? true : false ;
	}
	?>

	<?php
	// Usage

	/**
	* This gist demonstrates how to properly load jQuery within the context of WordPress-targeted JavaScript so that you don't
	* have to worry about using things such as `noConflict` or creating your own reference to the jQuery function.
	*
	* @version 1.0
	*/
	(function( $ ) {
	"use strict";

	$(function() {