jiuks

rm-header {
    margin-left: -25px;
}

.rm-header img {
    margin-top: 10px;
    float: right;
    height: 50px;
}

jiuks

set p to POSIX path of "/Users/jonmead/Dropbox (Personal)/notes/todo.md"
set input_file to POSIX path of p
set l to paragraphs of (do shell script "grep . " & "\"" & input_file & "\"")
tell application "OmniFocus" to tell document 1
	repeat with v in l
		make new inbox task with properties {name:v}
	end repeat
end tell

jiuks

The primary difference between making unhappy customers happy and making happy customers even happier is the point of initiation. With unhappy customers, even if you did not know why they were unhappy before speaking with them, you can be certain that you soon will learn the reason for their unhappiness. Once you know why they are unhappy, it is relatively easy to plot a course of action to convert them into a happy customer.

jiuks

Gists are a feature of git, and a nice way to share snippets of code or short documents. They benefit from being private or public, and can be cloned etc like standard git repositories.

To post a git from the command line there is a tool available called gist, installed with brew:

brew install gist

Then set your git username + password:

git config --global github.user "jbloggs"
git config --global github.password "welcome1"

jiuks

My background is writing code and one of the most useful things I learnt was [Don't Repeat Yourself][wikipedia], this was something I read in a book called the [Pragmatic Programmer][pragprog] which I would thoroughly recommend to anyone today who has anything to do with software.

What interests me now is how we should relate this to the Business Intelligence, Data Integration and Analytics worlds, and one conversation I had yesterday reminded me of several other conversations that I have had over the years: how can we automate ETL and Business Intelligence meta data generation?

A traditional Data Warehousing project will follow some or all of these steps, whether they do it in repeated [Agile][wikipedia 2] sprints, or one big [Waterfall Model][wikipedia 3]:

• elicit, document and validate requirements.
• design logical and then physical model.
• indentify source data attribute(s) and transformations for target model.
• write ETL packages to move code through whichever data warehouse architecture you a

jiuks

# bind tmux commands to Ctrl-A for Vim compatibility
# and better ergonomics :)
unbind C-b
set -g prefix C-a

# Ctrl-A Ctrl-A switches to last window
bind C-a last-window
bind a send-prefix

# Rebind Ctrl-| to split the window horizontally [  |  ]

jiuks

#!/bin/bash
# ====================================================================
# This is the tmux configuration I use for setting up my Ruby on Rails 
# Tutorial session
# 

BASE="~/apps/envtest"
cd $BASE

tmux start-server