ArthurN

# Why:
# 1) Chrome 63 (Dec 8) breaks .dev domains by forcing HTTPS: https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/
# 2) Pow is at EOL, superceded by puma-dev (see http://pow.cx/manual, 6 Version History, 0.6.0, Dec 8 2017)

# Uninstall pow
curl get.pow.cx/uninstall.sh | sh

# If you use powder, you can remove it as well
gem uninstall powder

dypsilon

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

---

nbibler

if [ -f "$rvm_path/scripts/rvm" ]; then
  source "$rvm_path/scripts/rvm"

  if [ -f ".rvmrc" ]; then
    source ".rvmrc"
  fi

  if [ -f ".ruby-version" ]; then
    rvm use `cat .ruby-version`
  fi

bryanl

# put this at ~/.gitconfig

[alias]

  # I'm lazy, so two letters will always trump the full command
  co = checkout
  ci = commit
  cp = cherry-pick
  st = status
  br = branch

jpmckinney

# blog post: http://blog.slashpoundbang.com/post/2613268281/changing-from-tz-database-identifiers-to-rails-friendly
{
  "Australia/Adelaide"             => "Adelaide",
  "Australia/Broken_Hill"          => "Adelaide",
  "America/Anchorage"              => "Alaska",
  "America/Juneau"                 => "Alaska",
  "America/Nome"                   => "Alaska",
  "America/Yakutat"                => "Alaska",
  "Pacific/Gambier"                => "Alaska",
  "Asia/Almaty"                    => "Almaty",

jashkenas

// Handles JavaScript history management and callbacks. To use, register a
// regexp that matches the history hash with its corresponding callback.
window.HashHistory = {

  // The interval at which the window location is polled.
  URL_CHECK_INTERVAL : 500,

  // We need to use an iFrame to save history if we're in an old version of IE.
  USE_IFRAME : jQuery.browser.msie && jQuery.browser.version < 8,

mironov

class User < ActiveRecord::Base
  # gradual engagement is needed, to allow admin creation of users
  # users should create authorization data only when they need to
  # access some system feature that requires authentication
  # So ... our gradual engagement scheme for authlogic:
  # 1. admin creates user, setting only name and phone number (required)
  #    admin may set email address (optional)
  # 2. user is sent email invitation with link to activate their account
  #    admin can re-send email at user's request
  # 3. user sets login and password/password_confirmation using activation form