Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
| Dependencies | |
| brew install gnu-sed |
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!
\
Leanstack.io list of cloud services
Analytics
| if Moped.logger == Rails.logger | |
| Moped.logger = Logger.new($stdout) | |
| true | |
| else | |
| Moped.logger = Rails.logger | |
| false | |
| end |
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.
| #!/bin/bash | |
| repos=( | |
| 'https://github.com/github/gitignore' | |
| 'https://github.com/twitter/bootstrap' | |
| 'https://github.com/h5bp/html5-boilerplate' | |
| 'https://github.com/cloudhead/less.js' | |
| 'https://github.com/jquery/jquery' | |
| 'https://github.com/jquery/jquery-mobile' |