Reggi reggi

When you build a community you're creating a culture. That culture will be about more than the code, the modules, or the language. The people you draw in will have their own biases and behaviors that impact the kinds of people you continue to draw as you grow.

Cultures will naturally fight behavior that is divisive. That is, behavior that is divisive to the established members of that community. As a community grows larger it is harder and harder to change what the culture finds acceptable because changing it, even if it is inclusive in nature, is disturbing and divisive to existing membership. Fighting for change in established cultures means dealing with a lot of dismissive language and attacks for the "tone" of your argument.

That is why it is so important that a culture becomes comfortable with aggressively fighting exclusionary behavior. While it is certainly more beneficial to make pro-active steps to increase diversity we cannot be dismissive of the effect that passionate reactions to poor behavior

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

Talk links:

Jennifer Schiffer:

Sorting Algorithms in Javascript

- https://github.com/osresearch/LEDscape
- http://fritzing.org/home/
- https://github.com/kperch/node-open-pixel-control

Trevor Landau:

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.

	BIN = ./node_modules/.bin
	SRC = $(wildcard src/*.coffee)
	LIB = $(SRC:src/%.coffee=lib/%.js)

	build: $(LIB)

	lib/%.js: src/%.coffee
	@mkdir -p $(@D)
	@$(BIN)/coffee -bcp $< > $@

	.col-ms-1,
	.col-ms-2,
	.col-ms-3,
	.col-ms-4,
	.col-ms-5,
	.col-ms-6,
	.col-ms-7,
	.col-ms-8,
	.col-ms-9,
	.col-ms-10,

	// ES6 version using asynchronous iterators, compatible with node v10.0+

	const fs = require("fs");
	const path = require("path");

	async function* walk(dir) {
	for await (const d of await fs.promises.opendir(dir)) {
	const entry = path.join(dir, d.name);
	if (d.isDirectory()) yield* walk(entry);
	else if (d.isFile()) yield entry;

	# Node-WebKit CheatSheet
	# Download: https://github.com/rogerwang/node-webkit#downloads
	# Old Versions: https://github.com/rogerwang/node-webkit/wiki/Downloads-of-old-versions
	# Wiki: https://github.com/rogerwang/node-webkit/wiki
	# How: https://github.com/rogerwang/node-webkit/wiki/How-node.js-is-integrated-with-chromium


	# 1. Run your application.
	# https://github.com/rogerwang/node-webkit/wiki/How-to-run-apps

	#!/bin/sh
	git --no-pager log -n 20 --graph --pretty=format:'%Cred%h%Creset %an: %s - %Creset %C(yellow)%d%Creset %Cgreen(%cr)%Creset' --abbrev-commit --date=relative