Beau Dacious nocash

The rights of the user/client (referred to as “data subject” in the regulation) that I think are relevant for developers are:

the right to erasure (the right to be forgotten/deleted from the system)
right to restriction of processing (you still keep the data, but mark it as “restricted” and don’t touch it without further consent by the user),
the right to data portability (the ability to export one’s data in a machine-readable format),
the right to rectification (the ability to get personal data fixed),
the right to be informed (getting human-readable information, rather than long terms and conditions),
the right of access (the user should be able to see all the data you have about them).

Band-aid fix for exceeding max open files limit on OSX.

To check the current limits on your Mac OS X system, run:

launchctl limit maxfiles

	<h1>Testing display of HTML elements</h1>

	<h2>This is 2nd level heading</h2>
	<p>This is a test paragraph.</p>
	<h3>This is 3rd level heading</h3>
	<p>This is a test paragraph.</p>
	<h4>This is 4th level heading</h4>
	<p>This is a test paragraph.</p>
	<h5>This is 5th level heading</h5>
	<p>This is a test paragraph.</p>

	#!/bin/bash -e

	ack_args=$@
	git_ref=$( git which-master )
	pattern='TODO\|NOTE\|XXX\|placehold\.it\|TK\|tbd\|console\.log'

	function committed_files {
	git diff ${git_ref}..HEAD --diff-filter=ACMX -G"$pattern" --name-only
	}

	#!/usr/bin/env ruby

	require 'fileutils'

	REM_PATTERN = /([\d.-]+)rem\b/

	current_size, target_size, *file_paths = ARGV

	def trim_num(num)
	num.to_f == num.to_i ?

	#!/bin/bash
	set -e
	current=`git symbolic-ref --quiet --short HEAD`
	exclude="^(master\|develop)"


	git fetch origin
	git checkout master
	git reset --hard origin/master
	git branch --merged origin/master \

	[alias]
	br- = "!f() { git branch $(dasherize \"$@\"); }; f"
	cob- = "!f() { git checkout -b $(dasherize \"$@\"); }; f"