Esteban De la Rosa gabbanaesteban

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

	dispatch:beforeDispatchLoop
	dispatch:beforeDispatch
	dispatch:beforeNotFoundAction
	dispatch:beforeExecuteRoute
	dispatch:afterInitialize
	dispatch:afterExecuteRoute
	dispatch:afterDispatch
	dispatch:afterDispatchLoop
	dispatch:beforeException

	#!/bin/bash
	# git-cleanup-repo
	#
	# Author: Rob Miller <rob@bigfish.co.uk>
	# Adapted from the original by Yorick Sijsling

	git checkout master &> /dev/null

	# Make sure we're working with the most up-to-date version of master.
	git fetch

	So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

	Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

	* Off the top of my head *

	1. Fork their repo on Github
	2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

	git remote add my-fork git@github...my-fork.git

Esteban De la Rosa gabbanaesteban

General rules

Design rules