Nicholas Henry nicholasjhenry

Cohesion and Big ActiveRecord Models

One of the problems of big ActiveRecord models is their low cohesion. In Rails we group behaviour around the entities of the domain we're modelling. If we use only ActiveRecord models for that, we'll probably end up with classes full of actions, in most cases, completely unrelated to each other (except for the fact that they act on the same domain entity).

To illustrate the issue let's imagine a big Post AR model of a blog application. In this app, users can add tags to their posts. Since this is the only class with this ability, I decide to put the related logic in the Post model itself. For this, presumably at the beginning of the file, I write a couple of has_many entries for tags and taggings. Then, fifty lines below, along with the rest of scopes, I add one more to find posts by tag name. A couple of hundred lines later, I put a virtual attribute tag_list which will be used to update the associations from a string of tag names separated by commas. Fin

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

YARD CHEATSHEET http://yardoc.org

cribbed from http://pastebin.com/xgzeAmBn

Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.

Modules

Namespace for classes and modules that handle serving documentation over HTTP

Requirements

Docker Machine + Docker
curl
A Virtualbox-driven Docker Machine called "default" docker-machine create --driver virtualbox default (this is the default with Docker toolkit).

Usage

The git.io URL (http://git.io/vsk46) is a shortened form of the raw url of the plist.

	# Install with:
	# bash < <(curl -L https://raw.github.com/gist/1780623)
	#
	# Reference: http://blog.wyeworks.com/2011/11/1/ruby-1-9-3-and-ruby-debug

	echo "Installing ruby-debug with ruby-1.9.3-p0 ..."

	curl -OL http://rubyforge.org/frs/download.php/75414/linecache19-0.5.13.gem
	curl -OL http://rubyforge.org/frs/download.php/75415/ruby-debug-base19-0.11.26.gem

	class ActiveUserPolicy
	LOGIN_PERIOD = 14.days

	class Query
	def initialize(relation = User.scoped)
	@relation = relation
	end

	def find_each(&block)
	@relation.

	require "dim"
	AppContainer = Dim::Container.new

	AppContainer.register(:env) { ENV['ADWORK_ENV'] \|\| "development" }
	AppContainer.register(:production?) { \|c\| c.env == 'production' }
	AppContainer.register(:development?) { \|c\| c.env == 'development' }
	AppContainer.register(:test?) { \|c\| c.env == 'test' }
	AppContainer.register(:root) { File.expand_path(File.dirname(__FILE__)+"/../..") }

	AppContainer.register(:logger) do \|c\|

	defmodule Example.Server do
	use GenServer

	def start_link(opts \\ []) do
	GenServer.start_link(__MODULE__, :ok, opts)
	end

	def init(state) do
	Process.flag(:trap_exit, true) # must trap exit for terminate call back to work
	IO.inspect "Starting server..."

	def index
	@stockist_countries = StockistCountry.active_stockists
	end

	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console