nrninsane

What are tests for? Tests are for declaring how implementations should behave.

Should we then test that which is declared? Yes.

But then you're declaring how a declaration should behave, no? Only if you test the declaration by itself. If you test the integration of the declaration, then you're testing an implementation.

Simple, yet complicated code

Code has many forms.

Many are hard to follow. Some are easy to follow. Many change a lot as you go deeper. Some change little as you go deeper.

Many have a form which we consider as ugly.

#Setting up Nginx on Your Local System ###by Keith Rosenberg

##Step 1 - Homebrew The first thing to do, if you're on a Mac, is to install homebrew from http://mxcl.github.io/homebrew/

The command to type into terminal to install homebrew is:

ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

to find where for example ls is defined, use

zsh -ixc : 2>&1 | grep "alias 'ls="

Note: only rebase local branches, NEVER REBASE A REMOTE BRANCH.

create backup to preserve original commit tree

git branch myBackup

get list of commits and their SHA

git --no-pager log --oneline

	{
	"global": {
	"check_for_updates_on_startup": true,
	"show_in_menu_bar": true,
	"show_profile_name_in_menu_bar": false
	},
	"profiles": [
	{
	"complex_modifications": {
	"parameters": {


	// Available variables:
	// - Machine
	// - interpret
	// - assign
	// - send
	// - sendParent
	// - spawn
	// - raise
	// - actions