dgowrie

Why aren't I seeing my changes?

What do you mean 404 error?!?

Oh come ON, I just DID that!

How often are you working on something and are stuck trying to debug some irritation problem, only to discover after time that you've done something embarrassingly stupid? It's good to go through a checklist of "dumb" questions before spending an hour in the debugger or pouring over changesets.

Example:

• Is the computer plugged in? (classic tech support!)

dgowrie

var myPrototypeModule = (function() {
	'use strict';
	var privateVar = 'Alex Castrounis',
		count = 0;

	function PrototypeModule(name) {
		this.name = name;
	}

	function privateFunction() {

dgowrie

There are many Git workflows out there, I heavily suggest also reading the atlassian.com [Git Workflow][article] article as there is more detail then presented here.

The two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited.

When using Bash in the command line, it leaves a bit to be desired when it comes to awareness of state. I would suggest following these instructions on [setting up GIT Bash autocompletion][git-auto].

Basic branching

When working with a centralized workflow the concepts are simple, master represented the official history and is always deployable. With each now scope of work, aka feature, the developer is to create a new branch. For clarity, make sure to use descriptive names like transaction-fail-message or github-oauth for your branches.

dgowrie

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "your_email@youremail.com"

dgowrie

var myModule = ( function($, undefined) {
	var _person = function(firstName, lastName, age) {
		this.firstName = firstName;
		this.lastName = lastName;
		this.age = age;
	};

	_person.prototype.fullName = function() {
		return this.firstName + ' ' + this.lastName;
	};

dgowrie

/* Use class-attribute selectors for modules with common styles */
[class*="btn--"] {
 	background: #CCC;
 	padding: .5em;
 	text-decoration: none;
}

/* Target individual module modifiers as needed */
.btn--add {
 	background-image:('icon-plus.png') 0 50% no-repeat;

dgowrie

// constructor
function Person(name) {
	this.name = name;

	// etc... but no methods here
}


// prototype for all methods, using an IIFE with a returned object for 'public' methods
Person.prototype = (function() {

dgowrie

// Demonstrates the side effects of using 'new' to extend a prototype and the reason to use Object.create (with a shim for IE8 support).
//
// It can be a problem to use 'new' when extending a superclass because you're actually running the superclass's constructor.
// Using Object.create() avoids the problem of unintentional side effects from running the superclass constructor.
// see http://www.objectplayground.com/ for details

// Parent class constructor
function Parent() {
    alert("side effect!");
}

dgowrie

Prototypal inheritance in JavaScript is described by Douglas Crockford as: you make prototype objects, and then ... make new instances. Objects are mutable in JavaScript, so we can augment the new instances, giving them new fields and methods. These can then act as prototypes for even newer objects. We don't need classes to make lots of similar objects....Objects inherit from objects. What could be more object oriented than that?

http://javascript.crockford.com/prototypal.html

dgowrie

// alternative approach for testing if value is an Object

(function() {

	'use strict';

	var hash = {
		level1a: 'l1a',
		level1b: 'l1b',
		level1c: {