Ben Anderson banderson

Introduction

An introduction to curl using GitHub's API.

The Basics

Makes a basic GET request to the specifed URI

curl https://api.github.com/users/caspyin

Ok, I geeked out, and this is probably more information than you need. But it completely answers the question. Sorry. ☺

Locally, I'm at this commit:

$ git show
commit d6cd1e2bd19e03a81132a23b2025920577f84e37
Author: jnthn <[email protected]>
Date:   Sun Apr 15 16:35:03 2012 +0200

When I added FIRST/NEXT/LAST, it was idiomatic but not quite so fast. This makes it faster. Another little bit of masak++'s program.

Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 µs
SSD random read ........................ 150,000 ns  = 150 µs

Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h or --help depending on your psql version):

-E: will describe the underlaying queries of the \ commands (cool for learning!)
-l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)

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.

React-Core Meeting Notes 2015-03-20

Note: This is the first time we're sharing meeting notes publicly. The primary reason we haven't shared these is because we often mix public discussions with matters that are Facebook specific and should not be public. We're really trying to be more open about our development process and what's happening inside the project so moving forward, we'll be sharing meeting notes. While most of us do work at Facebook, we're committed to this being an open project - for now we'll filter out the private notes from the public notes. Hopefully we can make it possible for these meetings to be open to any who wish to attend.

Attendees:

@zpao
@sebmarkbage
@spicyj
@jeffmo

	// JS Module Pattern:
	// http://j.mp/module-pattern

	// Redefine: $, window, document, undefined.
	var APP = (function($, window, document, undefined) {
	// Automatically calls all functions in APP.init
	$(document).ready(function() {
	APP.go();
	});

	(function(){
	var log = console.log;

	console.log = function(str) {
	var css = 'background: linear-gradient(to right, red, yellow, lime, aqua, blue, fuchsia, red); color: white; font-weight: bold;';
	var args = Array.prototype.slice.call(arguments);
	args[0] = '%c' + args[0];
	args.splice(1,0,css);
	return log.apply(console, args);
	}

	var Toggler = require('./toggler');
	var React = require('react/addons');
	var assert = chai.assert;
	var Simulate = React.addons.TestUtils.Simulate

	describe('Toggler', function(){

	var toggler, el;

	beforeEach(function() {

	/**
	* Page layout, reused across multiple Page components
	* @jsx React.DOM
	*/

	var React = require('react');
	var ExecutionEnvironment = require('react/lib/ExecutionEnvironment');
	var Navigation = require('../components/Navigation.jsx');

	var DefaultLayout = React.createClass({