kerrizor

# MAINTAINABLE CODE ON A LARGE PROJECT!!

# you shouldn't be able to use an object wrongly

# avoid mutability, especially to the outside world and to inputs. work with values
  def accrue_interest(loan, start_date, end_date)
    loan.accrued_interest = (loan.daily_interest_rate * loan.principal) * (start_date - end_date)
  end

  # becomes

kerrizor

Feature: Salary range comparisons
  
AS A      person involved in a recruitment discussion
I WANT    to know whether the candidate's and recruiter's expected salary ranges overlap
SO THAT   I can avoid spending time on negotiations that can't ultimately be satisfied

AS A      person who knows about the phenomenon of price anchoring
I WANT    to approach this question without necessarily being first to name a number
SO THAT   I don't compromise my negotiating position

kerrizor

require 'rical'
require 'open-uri'


url = "[iCal feed URL here]"

open(url) do |ics|
  #RiCal.parse returns an array of RiCalendar objects
  @calendars = RiCal.parse(ics)
end

kerrizor

class MiniTest::Unit::TestCase
  def assert_change(block)
    before = block.call

    yield

    refute_equal before, block.call
  end

  def refute_change(block)

kerrizor

Test Coverage

Rcov

• https://github.com/relevance/rcov

SimpleCov

• https://github.com/colszowka/simplecov

kerrizor

#
# Don't want to run PostgreSQL as a service? Want to manually start and stop it?
#  >> bundle exec rake rabbitmq:mac:start 
#  >> bundle exec rake rabbitmq:mac:stop
#

namespace :rabbitmq do
  namespace :mac do

    desc "Starts a Mac brew installed RabbitMQ server."

kerrizor

#!/bin/sh
#
# Suggested name for this script: git-clean-stale-branches
#
# This script will help to remove "stale" branches from a remote
# repository (by default the "origin" repository). Stale branches
# are any branches that does not exist in the local repository.
#
# This script should be run in the local repository. It will print
# out a git command to remove all branches from the remote repository

kerrizor

Get the Heroku db as detailed here:
http://devcenter.heroku.com/articles/pgbackups#exporting_via_a_backup

1. heroku pgbackups:capture
2. heroku pgbackups:url <backup_num>  #=>backup_url
   -  get backup_num with cmd "heroku pgbackups"
3. curl -o latest.dump <backup_url>

Then locally do:
$ pg_restore --verbose --clean --no-acl --no-owner -h localhost -U myuser -d mydb latest.dump

kerrizor

Models, Roles, Decorators, and Interactions

A modest alternative to DCI that might be worth further thought

One of the problems with advancing the discussion on DCI is that we lack a comparable alternative pattern that has the same goals, but favors a low ceremony approach. The closest thing we have to that is Rails concerns, but they are more like distant relatives of the DCI concepts rather than first cousins, and that makes comparisions between the two approaches not especially fruitful.

I am considering the idea of experimenting with my own paradigm that captures the intent and purity of DCI, but with the convenience of concerns. Please note that this is just the starting point of a conversation, it is NOT a promise of comercially available cold fusion or a cure for cancer. It's just a gist with an idea on it I'd like to hear your thoughts on.

What if we had a top-level topology that was split into Models, **Rol

kerrizor

"The Orc and the Pie"

by Monte Cook

The World's Shortest (Yet Technically Complete) Adventure

Adventure Background: An orc has a pie.

Adventure Synopsis: The PCs kill the orc and take his pie.