Sung sungwoncho

-- Firstly, remove PRIMARY KEY attribute of former PRIMARY KEY
ALTER TABLE <table_name> DROP CONSTRAINT <table_name>_pkey;

-- Then change column name of  your PRIMARY KEY and PRIMARY KEY candidates properly.
ALTER TABLE <table_name> RENAME COLUMN <primary_key_candidate> TO id;

In Rails 3

NOTE: This post now lives (and kept up to date) on my blog: http://hakunin.com/rails3-load-paths

If you add a dir directly under app/

Do nothing. All files in this dir are eager loaded in production and lazy loaded in development by default.

If you add a dir under app/something/

Thoughts and Rationale

This isn't a comprehensive language design, it's just ideas for syntactical constructs I'd really like to see some day. It'd probably be some kind of object/functional hybrid a la Scala - I really like the recent trend of "post-functional" languages that take a lot of ideas/influence from functional programming, but aren't fascist about it, or so scary that only math Ph.Ds can learn them. The idea is to fuse OOP and FP into a language which gives you a high level of expressiveness and power, but is actually useable for Getting Real Things Done.

Configure Postgres

Update pg_hba.conf (most likely in /etc/postgresql/9.4/main) with -
- host all all 0.0.0.0/0 trust
Update postgresql.conf to use listen_addresses = '*'
Be sure to sudo service postgresql restart

Configure Vagrant

The Ultimate Unit Testing Cheat-sheet

Sinon Chai
Chai
Sinon

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

	environment = process.env.NODE_ENV \|\| "development";

	var settings = {
	development: {
	public: {},
	private: {}
	},
	staging: {
	public: {},
	private: {}

	test.isFalse(v, msg)
	test.isTrue(v, msg)
	test.equal(actual, expected, message, not)
	test.length(obj, len)
	test.include(s, v)
	test.isNaN(v, msg)
	test.isUndefined(v, msg)
	test.isNotNull
	test.isNull
	test.throws(func)

	#!/bin/sh

	git filter-branch --env-filter '

	OLD_EMAIL="your-old-email@example.com"
	CORRECT_NAME="Your Correct Name"
	CORRECT_EMAIL="your-correct-email@example.com"

	if [ "$GIT_COMMITTER_EMAIL" = "$OLD_EMAIL" ]
	then

	# first:
	lsbom -f -l -s -pf /var/db/receipts/org.nodejs.pkg.bom \| while read f; do sudo rm /usr/local/${f}; done
	sudo rm -rf /usr/local/lib/node /usr/local/lib/node_modules /var/db/receipts/org.nodejs.*

	# To recap, the best way (I've found) to completely uninstall node + npm is to do the following:

	# go to /usr/local/lib and delete any node and node_modules
	cd /usr/local/lib
	sudo rm -rf node*