Otto G ottodevs

TODO: Add price informations
TODO: Add App Store Addresses

System Tools

###Chrome

One browser for your computer, phone and tablet

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

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.

Discourse Smartos Install Guide

Guide is working, but it's missing details on how to install pg_trgm extension. https://github.com/fire/pkgsrc-wip/tree/pg_trgm

Recommended Server Hardware

2 GB of RAM
2 GB of swap
2 processor cores

Default

Powerlevel10k

A Common .ruby-version File For Ruby Projects

Background

I've been using this technique in most of my Ruby projects lately where Ruby versions are required:

Create .rbenv-version containing the target Ruby using a definition name defined in ruby-build (example below). These strings are a proper subset of RVM Ruby string names so far...
Create .rvmrc (with rvm --create --rvmrc "1.9.3@myapp") and edit the environment_id= line to fetch the Ruby version from .rbenv-version (example below).

Today I learned about another Ruby manager, rbfu, where the author is using a similar technique with .rbfu-version.

A good commit message looks like this:

Header line: explaining the commit in one line

Body of commit message is a few lines of text, explaining things
in more detail, possibly giving some background about the issue
being fixed, etc etc.

The body of the commit message can be several paragraphs, and
please do proper word-wrap and keep columns shorter than about

	#!/bin/bash
	# node-reinstall
	# credit: http://stackoverflow.com/a/11178106/2083544

	## program version
	VERSION="0.0.13"

	## path prefix
	PREFIX="${PREFIX:-/usr/local}"

	-- Adapted from these sources:
	-- http://peterdowns.com/posts/open-iterm-finder-service.html
	-- https://gist.github.com/cowboy/905546
	--
	-- Modified to work with files as well, cd-ing to their container folder
	on run {input, parameters}
	tell application "Finder"
	set my_file to first item of input
	set filetype to (kind of (info for my_file))
	-- Treats OS X applications as files. To treat them as folders, integrate this SO answer:

	# ============== shell
	# Case-insensitive globbing.
	shopt -s nocaseglob;

	# Do not overwrite files when redirecting using ">", ">&" or "<>".
	# Note that you can still override this with ">\|".
	set -o noclobber;

	# UTF-8 all the way.
	export LC_ALL='en_GB.UTF-8';