avdi

Dear IT Professional,

We have the following position provided below available.

Skills: Ruby on Rails
Location: Atlanta, GA

They will talk to anyone who has RUBY.

This digital start-up is searching for a progressive Software Engineer

mpapis

Use this command and follow the instructions:

curl -L get.rvm.io | bash -s stable --rails

Other options include(any gems imply --ruby):

--ruby=1.9.3
--gems=rails,gist

Optionally on OSX install homebrew, use brew command to install whatever database engine you need, ie brew install sqlite

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

tenderlove

###
# Scheme code is translated to YARV byte code, then evaluated in the
# Ruby Virtual Machine

require 'rbconfig'
require 'dl'
require 'fiddle'
require 'strscan'

class RubyVM

tagrudev

# Do not refactor, it is a bad practice. YOLO

# Not understanding why or how something works is always good. YOLO

# Do not ever test your code yourself, just ask. YOLO

# No one is going to read your code, at any point don't comment. YOLO

# Why do it the easy way when you can reinvent the wheel? Future-proofing is for pussies. YOLO

jcoglan

$VERBOSE = nil
require File.expand_path('../rooby', __FILE__)


Person = Rooby::Class.new 'Person' do
  define :initialize do |name|
    @name = name
  end
  
  define :name do

pengwynn

$ curl https://api.github.com/zen | octocatsay

           MMM.           .MMM
           MMMMMMMMMMMMMMMMMMM
           MMMMMMMMMMMMMMMMMMM      ____________________________
          MMMMMMMMMMMMMMMMMMMMM    |                            |
         MMMMMMMMMMMMMMMMMMMMMMM   | Practicality beats purity. |
        MMMMMMMMMMMMMMMMMMMMMMMM   |_   ________________________|
        MMMM::- -:::::::- -::MMMM    |/
         MM~:~   ~:::::~   ~:~MM

davidcelis

#!/usr/bin/env zsh
#
# Works best with blinking text; the last heart will blink
# when you have less than 25% of your battery life remaining.

BATTERY="$(pmset -g ps | awk 'NR==2' | perl -pe 's/.*?(\d+)%.*/\1/')"

if [[ $BATTERY -lt 25 ]]; then
  echo "\e[5;31m♥\e[0;31m♡♡\e[0m"
elif [[ $BATTERY -lt 50 ]]; then

bsodmike

The difference between those are that unit tests one object and one object only. Typically mocking anything else outside the SUT (System under test).

Integration tests a system of collaborators, or multiple objects that work in concert. Functional tests a system from the outside into the centre as a full stack test. User stories test interactions and outcomes.

The difference between functional and user stories is that a functional test exercises a system with a focus of "given this kind of input, I expect this output back" and user story is more focused on "When I perform this kind of thing, given the system is in this kind of state or has this data, I expect to see this kind of thing as a result."

Functional can also test the side-effects rather than just the input and output.

acook

module PubSub
  class << self
    def create type, channel, object
      channel = channel.to_sym

      case type
      when :listener
        listeners[channel] ||= Array.new
        listeners[channel] << object
        channels[channel] ||= Array.new