Kyle Kelley rgbkrk

###Title

Academic publishing using Git and GitHub

###Additional faciliators

Jessica Lord
Chrissie Brodigan
Andrew Nesbitt
Karthik Ram

Channels Are Not Enough

... or Why Pipelining Is Not That Easy

Golang Concurrency Patterns for brave and smart.

By @kachayev

Intro

We’re looking for a full-stack developer ready to help us build the next platform for Developer Experience at Rackspace. We need a leader to drive engineering decisions for the front and back-end, as well as implement significant portions of our Developer Portal. Working effectively as a remote employee in a collaborative environment, especially on open-source software, is an absolute must-have skill.

The Developer Experience team is focused on making the end-to-end experience for developers on the Rackspace Cloud awesome. From community & outreach to docs, tools & SDKs, our team is on the front lines for engaging with developers who are building modern cloud applications.

Ideal candidates should have experience with contemporary front-end frameworks, including but not limited to Ember, React, Angular and Backbone. Additionally, candidates should have experience with back-end frameworks for building modern web applications. Representative examples might include Python a

Reposted from Qiita

For almost a year now, I've been using this "flux" architecture to organize my React applications and to work on other people's projects, and its popularity has grown quite a lot, to the point where it shows up on job listings for React and a lot of people get confused about what it is.

Why I'm tired of using and teaching flux

There are a billion explainations on the internet, so I'll skip explaining the parts. Instead, let's cut to the chase -- the main parts I hate about flux are the Dispatcher and the Store's own updating mechanism.

If you use a setup similar to the examples in facebook/flux, and you use flux.Dispatcher, you probably have this kind of flow:

	package backends

	import (
	"fmt"
	"io"
	"strings"
	"sync"
	"time"

	"github.com/docker/libswarm"

	#!/bin/bash

	# usage: nbgrep 'pattern'

	SEARCHPATH=~/work/

	# 'jq' technique lifted with gratitude
	# from https://gist.github.com/mlgill/5c55253a3bc84a96addf

	# Break on newlines instead of any whitespace

	#!/usr/bin/env python

	""" A cross-platform (POSIX, at least) tool to list running IPython Notebooks
	and their working directories.

	This code will be incredibly simpler to write as of IPython 3.0, so
	contains numerous workarounds to make it work on 2.x.

	Thanks to @takluyver for the suggestions for improvement.

	#!/usr/bin/env python
	import dill
	import sys


	payload_filename = sys.argv[1]

	if len(sys.argv) > 2:
	print('Restoring __main__ context')
	main_filename = sys.argv[2]

	#!/bin/bash

	set -o errexit

	# This script assumes you're running it initially as root and you've created it with a key pair. If you
	# haven't, you'll be locked out of your server.

	if [ -z "$1" ]; then
	echo "Usage: $0 NON_ROOT_USER"
	echo "Example: $0 foo"

	FROM ipython/notebook

	MAINTAINER Alex Kerney <abk@mac.com>

	RUN apt-get install -y -q python-numpy python-scipy python-matplotlib python-pandas python-sympy python-nose