virtualstaticvoid

why ./task.js?

One word: task automation. It's basically zero effort and you can use the ./task.js package manager to handle any repetitive tasks. You can use ./task.js to automate everything with minimum effort.

./task.js provides the structure, order, and authority that you as a developer so desperately crave. ./task.js will also take responsibility for your actions if you need it to. It's what everybody is using now. ./task.js is the new hotness. It's all about ./task.js now, just like that.

This is compared to npm run/bash scripts, which are:

virtualstaticvoid

  # Use: it { should accept_nested_attributes_for(:association_name).and_accept({valid_values => true}).but_reject({ :reject_if_nil => nil })}
  RSpec::Matchers.define :accept_nested_attributes_for do |association|
    match do |model|
      @model = model
      @nested_att_present = model.respond_to?("#{association}_attributes=".to_sym)
      if @nested_att_present && @reject
        model.send("#{association}_attributes=".to_sym,[@reject])
        @reject_success = model.send("#{association}").empty?
      end
      model.send("#{association}").clear

virtualstaticvoid

module Resque
  def push_with_meta(queue, item)
    if item.respond_to?(:[]=)
      item[:meta] = {:queued_at => Time.now.to_f}
    end
    push_without_meta(queue, item)
  end

  class Job
    # Returns a Hash of the meta data related to this Job.

virtualstaticvoid

/*
 *	add this to your own css file,
 *	to overwrite the _chosen_ styling, to look more like bootstrap!
 *	
 *	note: for the error part to work, an .error class-name must be added
 *	to a wrapping DIV, to display the bootstrap error styling. I have
 *	just use the wrapping .control-group DIV
 *	
 *	credit: Rasmus Burkal, @rabu81
*/

virtualstaticvoid

require 'yaml'
require 'logger'
require 'active_record'

namespace :db do
  def create_database config
    options = {:charset => 'utf8', :collation => 'utf8_unicode_ci'}

    create_db = lambda do |config|
      ActiveRecord::Base.establish_connection config.merge('database' => nil)

virtualstaticvoid

# Author: Pieter Noordhuis
# Description: Simple demo to showcase Redis PubSub with EventMachine
#
# Update 7 Oct 2010:
# - This example does *not* appear to work with Chrome >=6.0. Apparently,
#   the WebSocket protocol implementation in the cramp gem does not work
#   well with Chrome's (newer) WebSocket implementation.
#
# Requirements:
# - rubygems: eventmachine, thin, cramp, sinatra, yajl-ruby

virtualstaticvoid

# CQRS+ES Domain DSL

class Symbol
  def snake_case
    to_s.gsub(/([A-Z]+)([A-Z][a-z])/, '\1_\2').
      gsub(/([a-z\d])([A-Z])/, '\1_\2').
      tr("-", "_").
      downcase.to_sym
  end

virtualstaticvoid

user  nginx;
worker_processes  5;

error_log  /var/log/nginx.error.log;
pid        /var/run/nginx.pid;

events {
  worker_connections  1024;
}

virtualstaticvoid

Pagination 101

Article by Faruk Ateş, [originally on KuraFire.net][original] which is currently down

One of the most commonly overlooked and under-refined elements of a website is its pagination controls. In many cases, these are treated as an afterthought. I rarely come across a website that has decent pagination, and it always makes me wonder why so few manage to get it right. After all, I'd say that pagination is pretty easy to get right. Alas, that doesn't seem the case, so after encouragement from Chris Messina on Flickr I decided to write my Pagination 101, hopefully it'll give you some clues as to what makes good pagination.

Before going into analyzing good and bad pagination, I want to explain just what I consider to be pagination: Pagination is any kind of control system that lets the user browse through pages of search results, archives, or any other kind of continued content. Search results are the o

virtualstaticvoid

# -*- mode: ruby; coding: utf-8 -*-

if defined? Rails
  railsrc = __FILE__ + '.rails'
  load railsrc if File.exist? railsrc
  envrc   = File.join( Rails.root, '.irbrc' )
  load envrc if File.exist? envrc
end