Fernando Blat ferblape

This allows you to use the following video streaming services outside of the US from your Mac without having to use a proxy or VPN, so no big bandwidth issues:

Hulu / HuluPlus
CBS
ABC
MTV
theWB
CW TV
Crackle
NBC

The problem with code examples

Anyone who writes or speaks at conferences about software knows that it's not easy to put together the right code examples. On one side, you want to illustrate just one specific idea or technique, so you try to make your example simple and clear to keep your audience focused. On the other side, if the example is too simple, chances are that it'll fail to justify your point.

This is an issue I come across often in researching resources about big ActiveRecord models. Let's take [this recent post][1] in Victor Savkin's blog. In this writing, the author proposes an alternative way to factor your domain logic in Rails. For that it uses an example which, implemented using a classic Rails way approach, it would have looked like this:

class Order < ActiveRecord::Base
  validates :amount, numericality: true
 has_many :items

Patch for ruby 1.9.3-p385 without backport-gc:

Patch for ruby 1.9.3-p385 with backport-gc:

rbenv instructions https://gist.github.com/samgranieri/4772546

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

Rules for good testing

Look at the following image...

...it shows an object being tested.

You can't see inside the object. All you can do is send it messages. This is an important point to make because we should be "testing the interface, and NOT the implementation" - doing so will allow us to change the implementation without causing our tests to break.

	#!/bin/sh
	#
	# Usage
	# copy_dotfiles user@machine
	#

	FILES=".vim .vimrc .inputrc .gitconfig"
	cd $HOME
	tar cL $FILES \| ssh -C $1 'tar vx'

	-- show running queries (pre 9.2)
	SELECT procpid, age(clock_timestamp(), query_start), usename, current_query
	FROM pg_stat_activity
	WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%'
	ORDER BY query_start desc;

	-- show running queries (9.2)
	SELECT pid, age(clock_timestamp(), query_start), usename, query
	FROM pg_stat_activity
	WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%'

	##### EXEC ###################################################################

	# $ brew install bash-completion
	if [ -f `brew --prefix`/etc/bash_completion ]; then
	. `brew --prefix`/etc/bash_completion
	fi
	# brew git-completion
	export GIT_PS1_SHOWDIRTYSTATE="true"
	export GIT_PS1_SHOWSTASHSTATE="true"
	export GIT_PS1_SHOWUNTRACKEDFILES="true"

	#######################################################################################################################
	# This Gist is some crib notes/tests/practice/whatever for talking to Active Directory via LDAP. The (surprisingly
	# helpful) documentation for Net::LDAP can be found here: http://net-ldap.rubyforge.org/Net/LDAP.html
	#######################################################################################################################

	require 'rubygems'
	require 'net/ldap'

	#######################################################################################################################
	# HELPER/UTILITY METHOD