Skip to content

Instantly share code, notes, and snippets.

Telmo / rspec-syntax-cheat-sheet.rb
Created January 20, 2012 14:24 — forked from dnagir/rspec-syntax-cheat-sheet.rb
RSpec 2 syntax cheat sheet by example
# RSpec 2.0 syntax Cheet Sheet by
# defining spec within a module will automatically pick Player::MovieList as a 'subject' (see below)
module Player
describe MovieList, "with optional description" do
it "is pending example, so that you can write ones quickly"
it "is already working example that we want to suspend from failing temporarily" do
pending("working on another feature that temporarily breaks this one")
class Dot
class Node
attr_reader :children, :name, :started
attr_accessor :finished
def initialize name, fields = [], started =
@name = name
@fields = fields
@children = []
@started = started
Telmo /
Created April 1, 2012 03:18 — forked from erikh/
OSX For Hackers
#!/usr/bin/env sh
# This is script with usefull tips taken from:
# install it:
# curl -sL | sh
Telmo / 1_let.rb
Created April 14, 2012 13:51 — forked from ryanb/1_let.rb
let vs def
desc "A user's comment" do
let(:user) { User.create! name: "John" }
let(:comment) { user.comments.create! }
it "delegates to user's name" do eq(
Telmo / personality.rb
Created April 18, 2012 19:48 — forked from wycats/personality.rb
More technical details about the discussion at last nights meetup
# Just wanted to clarify my points at the meetup last night.
# There were two different issues intertwined:
# (1) Whether to use extend or "include as extend"
# (2) When using "include as extend", what is the simplest way to achieve the goal?
# My personal opinion is that the answer to (1) is "extend", not "include as extend", but that
# is just my personal opinion. My answer to (2) is a more empirical question.
# Using the "extend" approach. Again, I personally prefer the simplicity of this approach, but
Telmo / fiber.rb
Created April 19, 2012 18:05 — forked from mfdela/fiber.rb
Ruby fiber benchmark
require 'fiber'
require 'benchmark'
class Ring
attr_reader :id
attr_accessor :attach
def initialize(id)
Telmo / futures.rb
Created April 22, 2012 19:15 — forked from wycats/0_app.rb
Example of using a simple future library for parallel HTTP requests
require "thread"
class Future
attr_reader :exception, :cancelled
def initialize(&block)
@thread =
@thread.abort_on_exception = false
@exception = nil
@cancelled = false
Telmo /
Created June 4, 2012 20:48 — forked from tenderlove/
An adapter for Rack that makes it look like node
# Make Rack look like node.
require 'node_adapter'
use Rack::Chunked
run createServer { |req, res|
Telmo /
Created October 21, 2012 06:51 — forked from briangonzalez/
img2boxshadow - a ruby script to convert images to CSS []


a ruby script to convert images to CSS (box-shadows)


gem install rmagick    # you'll need ImageMagick & Ruby first
gem install colormath
gem install micro-optparse
Telmo / integrated_docs.rb
Created November 21, 2012 12:20 — forked from mattwynne/integrated_docs.rb
Integrated documentation for Ruby
# For context, this was inspired by the RubyRogues podcast #79 where they talked about
# documentation in Ruby, and specifically grumbled quite a bit about the failings of RDoc.
# As someone who's spent a lot of time using an IDE for programming C# and Java, I think
# Ruby could do a lot better at putting documentation at our fingertips as we program.
# Maybe making the documentation part of the structure of the code would facilitate this?