evaldasg

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.

What to expect

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.

evaldasg

#!/bin/bash

# Downloads and install a .dmg from a URL
#
# Usage
# $ dmginstall [url]
# 
# For example, for installing alfred.app
# $ dmginstall http://cachefly.alfredapp.com/alfred_1.3.1_261.dmg
#

evaldasg

source: https://gist.github.com/gaearon/ffd88b0e4f00b22c3159

The “purer” version is O(n2) where the original version is O(n), so it’s not the same as using for loops vs Array#reduce. Here’s a benchmark:

function mapValues1(obj, fn) {
  return Object.keys(obj).reduce((result, key) => {
    result[key] = fn(obj[key], key);
    return result;
 }, {});

evaldasg

var YUI = require('yui').YUI,
    Y   = YUI(/* Your YUI Config */),
    requireAuth = require('./lib/middlware/auth'),
    modelLoader = require('./lib/middlware/loader'),
    app = /* create express app */;

Y.namespace('TDP').config = {
    webservices : global.config.webservices.path
};

evaldasg

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I lead the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can'

evaldasg

HTTP status code symbols for Rails

Thanks to Cody Fauser for this list of HTTP responce codes and their Ruby on Rails symbol mappings.

Status Code Symbol
1xx Informational
100 :continue
101 :switching_protocols
102 :processing

evaldasg

install https://www.xquartz.org/index.html
brew install chromedrive
gem install cucumber
bundle exec rails s thin -d -p 3333 -P /tmp/main.pid -e cucumber
bundle exec cucumber features/

evaldasg

ffmpeg -i screen01.mp4 -r 15 output.gif

evaldasg

Rails Rspec APIs Testing Notes

Folders Structure

  spec
  |--- apis #do not put into controllers folder. 
        |--- your_api_test_spec.rb  
  |--- controllers
  |--- models
  |--- factories
 |--- views

evaldasg

git clone https://github.com/vim/vim.git

sudo apt-get install libncurses-dev

e ~/Downloads/vim/src % ./configure --prefix=/usr/local \                                                                                                                                                                                                                  ✭ master ‹2.4.1›
--enable-gui=auto --without-x --disable-nls --enable-multibyte --with-tlib=ncurses --enable-pythoninterp --enable-rubyinterp --with-ruby-command=$(which ruby) --with-features=huge

make
sudo make install