Tristan Rentz terentz

System Design Cheatsheet

use case : the things your system needs to be do.

constraints : the things your system will have to consider to be able to do stuff

Picking the right architecture = Picking the right battles + Managing trade-offs

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

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.

A current list of styleguide genorators useful for creating your own "bootstrap".

	#!/bin/bash
	#
	# START CONFIG
	#
	# Change driveletter below if windows is installed on something other than the C drive
	driveletter=c
	#
	# END CONFIG
	#
	#

	var fs = {
	read: (filename, cb, err) => {
	navigator.webkitPersistentStorage.requestQuota(0, (bytes) => {
	window.webkitRequestFileSystem(PERSISTENT, bytes, (fs) => {
	fs.root.getFile(filename, {},
	(entry) => {
	entry.file((file) => {
	var reader = new FileReader();
	if(err)
	reader.onerror = err;

	#!/bin/sh

	set -e
	set -x

	for package in $(npm -g outdated --parseable --depth=0 \| cut -d: -f2 \| sed 's/@.*//g')
	do
	npm -g install "$package@latest"
	done

	the best way (I've found) to completely uninstall node + npm is to do the following:

	go to /usr/local/lib and delete any node and node_modules
	go to /usr/local/include and delete any node and node_modules directory
	if you installed with brew install node, then run brew uninstall node in your terminal
	check your Home directory for any local or lib or include folders, and delete any node or node_modules from there
	go to /usr/local/bin and delete any node executable
	You may need to do the additional instructions as well:

	sudo rm /usr/local/bin/npm