What happens prior to step #1 from a candidate's perspective? How do candidates express interest and do 100% of the folks who express interest get a call?
The way this "scaled" at Matasano was that we gradually got smarter with our outreach, so that instead of constantly circulating wide appeals to the whole developer community, we staged events (Cryptopals, Microcorruption) that targeted a specific community of enthusiasts with whom those phone calls were likely to be valuable to us.
But in the beginning, we just posted on the HN hiring threads; it's a fine starting place. That's what we're doing now. I'll do a couple phone calls a day at this point.
I was having trouble with that yesterday, as well. On the settings page for my repository, I switched from www.example.com to example.com and then back again to www.example.com. I noticed it is now working for my site, though I don't know for sure that my changes fixed it.
It sounds like you're asking some of the same questions that David Nolen is asking (and answering) with Om Next. If you haven't been following that process, you might find it informative. You can find some details about Om Next on the wiki https://github.com/omcljs/om/wiki and several talks by David are available YouTube.
Awesome! Thanks for the tip. I'll be checking that out. I've just recently started to dive into functional programming. Redux turned me on to the Elm Architecture and I've really started to think about programming differently ever since.
I use Ubuntu on my laptop. I've found that I typically don't need the latest and greatest versions of various software, and have been happy with 12.04 LTS. I suspect that my next version will be 16.04 LTS. I value the Long Term Support releases because I can stick with the same system for several years and still get security updates. At this point in my life / career, I'm not nearly as interested in with tinkering and tweaking things and would rather have something that generally works and is stable.
I've toyed with the idea of going with CentOS on a desktop, but I think that release cycle may be a little too slow. Ubuntu's LTS every two years gives me the opportunity to upgrade sooner if there's a compelling reason (e.g., Docker support).
I do web development at a consultancy (lots of different projects in a variety of languages / environments) and have in the past been able to do a pretty decent job isolating different client applications while running them locally. However, these days I'm moving more to Vagrant for some of the heavier applications and likely to Docker for some of the lighter ones.
I like my Lenovo X1 Carbon. It's nice and light but still quite capable for my needs (web development). Everything just worked for me, with the exception of an external display which I spent about 20 seconds trying to get to work. It could easily have been user error given my lack of experience with external displays.
I've had the opportunity to play with X1 Carbon not too long ago and found it to be pretty damn impressive. Haven't used it with linux, but if I was to get a high-end laptop, I would definitely get an X1. Nice to see that it's also linux-capable.
I'm using one since over a year, can't recommend. No proper support for the docking station (which goes via USB3 and doesn't support video output), power plug wears out really fast and causes ubuntu to reboot quite often when plugging it due to some short circuiting, disk is really slow for an ssd and working with vagrant sucks due to it, 802.11n driver doesn't work properly, etc etc.
It looks well, feels well, but it's not suitable for devs. I'm a long time lenovo x200 line user, and the X1 is really bad compared to those models.
By firewall, he would have to be talking about a client side firewall running on the machine making the request. Something that sees the request before it actually goes out on the wire.
If you keep your Jekyll site on GitHub, you can edit your site in your browser with Prose. I imagine you use GitHub for its Jekyll building and mirror the built site elsewhere.
According to this post[1] they charge based on how long it takes them to retrieve the data. The hourly retrieval rate would be the amount of data you requested divided by how long it takes them to retrieve it (3.5 - 4.5 hours).
If it takes them 4 hours to retrieve your 3TB, then your peak hourly retrieval rate would be 768GB / hour (3072 GB / 4 hours). Your billable hourly retrieval rate would be 768GB - 1.28GB (3072 * .05 / 30 / 4 hours).
Total retrieval fee: 766.72 * 720 * .01 = $5520.38 (~180x your monthly storage fee)
The pricing appears to not be optimized for retrieving all your data in one fell swoop. This particular example appears to be a worst case scenario for restoration because you haven't split up your data into multiple archives (doing so would allow you to reduce your peak hourly retrieval by spacing out your requests for each archive) and you want to restore all your data (the free 5% of your data stored doesn't help as much when you want to restore all your data).
A spokesperson for AWS confirmed this for me for an article [1] I wrote for Wired: "For a single request the billable peak rate is the size of the archive, divided by four hours, minus the pro-rated 5% free tier."
