lukebaker

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?

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.

https://help.github.com/articles/troubleshooting-custom-doma...

That link didn't work for me but this did: https://www.youtube.com/watch?v=S8HXkEnA48g

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.

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.

Would using HTTPS prevent the VPN and various proxies from messing with the traffic as described in the article?

Does this provide traffic details for GitHub Pages associated with the repo?

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.

http://prose.io/about.html

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).

[1] https://forums.aws.amazon.com/message.jspa?messageID=374065#...

I'm a fan of PasswordMaker. Based on the domain name of the site, a master password (you could still use a tier system where sites of different value have a different master password), and other settings a password gets generated. Each site gets its own password and your passwords are only stored on the target site (i.e., there's no central password manager that stores all your passwords). There are browser extensions that make it easier to use and if you're not on your own browser there's an online JS version available for generating your passwords.

Files in the Google Docs format do not count against your quota. Files not in Google Docs format also support revisions, but each revision counts against your quota.

Every detail points to them providing an local client for Google Docs. Google Docs has: 1GB free, ability to upload arbitrary files, web preview of a variety of file types (videos, music, documents, etc.), an API, Google Apps integration.

The compile happens in the setup of the benchmark. So the actual benchmark is testing the rendering speed of the compiled templates.

A brainstorming meeting is not a place to offer harsh critique. I think it's okay to offer variations of an idea during a brainstorm, but not outright critique. This is a situation where you want creativity to flow. After the brainstorming, everyone needs to think critically about the ideas and have a time for debate when deciding what to execute.

So to answer your question, it depends what mode you are in. Are you still in the idea gathering phase? Then let bad ideas in. If not, then it's time for critique.

(I base these off of a talk I heard by Craig McNair Wilson, a Disney Imagineer. Here are some notes someone else took on the same topic.)

http://www.theparagon.org/archives/2006/02/03/brainstorming_...

One technique that I've used in the past is to print the PDF to file as SVG, edit in Inkscape, then print the SVG to file as PDF.

I think I used Evince to open the PDF and print to SVG.

According to the keynote at Google I/O, Google has been working with Netflix to get it working on Chromebooks. I would hope this means inside the Chrome browser everywhere.

I do some work with a Bible search site that saw its traffic drop dramatically right around the time that Google implemented some of these changes. My conjecture is that the site was penalized because it had similar content (the Bible itself) as other sites.

Looks like they're saying it was an accident and will return to its rightful place.

http://twitter.com/#!/googlereader/status/28595016557400064