RickCogley

@echo off
# Author: Rick Cogley
# Last Update: 1 Nov 2014
echo "== STARTING BATCH =="
echo "Results from %computername%:" > results.txt 
echo "Pinging..." >> results.txt
ping www.esolia.com >> results.txt
echo. >> results.txt
echo "Running SET..." >> results.txt
set >> results.txt

RickCogley

	var socials = '';
	socials += '<a class="aSocialMediaLink" id="idsocialFacebook" href="<%socialFacebook%>" target="_blank"><i class="fa fa-facebook"></i></a>';
	socials += '<a class="aSocialMediaLink" id="idsocialTwitter" href="<%socialTwitter%>" target="_blank"><i class="fa fa-twitter"></i></a>';
	socials += '<a class="aSocialMediaLink" id="idsocialLinkedin" href="<%socialLinkedin%>" target="_blank"><i class="fa fa-linkedin"></i></a>';
	socials += '<a class="aSocialMediaLink" id="idsocialGithub" href="<%socialGithub%>" target="_blank"><i class="fa fa-github"></i></a>';
	socials += '<a class="aSocialMediaLink" id="idsocialGoogleplus" href="<%socialGoogleplus%>" target="_blank"><i class="fa fa-google-plus"></i></a>';
	socials += '<a class="aSocialMediaLink" id="idsocialFlickr" href="<%socialFlickr%>" target="_blank"><i class="fa fa-flickr"></i></a>';
	socials += '<a class="aSocialMediaLink" id="idsocialInstagram" href="<%socialInstagram%>" target="_blank"><i class="fa fa-instagram"></i></a>';
	socials += '<a 

RickCogley

killall -KILL Finder

killall -KILL Dock

killall -KILL SystemUIServer

RickCogley

Can't access the outline at "http://little.porkchop.io/settings.opml" because the remote server didn't find it.

RickCogley

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

RickCogley

Libraries

• jQuery - The de-facto library for the modern age. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers.
• Backbone - Backbone.js gives structure to web applications by providing models with key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing API over a RESTful JSON interface.
• AngularJS - Conventions based MVC framework for HTML5 apps.
• Underscore - Underscore is a utility-belt library for JavaScript that provides a lot of the functional programming support that you would expect in Prototype.js (or Ruby), but without extending any of the built-in JavaScript objects.
• lawnchair - Key/value store adapter for indexdb, localStorage

RickCogley

Libraries

• 960 Grid System - An effort to streamline web development workflow by providing commonly used dimensions, based on a width of 960 pixels. There are two variants: 12 and 16 columns, which can be used separately or in tandem.
• Compass - Open source CSS Authoring Framework.
• Bootstrap - Sleek, intuitive, and powerful mobile first front-end framework for faster and easier web development.
• Font Awesome - The iconic font designed for Bootstrap.
• Zurb Foundation - Framework for writing responsive web sites.
• SASS - CSS extension language which allows variables, mixins and rules nesting.
• Skeleton - Boilerplate for responsive, mobile-friendly development.

Guides

RickCogley

Bug

ffb8b8  ✘
fc4e4e  ✘✘
red     ✘✘✘


Feature

89f786  ✔

RickCogley

You could define different groups of labels like issue types, issue priorities, issue statuses, version tags, and maybe more. In order to be able to see instantly to which group a label belongs to you could use a naming convention like <label-group>:<label-name>.

Using such a naming convention should make managing Github issues much easier and helps others to "understand" issues much faster. Note that you can also assign colors to labels which can add even more to readability (I would use a specific color for each label group). But because you still have to assign/unassign those labels to/from issues manually you might want to keep the overall list of groups/labels small.

According to the scheme suggested above you might define groups and corresponding labels as follows.

'issue type' group

type:bug
type:feature

RickCogley

The trickiest thing to get right is the labels. One that worked well for us is the idea of two-dimensional labelling (i.e. every issue has two labels):

Severity label: these labels have colors to make them visually identifiable. It’s important to not have too many of these, to make the choice easy, here are some suggestions:
blocking: drop everything you’re working on, this needs to be fixed today (we also had “überblocking” for extremely severe issues)
critical: this should be the next thing to work on, should be fixed within a few days
high priority: important to work on
low priority: if you have some spare time this would be nice to have.
Component label: which aspect of the project the issue related to, such as “debugger”, “dashboard” etc.
The labels are assigned by the reporter and adjusted (if necessary) by quality assurance people or the product/project manager