h srhrshr

Prereq:

apt-get install zsh
apt-get install git-core

Getting zsh to work in ubuntu is weird, since sh does not understand the source command. So, you do this to install zsh

wget https://github.com/robbyrussell/oh-my-zsh/raw/master/tools/install.sh -O - | zsh

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

This can reduce files to ~15% of their size (2.3M to 345K, in one case) with no obvious degradation of quality.

ghostscript -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/printer -dNOPAUSE -dQUIET -dBATCH -sOutputFile=output.pdf input.pdf

Other options for PDFSETTINGS:

/screen selects low-resolution output similar to the Acrobat Distiller "Screen Optimized" setting.
/ebook selects medium-resolution output similar to the Acrobat Distiller "eBook" setting.
/printer selects output similar to the Acrobat Distiller "Print Optimized" setting.
/prepress selects output similar to Acrobat Distiller "Prepress Optimized" setting.

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

	#!/usr/bin/env ruby

	# ************************************************************************
	# A simple ruby script to read the index file of any git repository
	# and dump its contents to a file in a readable format.
	#
	# This is totally a study tool, written when I was trying to understand
	# the git internals.
	#
	# The file strucutre specification considered is this :

	<cities>
	<state>
	<name>Alabama</name>
	<city>Abbeville</city>
	<number>1</number>
	</state>
	<state>
	<name>Alabama</name>
	<city>Adamsville</city>
	<number>1</number>

	var fn = function(arg1, arg2) {
	var str = '<p>aap ' + this.noot + ' ' + arg1 + ' ' + arg2 + '</p>';
	document.body.innerHTML += str;
	};
	var context = {
	'noot': 'noot'
	};
	var args = ['mies', 'wim'];

	// Calls a function with a given 'this' value and arguments provided individually.

	import os
	import numpy
	from pandas import DataFrame
	from sklearn.feature_extraction.text import CountVectorizer
	from sklearn.naive_bayes import MultinomialNB
	from sklearn.pipeline import Pipeline
	from sklearn.cross_validation import KFold
	from sklearn.metrics import confusion_matrix, f1_score

	NEWLINE = '\n'

	#!/bin/bash

	# Bash script to install latest version of ffmpeg and its dependencies on Ubuntu 12.04 or 14.04
	# Inspired from https://gist.github.com/faleev/3435377

	# Remove any existing packages:
	sudo apt-get -y remove ffmpeg x264 libav-tools libvpx-dev libx264-dev

	# Get the dependencies (Ubuntu Server or headless users):
	sudo apt-get update