After creating the keypair it should appear in your EC2 key pairs listing. The
keystuff.json file will contain the RSA private key you will need to use
to connect to any instances you create with the keypair, as well as the name of
the key and its fingerprint.

If you're using GitLab.com for hosting your repositories, you may have encountered
a strange problem wherein your newly-created repository's dashboard doesn't update.

That is, when you git push your changes to the repository, the interface still
looks like a newly-created repository, and neither your files nor your commits
are visible in the web UI. This is weird because the remote repository works in
all other respects. You can push code up to it, clone it, etc. You just can't see
it on the GitLab website.

I've seen this happen a couple of times, and so far I've found that the quick fix is to
run Housekeeping on the repository from the Edit Project page.

Housekeeping can take a couple of minutes but most of the time it works and you
can see your repository's files and commit history after running it. If it
doesn't work, you have to delete the repository in GitLab and re-create it,
pushing your code up again.

CentOS 7 ships with python 2.7.5 by default. We have some software that requires 2.7.11. It's generally a bad idea to clobber your system python, since other system-supplied software may rely on it being a particular version.

Our strategy for running 2.7.11 alongside the system python is to build it from source, then create virtualenvs that will run our software.

Now the caller is poluted with literal strings like 'success', 'code' and 'status'. These can be hell to debug, specially if you happen to misspell one of them in your code. Even if you're using an awesome IDE like PyCharm.

An altenative to defining these ad-hoc dict structures is to use namedtuple from the collections package.

This is almost as simple as our first example, and is free of string literals. And if you're using PyCharm, you can take advantage of the code completion which will know about the attributes of your new namedtuple class:

So if your code is littered with string literals as keys for return values from methods that return dict, consider having them return a namedtuple instead.

In the book, Peng and co-author Elizabeth Matsui walk us through the different activites of data analysis, from formulating questions, basic exploratory data analysis to get a rough feel for the data, to modelling the data with familiar distributions through to basic inference and prediction.

Using R and the datasets that come bundled with it, Peng and Matsui demonstrate how each activity is actually an iterative process itself. At each stage, it's important to evaluate what you already know (or think you know) and revise your expectations based on the data.