Renzo Canepa rcanepa

The introduction to Reactive Programming you've been missing

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.

Commit Message Conventions

These rules are adopted from the AngularJS commit conventions.

Goals
Generating CHANGELOG.md
- Recognizing unimportant commits
- Provide more information when browsing the history
Format of the commit message
Subject line

Rich Hickey on becoming a better developer

Rich Hickey • 3 years ago

Sorry, I have to disagree with the entire premise here.

A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.

Mastery comes from a combination of at least several of the following:

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

Moved to https://github.com/nobssoftware/nocommit

Things that programmers don't know but should

(A book that I might eventually write!)

Gary Bernhardt

I imagine each of these chapters being about 2,000 words, making the whole book about the size of a small novel. For comparison, articles in large papers like the New York Times average about 1,200 words. Each topic gets whatever level of detail I can fit into that space. For simple topics, that's a lot of space: I can probably walk through a very basic, but working, implementation of the IP protocol.

	(Chapters marked with * are already written. This gets reorganized constantly
	and 10 or so written chapters that I'm on the fence about aren't listed.)

	Programmer Epistemology
	* Dispersed Cost vs. Reduced Cost
	* Verificationist Fallacy
	* Mistake Metastasis
	The Overton Window
	Epicycles All The Way Down
	The Hyperspace Gates Were Just There

	(require '[schema.core :as s])
	(require '[schema.coerce :as coerce])
	(require '[schema.utils :as utils])

	(defn filter-schema-keys
	[m schema-keys extra-keys-walker]
	(reduce-kv (fn [m k v]
	(if (or (contains? schema-keys k)
	(and extra-keys-walker
	(not (utils/error? (extra-keys-walker k)))))

	// Promise.all is good for executing many promises at once
	Promise.all([
	promise1,
	promise2
	]);

	// Promise.resolve is good for wrapping synchronous code
	Promise.resolve().then(function () {
	if (somethingIsNotRight()) {
	throw new Error("I will be rejected asynchronously!");

	CREATE EXTENSION btree_gist;

	CREATE TABLE room_reservations (
	room_id integer,
	reserved_at timestamptz,
	reserved_until timestamptz,
	canceled boolean DEFAULT false,
	EXCLUDE USING gist (
	room_id WITH =, tstzrange(reserved_at, reserved_until) WITH &&
	) WHERE (not canceled)