Skip to content

Instantly share code, notes, and snippets.

View christophermoura's full-sized avatar

Christopher Moura christophermoura

View GitHub Profile
# SUPER DARING APP TEMPLATE 1.0
# By Peter Cooper
# Link to local copy of edge rails
inside('vendor') { run 'ln -s ~/dev/rails/rails rails' }
# Delete unnecessary files
run "rm README"
run "rm public/index.html"
run "rm public/favicon.ico"
[alias]
st = status
ci = commit
co = checkout
svnup = svn fetch
sup = svn fetch
svnci = svn dcommit
sci = svn dcommit
up = pull --rebase
sreb = svn rebase
#!/usr/bin/env ruby -w
# Rename all files in the directory. The new names will be generated from a basename.
#
# AUTHOR: Daniel Lopes
# October 20, 2009
#
# USAGE:
# rename-files . base_name.jpg #=> base_name1.jpg, base_name2.jpg, etc
require "pathname"
#!/usr/bin/env ruby -w
# Ruby beautifier, version 2.1, 09/11/2006
# Copyright (c) 2006, P. Lutus
# Released under the GPL
# To use in TextMate:
# Make a command that calls "~/bin/beautify" with
# Input: Selected Text or Document
# Output: Replace Selected Text
# simple capistrano task for wordpress deploy
# just replace the content to fit your app path and names
# and run cap deploy:setup && cap deploy
# you can also run a cap wordpress:upload_config to copy the local config-sample.php to remote shared folder
# warning: this recipe don't create the database
# APP SETTINGS
set :application, "your_app_name"
set :domain_name , "yourdomain.com.br"
@christophermoura
christophermoura / gist:1209075
Created September 11, 2011 02:05 — forked from viniciusteles/gist:556029
Sete Atitudes para Hackear a Indústria de Software
Sete Atitudes para Hackear a Indústria de Software
By Klaus Wuestefeld
1) Torne-se excelente.
Seja realmente bom em alguma coisa. Não fique só choramingando ou
querendo progredir às custas dos outros. Não pense q pq vc sentou 4
anos numa faculdade ouvindo um professor falar sobre software q vc
sabe alguma coisa. Jogador de futebol não aprende a jogar bola tendo

Contract Killer 3

Revised date: 07/11/2012

Between us [company name] and you [customer name]

Summary:

We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.

Clean Code - Martin
Code Complete - McConnell
Compilers - Aho
Computer Networks (5th Edition) - Tanenbaum
Design Patterns - Gamma, et al
Domain-Driven Design - Evans
Growing Object-Oriented Software, Guided by Tests - Freeman, et al
Introduction to Automata Theory, Languages, and Computation - Hopcroft
Purely Functional Data Structures - Okasaki
Refactoring - Fowler
/*
POMODORO 0.2
by @erikaheidi
January 2015
LED STATES:
starts blue - idle. When the button is clicked, it starts a pomodoro working phase. LED will be a red "breathing" style.
After the time is done, it will change to GREEN (static) - indicating that the pomodoro was completed and now you should go to a PAUSE
When clicking the button, the PAUSE phase will start (GREEN "BREATHING"). It will turn to RED (static) when the pause is done, indicating that
a new WORKING phase should follow. When the button is clicked, starts over with the WORKING phase (RED breathing LED) :)
@christophermoura
christophermoura / 0_reuse_code.js
Last active August 29, 2015 14:18
Here are some things you can do with Gists in GistBox.
// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console