h3h

[user]
        name = Brad Fults
        email = bfults@gmail.com
[alias]
        amend = commit --amend
        co = checkout
        st = status
        cp = cherry-pick

        # edit config (global, local)

h3h

# awesome git prompt
export GIT_PS1_SHOWDIRTYSTATE=1
export GIT_PS1_SHOWSTASHSTATE=1
export GIT_PS1_SHOWUPSTREAM="auto"
export PS1="${WHITE}\$(date +%H:%M) ${CYAN}\w ${RED}\$(~/.rvm/bin/rvm-prompt v)${GREEN}\$(__git_ps1)${WHITE}\$${RESET} "
export TERM="xterm-256color"

# scm stuff
alias gp="git pull"
alias gpu="git push"

h3h

$ rake db:load_config
** Invoke db:load_config (first_time)
** Execute db:load_config
rake aborted!
(<unknown>): did not find expected key while parsing a block mapping at line 1 column 1
/Users/bfults/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/psych.rb:203:in `parse'
/Users/bfults/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/psych.rb:203:in `parse_stream'
/Users/bfults/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/psych.rb:151:in `parse'
/Users/bfults/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/psych.rb:127:in `load'
/Users/bfults/.rvm/gems/ruby-1.9.3-p194@uncommon/gems/railties-3.2.8/lib/rails/application/configuration.rb:115:in `database_configuration'

h3h

Original Post

Evaluating Team Members

If people want to move, and the leads of those projects deem them qualified, there’s no reason not to allow this.

Deeming someone qualified is a pretty nuanced and difficult process. I wouldn’t expect all or even most temporary tech leads to get it right (or even be close) for a long time.

h3h

My personal user stylesheet to get rid of focus outlines on non-form elements because I don't personally need them for accessibility.

Don't ever do this in your site's stylesheet because you're putting disabled users at a disadvantage. Do put this in your own user stylesheet if you hate the focus outlines in Gmail, Google Groups and countless other web apps.

See also: http://www.outlinenone.com/

For Chrome on Mac, this goes in ~/Library/Application Support/Google/Chrome/Default/User StyleSheets/Custom.css

h3h

Modifying Programs

When modifying a program, or when reviewing a modification of a program, you will want to consider at least the following:

1. Tests

• Is the modification tested?
• Can you prove that the tests cover both the pre-modification and post-modification states of the program correctly? Do it.

2. Interface

• Does the modification change the interface of the code?
• If so, are all possible callers prepared for the change?

h3h

https://github.com/[yourname]

Ambition

[Describe ambitions: type of work, attributes of team, what you want to learn & teach]

Experience

[in reverse chronological order, list at most 5 positions or 10 years back, whichever is fewer]

h3h

source "https://rubygems.org/"

gem 'rack-fiber_pool'
gem 'mysql2'
gem 'activerecord'
gem 'em-synchrony'
gem 'em-http-request'
gem 'grape'
gem 'goliath'
gem 'multi_json'

h3h

class Foo < ActiveRecord::Base

  ALLOWED_HTML_ELEMENTS = %w[
    a b br blockquote code em h2 h3 hr i li ol p pre s strong sub sup u ul
  ]
  ALLOWED_EMPTY_HTML_ELEMENTS = %w[br hr]

  before_validation :sanitize_html

  private

h3h

github.com##div#discussion_bucket div.form-actions div.form-actions-protip
github.com##div#discussion_bucket div.previewable-comment-form p.drag-and-drop
github.com##div#discussion_bucket p.push-more
github.com##div#discussion_bucket span.tabnav-right span.tabnav-widget.text
github.com##div#discussion_bucket div.discussion-timeline div.thread-subscription-status