Paul Cook cookavich

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

This is a plain-text version of Bret Victor’s reading list. It was requested by hf on Hacker News.

Highly recommended things!

This is my five-star list. These are my favorite things in all the world.

A few of these works have had an extraordinary effect on my life or way of thinking. They get a sixth star. ★

codegolf JS

Mini projects by Maxime Euzière (xem), subzey, Martin Kleppe (aemkei), Mathieu Henri (p01), Litterallylara, Tommy Hodgins (innovati), Veu(beke), Anders Kaare, Keith Clark, Addy Osmani, bburky, rlauck, cmoreau, maettig, thiemowmde, ilesinge, adlq, solinca, xen_the,...

(For more info and other projects, visit http://xem.github.io)

(Official Slack room: http://jsgolf.club / join us on http://register.jsgolf.club)

Architecture in Elm

This document is a collection of concepts and strategies to make large Elm projects modular and extensible.

We will start by thinking about the structure of signals in our program. Broadly speaking, your application state should live in one big foldp. You will probably merge a bunch of input signals into a single stream of updates. This sounds a bit crazy at first, but it is in the same ballpark as Om or Facebook's Flux. There are a couple major benefits to having a centralized home for your application state:

There is a single source of truth. Traditional approaches force you to write a decent amount of custom and error prone code to synchronize state between many different stateful components. (The state of this widget needs to be synced with the application state, which needs to be synced with some other widget, etc.) By placing all of your state in one location, you eliminate an entire class of bugs in which two components get into inconsistent states. We also think yo

React (Virtual) DOM Terminology

In React's terminology, there are five core types that are important to distinguish:

ReactElement / ReactElement Factory
ReactNode
ReactComponent / ReactComponent Class

React Elements

	[T]he difference between a bad programmer and a
	good one is whether he considers his code or his
	data structures more important. Bad programmers
	worry about the code. Good programmers worry about
	data structures and their relationships.
	-- Linus Torvalds
	~~~
	Clarity and brevity sometimes are at odds.
	When they are, I choose clarity.
	-- Jacob Kaplan-Moss

	'use strict';

	var q = require('q');

	/**
	* Constructs a function that proxies to promiseFactory
	* limiting the count of promises that can run simultaneously.
	* @param promiseFactory function that returns promises.
	* @param limit how many promises are allowed to be running at the same time.
	* @returns function that returns a promise that eventually proxies to promiseFactory.

	#add 'node_modules' to .gitignore file

	git rm -r --cached node_modules
	git commit -m 'Remove the now ignored directory node_modules'
	git push origin <branch-name>

	'use strict';

	var React = require('react'),
	classSet = require('react/lib/cx'),
	_ = require('underscore');

	var ClassNameMixin = {
	propTypes: {
	className: React.PropTypes.string,
	context: React.PropTypes.string

	'use strict';

	var React = require('react');

	function createAsyncHandler(getHandlerAsync, displayName) {
	var Handler = null;

	return React.createClass({
	displayName: displayName,