sferik

What is the system Ruby?

What version of Ruby shipped by default on Mac OS X?

Default Ruby version * Refers to the fully patched version (e.g. 10.5.8, not 10.5.0). Earlier versions may have shipped with different Ruby patchlevels but the RUBY_VERSION has never changed within major Mac OS X releases.

Mac OS X version*	Mac OS X release date

bendc

const arr = [["foo", "bar"], ["hello", "world"]];

// Create object from array of tuples
const obj = {}; arr.forEach(el => obj[el[0]] = el[1]);
const map = new Map(arr);

// Get object size
const objSize = Object.keys(obj).length;
const mapSize = map.size;

cbetta

alias latest='function _latest(){ curl -s "https://rubygems.org/api/v1/versions/$1/latest.json" | cut -d"\"" -f 4 };_latest'

henrik

# ESV - Excel generation with the ease of CSV generation.
#
# By Henrik Nyh 2015-07-01 under the MIT license.
# Using a lot of code from LivingSocial's Excelinator, also under the MIT license: https://github.com/livingsocial/excelinator/blob/master/lib/excelinator/xls.rb

require "spreadsheet"

class ESV
  def self.generate
    instance = new

jimmycuadra

#cloud-config

coreos:
  etcd:
    # generate a new token for each unique cluster from https://discovery.etcd.io/new
    discovery: https://discovery.etcd.io/<token>
    # multi-region deployments, multi-cloud deployments, and droplets without
    # private networking need to use $public_ipv4
    addr: $private_ipv4:4001
    peer-addr: $private_ipv4:7001

dhh

# config/routes.rb
resources :documents do
  scope module: 'documents' do
    resources :versions do
      post :restore, on: :member
    end

    resource :lock
  end
end

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

henrik

1. Your class can be no longer than 100 lines of code.
2. Your methods can be no longer than five lines of code.
3. You can pass no more than four parameters and you can’t just make it one big hash.
4. When a call comes into your Rails controller, you can only instantiate one object to do whatever it is that needs to be done. And your view can only know about one instance variable.

You can break these rules if you can talk your pair into agreeing with you.

avand

# Just replace the URL (don't forget "/raw")
curl --silent https://www.stypi.com/raw/avand/interviews/reverse_polish_notation.rb | ruby

swanson

J.B. Rainsberger - Integration Tests are a Scam

J.B. Rainsberger - When Is It Safe to Introduce Test Doubles?

Gary Bernhardt - Boundaries

Gary Bernhardt - Functional Core, Imperative Shell

Tom Stuart - Thinking functionally in Ruby