Joseph Tingsanchali lolptdr

Screencasting Framework

The following document is a written account of the Code School screencasting framework. It should be used as a reference of the accompanying screencast on the topic.

Why you should care about screencasting?

You're probably aren't going to take the time to read this document if you're not interested, but there are a lot of nice side effects caused by learning how to create quality screencasts.

Communicating more effectively - At Envy Labs we produce screencasts for our clients all the time. Whether it's demoing a new feature or for a presentation for an invester, they're often much more effective and pleasent than a phone call or screen sharing.

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 "[email protected]"

Using Git

Global Settings

Related Setup: https://gist.github.com/hofmannsven/6814278

Related Pro Tips: https://ochronus.com/git-tips-from-the-trenches/

ECMAScript 6 ^{git.io/es6features}

Introduction

ECMAScript 6 is the upcoming version of the ECMAScript standard. This standard is targeting ratification in June 2015. ES6 is a significant update to the language, and the first update to the language since ES5 was standardized in 2009. Implementation of these features in major JavaScript engines is underway now.

See the draft ES6 standard for full specification of the ECMAScript 6 language.

ES6 includes the following new features:

arrows
classes

Install your client-side programs:

	var mixin = require('mixin');

	class Cyclist {
	ride() {
	console.log(`${this.name} is riding`);
	}
	}

	class Swimmer {
	swim() {

	#!/bin/bash

	echo ""
	echo "=========================================================================="
	echo "= Pentest Attack Machine Setup ="
	echo "= Based on the setup from The Hacker Playbook ="
	echo "=========================================================================="
	echo ""

	# Prepare tools folder

	How to write the perfect pull request

	January 21, 2015 Keavy McMinn keavy Engineering
	As a company grows, people and projects change. To continue to nurture the culture we want at GitHub, we've found it useful to remind ourselves what we aim for when we communicate. We recently introduced these guidelines to help us be our best selves when we collaborate on pull requests.

	Approach to writing a Pull Request

	Include the purpose of this Pull Request. For example:
	This is a spike to explore…
	This simplifies the display of…

	#!/usr/bin/env ruby

	require 'fileutils'
	require 'mkmf'

	USERNAME = `whoami`.chomp
	HOME_DIR = File.expand_path('~/')
	DOT_DIR = File.expand_path('~/.mks-dotfiles')
	MKS_DIR = File.expand_path('~/code/mks')
	DOT_FILES = ['.gitignore', '.gitconfig', '.zshrc']

	// Short-circuit examples
	var one = 10 \|\| 20
	console.log("1.", one)

	var two = false \|\| 30
	console.log("2.", two)

	var three = true \|\| 40 \|\| 50
	console.log("3.", three)