vasanthk

System Design Cheatsheet

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

Basic Steps

1. Clarify and agree on the scope of the system

• 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?

jbenet

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

tsmith512

An Introduction

Through both a yearning for familiarity and the knowledge that corporate computer defenestration is a terminal act, I have arduously forged this list of tips, less useful for those on a quest to be an ultimate iUser than for those who want to retain a glimpse, however fleeting, of the Windows/Linux they used to know.

-- [tsmith512][]

adrienbrault

#!/bin/sh

# Credits to:
#  - http://vstone.eu/reducing-vagrant-box-size/
#  - https://github.com/mitchellh/vagrant/issues/343

aptitude -y purge ri
aptitude -y purge installation-report landscape-common wireless-tools wpasupplicant ubuntu-serverguide
aptitude -y purge python-dbus libnl1 python-smartpm python-twisted-core libiw30
aptitude -y purge python-twisted-bin libdbus-glib-1-2 python-pexpect python-pycurl python-serial python-gobject python-pam python-openssl libffi5

sjunior-dev

setw -g xterm-keys on
setw -g mode-mouse on
setw -g mode-keys vi
set -g mouse-select-pane on
set -g set-titles on
set -g history-limit 10000

set -g prefix C-a
bind-key C-a last-window