Personally, I’d love this system (I immediately thought of some code snippets I’d bring!), but I’m curious how you’d handle candidates without any open source projects or contributions who still have a substantial employment history but are unable to show any code from that because it’s all proprietary.

My biggest (mostly) irrational internet pet peeve is the proliferation of people suggesting “:wq” when “:x” is strictly better.

As someone from southern Colorado, the green chile slopper is the greatest food item ever created. I’ll occasionally try describing how good it is to people not from the area, and this article (in which a self-described skeptic tries it and falls in love) is a handy reference.

Edit to include my favorite quote:

We took our first bite and… holy shit. It was a revelation. I’m not being hyperbolic. It is literally one of the best things I’ve ever put in my face. A slopper is happy food. It’s heartwarming food.

Nim is one of my favorite languages, and has been one of my primary languages in rotation for projects for the last five or so years. I’ve written servers (and web frontends, CLI tools, quick scripts, etc.) with it and am very happy with the results.

It’s hard for me to put into words why I like it so much, but I think it might actually be because it’s such a mishmash of paradigms. If I’m in a functional mood, I can use lots of ideas from functional programming. If I feel like using OOP everywhere, I can do that too. And if I want to mix both together, it’s no problem! Nim kind of feels like the Wild West, and while that’s something I’d dislike in most languages, for whatever reason it works when writing in Nim.