Skip to content

Instantly share code, notes, and snippets.

Avatar

Scott González scottgonzalez

View GitHub Profile
View freddish.md
  1. “State the idea you wish to express as clearly as possible, and in terms preschoolers can understand.” Example: It is dangerous to play in the street.
  2. “Rephrase in a positive manner,” as in It is good to play where it is safe.
  3. “Rephrase the idea, bearing in mind that preschoolers cannot yet make subtle distinctions and need to be redirected to authorities they trust.” As in, “Ask your parents where it is safe to play.”
  4. “Rephrase your idea to eliminate all elements that could be considered prescriptive, directive, or instructive.” In the example, that’d mean getting rid of “ask”: Your parents will tell you where it is safe to play.
  5. “Rephrase any element that suggests certainty.” That’d be “will”: Your parents can tell you where it is safe to play.
  6. “Rephrase your idea to eliminate any element that may not apply to all children.” Not all children know their parents, so: Your favorite grown-ups can tell you where it is safe to play.
  7. “Add a simple motivational idea that gives preschool
View cli.md

Shell

The shell is a layer above the kernel and can be a command-line shell or a graphical shell. We're going to focus on command-line shells.

The Shell Command Language is a POSIX standard which has many implementations. Not all shells have the same functionality, so it's important to know what is common amongst all popular shells and what is unique to specific shells. sh, bash, csh, zsh are some common shells.

Manual

Shells include online manual pages, often referred to as man pages, due to the man command which displays them.

View cla-dco.md

The Linux DCO does something very useful. It makes every contribution have an explicit licensing agreement. Want to know if a specific contribution is covered by the DCO? Simply check the commit. Want to check if an entire file is covered? Simply check the history of the file. However, this introduces a burden upon the contributors to agree for every single contribution. It also makes agreeing to updates hard to track. How does a contributor know if their sign-off on their latest commit means the same thing as their sign-off when they read the DCO a year ago? The only way to know is to re-read the DCO or blame the file that contains the DCO to see if there were any changes.

There's another major drawback to the Linux DCO though. You have to know ahead of time that you need a sign-off in your commit. How do you find that? By reading through a ton of documentation. What's the penalty for not knowing? Rebasing. Do you know what that word means to people new to git? It means that they futz around with git, creat

View showhide.md

Expected inline display

Non-animated

Initially block

Initial state .show() .hide() or .toggle() .hide().show() or .toggle().toggle() .show().hide()
default block, no inline has layout, no action none, don't save remove because not saved none, don't save
cascade block, no inline has layout, no action none, don't save remove because not saved none, don't save
default list-item, inline block has layout, no action none, save "block" block, restored from saved none, save "block"
cascade list-item, inline block has layout, no action none, save "block" block, restored from saved none, save "block"
cascade none, inline block has layout, no action none, save "block" block, restored from saved none, save "block"
View dependencies
t2-cli (master *) $ npm ls
t2-cli@0.0.4 /Users/scottgonzalez/Projects/t2-cli
├── async@1.4.2
├── bluebird@2.10.2
├── colors@1.1.2
├─┬ debug@2.2.0
│ └── ms@0.7.1
├── envfile@1.0.0
├─┬ fs-extra@0.18.4
│ ├── graceful-fs@3.0.8
View BlinkM-commands.md
  • Go to RGB Color Now
    • Already implemented; just basic RGB functionality
  • Fade to RGB Color
    • Can be implemented; needs fading logic
  • Fade to HSB Color
    • Can be implemented; needs fading logic and HSB translation
  • Fade to Random RGB Color
    • Can be implemented; needs fading logic
  • Fade to Random HSB Color
    • Can be implemented; needs fading logic
View jquery.webforms.js
/*
* Web Forms 0.4.0 - jQuery plugin
*
* Copyright (c) 2007 - 2008 Scott Gonzalez
*
* Dual licensed under the MIT and GPL licenses:
* http://www.opensource.org/licenses/mit-license.php
* http://www.gnu.org/licenses/gpl.html
*/
View commit-components.js
var spawn = require( "child_process" ).spawn;
var path = "/Users/scottgonzalez/Projects/jquery-release";
var committish = "master";
function getLog( callback ) {
var stdout = "";
var stderr = "";
var child = spawn( "git", [ "log", "--format=%s", committish ], { cwd: path } );
var hadError = false;
View custom-tolerance.js
$.ui.intersect = (function( original ) {
return function( draggable, droppable, toleranceMode ) {
if ( toleranceMode !== "myCustomTolerance" ) {
return original.apply( this, arguments );
}
// custom logic here
};
})( $.ui.intersect );
View pr-merge.md

Update master

First, make sure master is up to date.

git checkout master
git pull upstream master

Rebase your branch