type below:
brew update
brew install redis
To have launchd start redis now and restart at login:
brew services start redis
| // USAGE | |
| /* | |
| .box { | |
| width: 100%; | |
| @include bp(mobile-up) { | |
| width: 100px; | |
| } | |
| } |
type below:
brew update
brew install redis
To have launchd start redis now and restart at login:
brew services start redis
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
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.
| 1) Create a branch with the tag | |
| git branch {tagname}-branch {tagname} | |
| git checkout {tagname}-branch | |
| 2) Include the fix manually if it's just a change .... | |
| git add . | |
| git ci -m "Fix included" | |
| or cherry-pick the commit, whatever is easier | |
| git cherry-pick {num_commit} | |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Box Shadow</title> | |
| <style> | |
| .box { | |
| height: 150px; | |
| width: 300px; | |
| margin: 20px; |
| -- model | |
| some sort of constant hash: | |
| HASH_NAME = { | |
| 0 => "Choose:", | |
| 1 => "On-Campus Recruiting - CSO",· | |
| 2 => "CSO Staff Referral", | |
| 3 => "Faculty Contact",· | |
| 4 => "Career Day",· | |
| 5 => "CSO Summer Job Listing",· | |
| 6 => "Alumni Contact",· |