cribbed from http://pastebin.com/xgzeAmBn
Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.
Just install this in your apps like so:
gem 'test-spec-mini', :git => 'git://gist.github.com/1806986.git', :require => 'mini'
This installs a patched ruby 1.9.3-p327 with various performance improvements and a backported COW-friendly GC, all courtesy of funny-falcon.
You will also need a C Compiler. If you're on Linux, you probably already have one or know how to install one. On OS X, you should install XCode, and brew install autoconf using homebrew.
| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE | |
| Version 2, December 2004 | |
| Copyright (C) 2011 YOUR_NAME_HERE <YOUR_URL_HERE> | |
| Everyone is permitted to copy and distribute verbatim or modified | |
| copies of this license document, and changing it is allowed as long | |
| as the name is changed. | |
| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE |
| {-# OPTIONS_GHC -fcontext-stack=32 #-} | |
| {-# LANGUAGE TypeSynonymInstances, DeriveDataTypeable, MultiParamTypeClasses #-} | |
| import XMonad hiding ( (|||) ) | |
| import qualified XMonad.StackSet as W | |
| import Control.OldException(catchDyn,try) | |
| import Data.Char (toLower) | |
| import Data.Monoid (mappend) | |
| import Data.List (intercalate, intersperse, isSuffixOf, isPrefixOf) |
Fibur is a library that allows concurrency during Ruby I/O operations without needing to make use of callback systems. Traditionally in Ruby, to achieve concurrency during blocking I/O operations, programmers would make use of Fibers and callbacks. Fibur eliminates the need for wrapping your I/O calls with Fibers and a callback. It allows you to write your blocking I/O calls the way you normally would, and still have concurrent execution during those I/O calls.
Say you have a method that fetches data from a network resource:
Rails 3.2 ships with a simple FileWatcher that only reloads your app if any of the files changed.
Besides, it also provides a mechanism to hook up your own file watcher mechanism, so we can use tools like FSSM that hooks into Mac OS X fsevents. This is an example on how to hook your own mechanism (you need Rails master, soon to be Rails 3.2):
Copy the 2_file_watcher.rb file below to lib/file_watcher.rb
Add the following inside your Application in config/application.rb
if Rails.env.development?
| Hi David, | |
| I came across your profile online and wanted to reach out about Development | |
| Opportunities here at Groupon. The company is growing, and we're always | |
| looking for folks with solid skills that can make positive contribution to | |
| our continued success. Any chance you'd be open to a quick conversation | |
| about opportunities, or for any possible networking potential? If so, let me | |
| know when you're free and we can set up a time to chat. Also, if you are | |
| interested, it would be great if you could forward a current resume over | |
| that I can take a look at. I look forward to hearing back from you! Please | |
| let me know if you have any questions. |
This gist is no longer valid. Please see Compass-Rails for instructions on how to install.
| # WAIT! Do consider that `wait` may not be needed. This article describes | |
| # that reasoning. Please read it and make informed decisions. | |
| # https://www.varvet.com/blog/why-wait_until-was-removed-from-capybara/ | |
| # Have you ever had to sleep() in Capybara-WebKit to wait for AJAX and/or CSS animations? | |
| describe 'Modal' do | |
| should 'display login errors' do | |
| visit root_path |
