Quentin McRee qmcree

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

Tutorials & Articles

http://www.smashingmagazine.com/2015/04/21/react-to-the-future-with-isomorphic-apps/

http://blog.andrewray.me/reactjs-for-stupid-people/

http://blog.andrewray.me/flux-for-stupid-people/

https://scotch.io/tutorials/learning-react-getting-started-and-concepts

https://www.codementor.io/reactjs/tutorial/react-js-flux-architecture-tutorialReact

Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded and multipart/form-data.

“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data. Otherwise, use application/x-www-form-urlencoded.”

Matt Bridges' answer in full:

The MIME types you mention are the two Content-Type headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing

	var autocompletes = ['name', 'honorific-prefix', 'given-name',
	'additional-name', 'family-name', 'honorific-suffix',
	'nickname', 'username', 'new-password',
	'current-password', 'organization-title', 'organization',
	'street-address', 'address-line1', 'address-line2',
	'address-line3', 'address-level4', 'address-level3',
	'address-level2', 'address-level1', 'country',
	'country-name', 'postal-code', 'cc-name', 'cc-given-name',
	'cc-additional-name', 'cc-family-name', 'cc-exp',
	'cc-exp-month', 'cc-exp-year', 'cc-csc', 'cc-type',

	var isbns = ['ISBN 0-330-28498-3',
	'ISBN 1-58182-008-9',
	'ISBN 2-226-05257-7',
	'ISBN 3-7965-1900-8',
	'ISBN 4-19-830127-1',
	'ISBN 5-85270-001-0',
	'ISBN 978-600-119-125-1',
	'978-601-7151-13-3',
	'ISBN 978-602-8328-22-7',
	'ISBN 978-603-500-045-1',

	# The command finds the most recent tag that is reachable from a commit.
	# If the tag points to the commit, then only the tag is shown.
	# Otherwise, it suffixes the tag name with the number of additional commits on top of the tagged object
	# and the abbreviated object name of the most recent commit.
	git describe

	# With --abbrev set to 0, the command can be used to find the closest tagname without any suffix:
	git describe --abbrev=0

	# other examples

	<?php

	class Math {

	/**
	* The base.
	*
	* @var string
	*/
	private static $base = '0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ';

	# -- coding: utf-8 --
	import json
	import urllib2
	from M2Crypto import X509
	from base64 import b64decode
	from M2Crypto.Err import M2CryptoError

	SNS_MESSAGE_TYPE_SUB_NOTIFICATION = "SubscriptionConfirmation"
	SNS_MESSAGE_TYPE_NOTIFICATION = "Notification"
	SNS_MESSAGE_TYPE_UNSUB_NOTIFICATION = "UnsubscribeConfirmation"

	#!/bin/bash

	# Vagrant CentOS6 boxes
	# CentOS 6.4 x64 https://github.com/2creatives/vagrant-centos/releases/download/v6.4.2/centos64-x86_64-20140116.box
	# CentOS 6.5 x64 https://github.com/2creatives/vagrant-centos/releases/download/v6.5.3/centos65-x86_64-20140116.box

	# Update
	sudo yum -y update

	# Add Development tools

	// default exports
	export default 42;
	export default {};
	export default [];
	export default foo;
	export default function () {}
	export default class {}
	export default function foo () {}
	export default class foo {}