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.

I’m a Vim user to my core, but I still use org-mode with this plugin (and Orgzly on Android) because of how useful it is.

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

• I really, really dislike having two MNF games at the same time. The entire point of primetime games is that everyone can watch and talk about the same game.
• Although both games were decided in the final two minutes, overall, these two games were amazingly bad (in the sense of quality of play, not entertainment value).
• It’s always great to see Deshaun Watson lose. I pirated this game even though I have the necessary subscriptions to watch legally along with a TV antenna because I refuse to give an official view to any game the Browns are playing in.

McLaughlin with his debut touchdown! Good to see a faster pace from the Broncos this week.

This is fascinating. It answers so many questions I never knew I had!

This is exactly right. However, something that I’ve found frustrating is that in many projects (at least the ones that I’m interested in), it feels like there’s a secret roadmap that’s not documented anywhere outside of the maintainer’s head(s). You can scour the wiki, watch the IRC channel and mailing lists, and read through the issue discussions, and you still won’t have a good sense of what they want done next or if the change you want to make is incompatible with some big planned rewrite. I know the answer is to just ask—and I’ve done that more and more recently—but that can be a big hurdle if you’re just getting started.

I’m trying to build a community for a project right now, and this is something I’m very aware of. I’m trying to report on what I’m working on and planning in the project chat so that if someone else comes along, hopefully they’ll (a) understand the current status and (b) feel comfortable asking about the overall vision.