vesan

namespace :routes do
  desc "Writes doc/routes.html. Requires Graphviz (dot)"
  task :visualizer => :environment do
    File.open(Rails.root.join('doc', 'routes.html'), 'wb') do |f|
      f.write Rails.application.routes.router.visualizer
    end
  end
end

vesan

#!/usr/bin/env ruby

require "rubygems"
require "mechanize"

TARGET_LOGIN_URL = "https://www.amazon.com/ap/signin?_encoding=UTF8&openid.assoc_handle=usflex&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.mode=checkid_setup&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.ns.pape=http%3A%2F%2Fspecs.openid.net%2Fextensions%2Fpape%2F1.0&openid.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amazon.com%2Fgp%2Fcss%2Fhomepage.html%3Fie%3DUTF8%26*Version*%3D1%26*entries*%3D0%26ref_%3Dnav_signin"
SOURCE_LOGIN_URL = "https://www.amazon.co.uk/ap/signin?_encoding=UTF8&openid.assoc_handle=gbflex&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.mode=checkid_setup&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.ns.pape=http%3A%2F%2Fspecs.openid.net%2Fextensions

vesan

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

vesan

module RedisHelper
  # decode Redis value back to Ruby object
  def self.decode(json)
    self.new(ActiveSupport::JSON.decode(json)["#{self.name.downcase}"])
  end

  # encode Ruby object for Redis
  def encoded
    self.updated_at = nil
    self.to_json

vesan

require "rubygems"
require "nokogiri"
require "uri"

module Rack
  class KarmaChameleon
    def initialize(app, options = {})
      @ext = options[:extension] || "html5"
      @ext_regexp = /\.#@ext$/
      @app = app

vesan

class DownloadsController < ApplicationController
  def show
    if @current_user
      send_file "#{Rails.root}/downloads/test.pdf"
    else
      head(:not_found)
    end
  end
end

vesan

#!/usr/bin/env ruby
# Usage: gemspec [-s] GEMNAME
#
# Prints a basic gemspec for GEMNAME based on your git-config info.
# If -s is passed, saves it as a GEMNAME.gemspec in the current
# directory. Otherwise prints to standard output.
#
# Once you check this gemspec into your project, releasing a new gem
# is dead simple:
#

vesan

# Put this file in your config/initializers directory and behold a tastier auto_link!

module ActionView
  module Helpers
    module TextHelper
      # Use auto_link and friends from Rails 3. They do the right thing (tm).

      remove_const(:AUTO_LINK_RE) if defined?(AUTO_LINK_RE)
      AUTO_LINK_RE = %r{
          ( https?:// | www\. )

vesan

gem 'cramp'
gem 'erubis', '2.6.5'
gem 'usher', "0.6.0"

vesan

# Monitor HTTP requests being made from your machine with a one-liner..
# Replace "en1" below with your network interface's name (usually en0 or en1)
sudo tcpdump -i en1 -n -s 0 -w - | grep -a -o -E "Host\: .*|GET \/.*"

# OR.. to be able to use as "httpdump" from anywhere, drop this into ~/.bash_profile:
# (again replace "en1" with correct network interface name)
alias httpdump="sudo tcpdump -i en1 -n -s 0 -w - | grep -a -o -E "Host\: .*|GET \/.*""

# All the above tested only on OS X.