hiromipaw

### Keybase proof

I hereby claim:

  * I am hiromipaw on github.
  * I am hiroisgroot (https://keybase.io/hiroisgroot) on keybase.
  * I have a public key ASDLnwDjjFZiM5Qo-TSwglzQKkC0t2mctvaBNZKU4jB4IAo

To claim this, I am signing this object:

hiromipaw

#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 3.16.43 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"

hiromipaw

Keybase proof

I hereby claim:

• I am hiromipaw on github.
• I am hiro (https://keybase.io/hiro) on keybase.
• I have a public key ASAvBJ_Yh-zR96MemhDKcwPVWpKq-XVzd3le5FVtmhhMTQo

To claim this, I am signing this object:

hiromipaw

print "Hello World"

# -*- encoding: utf-8 -*-
import os, sys, re, datetime, json
from datetime import datetime
from time import gmtime, strftime, sleep
from selenium import webdriver
from selenium.webdriver.common.keys import Keys
from selenium.common.exceptions import TimeoutException
from browsermobproxy import Server

hiromipaw

1. What is a class, what is an object and why we need modules

This may be simple, but it allows to start a conversation between two strangers involved into the same craft.

Answer:

Classes are a blue-print, they may hold data, likely they hold methods; classes are directly connected with an idea of objects, because object is an instance of a class. As objects are first-class citizens in Ruby, there is a main, root class Object, and all classes are inherited from this root entity. Modules, generally, are a tool for mix-ins and they provide something we call a namespace. Modules cannot be initialised the way we can do this with classes, but they provide a multiple inheritance.

2. Who’s _why and what’s up with his Shoes?

hiromipaw

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.