You should check out troposphere (https://github.com/cloudtools/troposphere/) and stacker (https://github.com/remind101/stacker/). I'm a maintainer of both - we try to make CF easier by catching errors earlier, and allowing you to do things like write for loops, in troposphere. stacker tries to take your troposphere templates and tie them together as totally separate stacks.
Same laptop but with the 3200 x 1800 screen. The pre-installed Ubuntu version was so slow; stuttering, major screen tearing, and HDPI font issues everywhere. Basically unusable. However, I updated the BIOS and installed Fedora 22. Had to install proprietary Broadcom WiFi drivers, but GNOME 3 works great with HDPI and the system is way more responsive. Touchscreen is a little useless though :)
That being said, I like the laptop with Fedora and would recommend it.
Yes, all containers are backwards compatible, pretty much to the first version.
In general backwards compatibility is a big deal in the Docker project - breaking changes are taken very seriously and we try to avoid them as much as humanly possible. That applies to the container image format, Dockerfile format, remote API and command-line interface. It's also important to preserve portability across drivers. For example different storage drivers (aufs, btrfs, devicemapper etc) don't affect the format of the images they produce.
Not to mention tell the operator if they are alive at all. It may not be obvious if you see from a few meters away someone who is mostly immobilized by a fallen whatever. For this sort of application, a microphone on a winched cable might be useful (n.b.: make a feature to jettison the cable if it gets stuck!).
Yes, strap a megaphone on here and now you've got a flying telephone for search & rescue as well as a chance for an aerial director to talk with folks in the ground without the need to set up a second comms channel (e.g. RF radios).
As far as Django goes, there hasn't been much tuning in general[0]. The only thing I see them doing is template caching. At the least they should be running 1.6 with persistent DB connections. Beyond that they have a lot of middleware enabled that isn't being used.
If you'd like to apply to SpaceX go through another recruiter. I applied through Ryan a while back. He was unprofessional and kept getting mixed up with the schedule. In the end I did 6+ hours of phone interviews and a 4 hour coding test. I sent in my results and was completely ignored. No feedback, no response to my inquiries. Honestly one of the most insulting things that's ever happed to me.
Go on Linkedin, SpaceX has several other recruiters available.
My apologies for not getting back to you and your candidate experience. This is deeply regrettable and something I would like to apologize for over the phone. Can you please e-mail me when you have a chance? I would like to get more information if possible so I can figure out where I dropped the ball.
