naw1

My approach has been giving candidates simple real world problems, e.g. extract the URLs from this file given a spec and a description of a few language builtins. I'll throw a few curveballs in depending on how they do but my goal isn't to stump them.

I'm mostly looking to filter out the candidates that flat out can't code or describe their thought process while coding. You'd be surprised how many candidates I've interviewed pass the resume check, get to the interview and can't reason out a problem that could be solved with two for loops and an if statement.

From my initial testing, the result quality leaves a bit to be desired. There are a lot of false positives.

For example, my info is definitely not on mugshotlook.com... And about 2/3 of the results I've clicked on have already been removed by Kanary (full disclosure, on the team, but was a happy customer before) or weren't real to begin with.

I'm a big fan of the Congo theme for Hugo: https://jpanther.github.io/congo/

It's simple to set up and looks pretty great.

Props to the Gitter team, this was the right move, but this is going to be a nightmare for the communities I'm a part of.

(After some growing pains though, this will be great)

Obligatory link to Gary Bernhardt's "The Birth and Death of Javascript": https://www.destroyallsoftware.com/talks/the-birth-and-death...