Rob Skillington robskillington

The prep-script.sh will setup the latest Node and install the latest perf version on your Linux box.

When you want to generate the flame graph, run the following (folder locations taken from install script):

sudo sysctl kernel.kptr_restrict=0
# May also have to do the following:
# (additional reading http://unix.stackexchange.com/questions/14227/do-i-need-root-admin-permissions-to-run-userspace-perf-tool-perf-events-ar )
sudo sysctl kernel.perf_event_paranoid=0

Architectural Questions

Are responsibilities well defined?
Are the collaborations well defined?
Is coupling minimized?
Can you identify potential duplication?
Are interface definitions and constraints acceptable?
Can modules access needed data—when needed?

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

Moving to ES6 from CoffeeScript

I fell in love with CoffeeScript a couple of years ago. Javascript has always seemed something of an interesting curiosity to me and I was happy to see the meteoric rise of Node.js, but coming from a background of Python I really preferred a cleaner syntax.

In any fast moving community it is inevitable that things will change, and so today we see a big shift toward ES6, the new version of Javascript. It incorporates a handful of the nicer features from CoffeeScript and is usable today through tools like Babel. Here are some of my thoughts and issues on moving away from CoffeeScript in favor of ES6.

While reading I suggest keeping open a tab to Babel's learning ES6 page. The examples there are great.

Punctuation

Holy punctuation, Batman! Say goodbye to your whitespace and hello to parenthesis, curly braces, and semicolons again. Even with the advanced ES6 syntax you'll find yourself writing a lot more punctuatio

In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.

Conceptual Model

At the moment GraphQL allows 2 types of queries:

query
mutation

Reference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.

Swift Concurrency Manifesto

Author: Chris Lattner

Chinese Translation by Jason Yu

	Linux - create "Default (Linux).sublime-mousemap" in ~/.config/sublime-text-3/Packages/User
	Mac - create "Default (OSX).sublime-mousemap" in ~/Library/Application Support/Sublime Text 3/Packages/User
	Win - create "Default (Windows).sublime-mousemap" in %appdata%\Sublime Text 3\Packages\User

	[
	{
	"button": "button1",
	"count": 1,
	"modifiers": ["ctrl"],
	"press_command": "drag_select",

	#!/bin/sh

	# Change these settings to match what you are wanting to do
	FILE=/File/To/Copy
	SERVER=localhost
	PATH=/Where/To/Put/File

	OPTIONS=`vagrant ssh-config \| awk -v ORS=' ' '{print "-o " $1 "=" $2}'`

	scp ${OPTIONS} $FILE vagrant@$SERVER:$PATH

	var fs = require('fs');

	var infile = process.argv[2];

	if (!infile) return console.log("need infile");

	var data = fs.readFileSync(infile, 'utf8').split('\n');
	var outlines = [];

	data.forEach(function(item) {

	package copy_vs_append

	import (
	"testing"
	)

	func TestCopy(t *testing.T) {
	y := doCopy(true, false)
	if len(y) != 1000 {
	t.Fatalf("Expected len(y) to be 1000 but was %d", len(y))