#HTML&CSS
- Front-end Formations
- CSS Cross-Country
- Journey Into Mobile
- Assembling Sass
- Assembling Sass Part 2
- Fundamentals of Design
#JavaScript
=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') |
iTerm2
http://iterm2.com/
Oh my ZSH
https://github.com/robbyrussell/oh-my-zsh
HomeBrew
Installation guide for Ruby stack in Ubuntu (Work In Progress) | |
Open your terminal and copy and paste the following commands: | |
# This will install: git, ruby and zsh: | |
sudo apt-get update | |
sudo apt-get install build-essential git zlib1g-dev openssl libopenssl-ruby1.9.1 libssl-dev libruby1.9.1 libreadline-dev libcurl4-gnutls-dev librtmp-dev curl -y | |
sudo apt-get install zsh -y |
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.