| =Navigating= | |
| visit('/projects') | |
| visit(post_comments_path(post)) | |
| =Clicking links and buttons= | |
| click_link('id-of-link') | |
| click_link('Link Text') | |
| click_button('Save') | |
| click('Link Text') # Click either a link or a button | |
| click('Button Value') |
| function git_branch { | |
| ref=$(git symbolic-ref HEAD 2> /dev/null) || return; | |
| echo "("${ref#refs/heads/}") "; | |
| } | |
| function git_since_last_commit { | |
| now=`date +%s`; | |
| last_commit=$(git log --pretty=format:%at -1 2> /dev/null) || return; | |
| seconds_since_last_commit=$((now-last_commit)); | |
| minutes_since_last_commit=$((seconds_since_last_commit/60)); |
| require 'mechanize' | |
| @username = '[email protected]' | |
| @password = 'hi2u' | |
| @download_path = File.expand_path 'downloads' | |
| @wget_cookie = File.expand_path(File.dirname(__FILE__)) + '/wget-cookies.txt' | |
| unless File.directory? @download_path | |
| puts "@{download_path} doesn't exist!" | |
| exit |
Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.
open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl
You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <title>Untitled</title> | |
| <style> | |
| #example { | |
| background: #f00; | |
| width: 300px; | |
| height: 300px; |
This re-styles your sublime text 2 sidebar to be darker, so it doesn't blind you when using a dark theme.
Save the Default.sublime-theme file into packages/Theme - Default, make a backup of your original if you want to be able to go back easily.
| Here is a list of scopes to use in Sublime Text 2 snippets - | |
| ActionScript: source.actionscript.2 | |
| AppleScript: source.applescript | |
| ASP: source.asp | |
| Batch FIle: source.dosbatch | |
| C#: source.cs | |
| C++: source.c++ | |
| Clojure: source.clojure | |
| CoffeeScript: source.coffee |
Originally published in June 2008
When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.
To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.
Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.
