An implementation of Conway's Game of Life in 140 characters of Ruby.
Created by Simon Ernst (@sier).
# the new and improved one-file rails app -- now including | |
require "action_controller/railtie" | |
class Tester < Rails::Application | |
config.session_store :cookie_store, :key => '_rails_session' | |
config.secret_token = '095f674153982a9ce59914b561f4522a' | |
end | |
class UsersController < ActionController::Base |
An implementation of Conway's Game of Life in 140 characters of Ruby.
Created by Simon Ernst (@sier).
Updated for Rails 4.0.0+
Set up the bower
gem.
Follow the Bower instructions and list your dependencies in your bower.json
, e.g.
// bower.json
{
#!/usr/bin/env ruby | |
# HOWTO: | |
# copy this file to script/travis-deploy | |
# chmod +x script/travis-deploy | |
# add the following to your .travis.yml | |
# after_success: | |
# - "script/travis-deploy" | |
Elasticsearch missing filter with nested objects |
This is a very rough script to export your octopress files to Ghost. You will still need to check your data but it will give you a head start. Feel free to fork and optimize the script for your purpose.
The following should be considered:
source/_posts
directory/var/www/ghost/content/images
#!/usr/bin/env ruby | |
require 'em-websocket' | |
require 'thor' | |
module Handler | |
def initialize(args) | |
@ws = args | |
end | |
def receive_data(data) |
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".