I had a lot of fun playing John Tiller's Campaign Series by myself and with my buddies. We'd play the turn based, company/battalion level tactical game on a single computer using its unique single-machine play feature. I can still remember the hex tiles, and the catchy background music.
> The infrastructure for background checks and criminal records in India is more or less nonexistent, so I doubt that Lyft would've been able to catch this driver before he committed a crime any more than Uber would've been able to.
Yes, blame it on the system. Never mind that Uber performed NO checks; never mind that the guy's record was revealed shortly after his arrest, indicating that had Uber performed a check they stood a good chance of finding the same out.
While India's police system is not perfect, Uber's attitude is downright arrogant: "it is you natives and your cops who are to blame". The law mandates a background check, you didn't follow the mandate. The least you can do is to own up to that.
A language spec is roughly analogous to the definitions of scientific units of measurement[1]. They among other things, allow us to verify something independently of a specific kind of measuring device.
Nice description. I'd suggest explaining how decorators that accept arguments (i.e. @memcached('some-arg')) work lest it befuddle some beginner. It is not straightforward (the first argument of a decorator is the function being decorated).
I've found that pairing with interviewees on real(ish) problems usually helps to detect useful traits (I am not advocating pair-programing here FYI; rather working with them in front of a machine during the interview). Your mileage may vary.
Some of the things I look for are (in no particular order):
1. Knowing where to look for help when stuck
2. Systematically looking up the man pages/docs/API when stuck as opposed to making multiple wild guesses
3. Indenting code and saving files with proper names (you would be surprised how many people don't intend code even when it spills over 15-20 lines)
4. Instinctive eye for usability - for e.g. parsing command line arguments when appropriate rather than doing it blindly (`if sys.argv[n]: foo elif sys.argv[n-1]: bar`)
5. Inclination to iterate, even during an interview. Many people are happy to produce a working answer and leave it at that. Some iterate and tidy up without being asked to.
In case any of the fabric folks hang out here I'd like to post a suggestion.
local task no longer works with cd. It works well with lcd though. The change log presents lcd as a new feature. It might be worth adding a note under "backward incompatible changes" that existing local tasks running inside a cd context may break (as they did for me).
Thanks for all the memories. RIP John.