create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
# Vagrant Cheats | |
# =========================== | |
alias vup="vagrant up" | |
alias vh="vagrant halt" | |
alias vs="vagrant suspend" | |
alias vr="vagrant resume" | |
alias vrld="vagrant reload" | |
alias vssh="vagrant ssh" | |
alias vstat="vagrant status" |
create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
This post examines the features of [R Markdown](http://www.rstudio.org/docs/authoring/using_markdown) | |
using [knitr](http://yihui.name/knitr/) in Rstudio 0.96. | |
This combination of tools provides an exciting improvement in usability for | |
[reproducible analysis](http://stats.stackexchange.com/a/15006/183). | |
Specifically, this post | |
(1) discusses getting started with R Markdown and `knitr` in Rstudio 0.96; | |
(2) provides a basic example of producing console output and plots using R Markdown; | |
(3) highlights several code chunk options such as caching and controlling how input and output is displayed; | |
(4) demonstrates use of standard Markdown notation as well as the extended features of formulas and tables; and | |
(5) discusses the implications of R Markdown. |
I haven't set up an install guide for the latest ubuntu release, largely because the last set of instructions worked pretty closely with the latest and greatest Ubuntu, 12.04 Precise Pangolin, however when installing today, I found that there were enough differences in the way that I configure my setup to justify an update, so here it goes. Yes, I'm late to the party, but a quick google search didn't find anything that I felt was as complete for my requirements as my previous install guides, so here I go.
As always with my install guides, I have included here is just about everything you'll need (and then some) to get started with ruby on rails development with Ubuntu 12.04 as a platform. These are my settings and preferences, and this is certainly not the only way of doing things, so keep that in mind.
sudo apt-get update && sudo apt-get upgrade
<?php | |
/** | |
* Copyright (c) 2007, Roger Veciana | |
* All rights reserved. | |
* | |
* Redistribution and use in source and binary forms, with or without | |
* modification, are permitted provided that the following conditions are met: | |
* | |
* Redistributions of source code must retain the above copyright notice, this |
#!/usr/bin/env python | |
# encoding: utf-8 | |
from selenium import webdriver | |
import unittest | |
import nose | |
from nose.plugins.multiprocess import MultiProcess | |
import new | |
import json | |
import httplib |
<?xml version="1.0" encoding="UTF-8"?> | |
<resources> | |
<!-- Totally "960 Colors" | |
Author : VenomVendor | |
Refer : http://stackoverflow.com/q/3769762/1008278 | |
Reference : http://www.computerhope.com/htmcolor.htm , http://www.color-hex.com/color-names.html | |
--> | |
<!-- Colors arranged from A -Z --> | |
<color name="air_force_blue">#5D8AA8</color> |
This chapter is about defensive coding practices, both against users of your software and against yourself. Pragmatic Programmers, after all, understand that everyone makes mistakes, even themselves.
This confused the shit out of me. I wasn't entirely sure what the difference was between a contract and a unit test.
Contracts are introduced in the context of employment contracts. That is, before any work is done, the responsibilities of both parties are defined, as well as the consequences of failing. Contracts in programming are similar. As I mentioned before, I wasn't able to make a strong distinction between contracts and unit tests (given some condition, when some event, then this should happen, though I may be confusing this with [BDD][bdd]). It's all a bit jumbled in my head.