UPDATE a fork of this gist has been used as a starting point for a community-maintained "awesome" list: machine-learning-with-ruby Please look here for the most up-to-date info!
- liblinear-ruby: Ruby interface to LIBLINEAR using SWIG
#!/bin/sh -e | |
# A simple script to keep a tidy ~/code directory organized by owner & then repo | |
# When the script is done, just hit command-v to switch into the directory | |
# (Github and Mac only. Sorry, openness!) | |
# | |
# Usage: | |
# gloan <org>/<repo> | |
# Or: | |
# gloan <org> <repo> |
require 'minitest/autorun' | |
class FooTest < Minitest::Test | |
def self.profile name | |
define_method("test_profile_#{name}") do | |
# start timer | |
10.times { send name } | |
# end timer | |
if performace_regresses | |
flunk "you failed" |
require 'slippery' | |
require 'fileutils' | |
require 'tempfile' | |
require_relative 'watch_task' | |
namespace :slippery do | |
extend Slippery::ProcessorHelpers::ClassMethods | |
NAME = 'learn_to_learn' |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.
Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.
First you will need to get an OAuth Token from GitHub using your own username and "note"