Nathan Witmer zerowidth

Reciprocal Needs in the Employment Relation

We can look at two sides of the management coin: What do the individuals get out of it? And what benefit does the whole system derive from it?

I will disregard any benefits that accrue to managers just by holding the position of managing. Those are just circular logic. Circular logic abounds in discussions of management and hierarchy. For example, consider status reports. It will be said that status reports are necessary so managers know what their employees are working on. It’s

Vim and Git in Code Demos

I want to give a code demo that shows progression of the code. I thought it would be great if I could craft the series of commits on a branch and have a single vim keystroke that would checkout the next (or previous) commit and force my buffers to reload. That would allow me to show one commit, then give me the freedom to live code how the next step is done, but when I advance to the next commit I know I'll have working code. It's like a safety harness for live coding.

Here's how it's supposed to work:

I created a test_forward branch, and, yeah, it's hardcoded in the vimscript :-(
Then I created 3 consecutive commits with one line changes in my README
optional: I used "git tag $tag_name" to give a friendly name in my bash prompt for each commit (I wish the fugitive statusline would use it too though)
I checked out the 1st of the demo commits

	#!/usr/bin/env ruby

	require 'logger'

	# rotatelogs required...
	# http://httpd.apache.org/docs/2.2/programs/rotatelogs.html
	logger = Logger.new("\|rotatelogs ./foo.log.%Y-%m-%d-%H 3600", 0, 0)

	10.times do
	logger.error "testing..."

	The right side of my brain helps me make things rhyme
	The left side keeps it all in time
	Whats in between helps me learn and perceive
	But do I Believe,
	I have the answers I need?

	Ours is a culture with pride in logic and reason
	But do the ones and zeros truly have meaning
	Does your software have feelings?
	Stay Tuned

	#! /usr/bin/env ruby
	require 'rubygems'
	require 'main'
	require 'pathname'
	require 'fileutils'

	Main{

	argument("youtube_url")

	#!/bin/sh
	#
	# Requires the `t` gem: https://github.com/sferik/t
	#
	# gem install t
	#

	if [ -z $(t lists \| grep -i githubbers) ]
	then
	t list create GitHubbers

	# Add the following 'help' target to your Makefile
	# And add help text after each target name starting with '\#\#'

	help: ## Show this help.
	@fgrep -h "##" $(MAKEFILE_LIST) \| fgrep -v fgrep \| sed -e 's/\\$$//' \| sed -e 's/##//'

	# Everything below is an example

	target00: ## This message will show up when typing 'make help'
	@echo does nothing

	Ruby 2.1.0 in Production: known bugs and patches

	Last week, we upgraded the github.com rails app to ruby 2.1.0 in production.
	While testing the new build for rollout, we ran into a number of bugs. Most of
	these have been fixed on trunk already, but I've documented them below to help
	anyone else who might be testing ruby 2.1 in production.

	@naruse I think we should backport these patches to the ruby_2_1 branch and
	release 2.1.1 sooner rather than later, as some of the bugs are quite critical.
	I'm happy to offer any assistance I can to expedite this process.

	== Rules ==
	On Infrastructure
	-----------------
	There is one system, not a collection of systems.
	The desired state of the system should be a known quantity.
	The "known quantity" must be machine parseable.
	The actual state of the system must self-correct to the desired state.
	The only authoritative source for the actual state of the system is the system.
	The entire system must be deployable using source media and text files.

	-- Response to https://twitter.com/mfeathers/status/495979138365149184
	-- Based on http://git.zx2c4.com/spark/tree/spark.c

	import System.IO (hPutStrLn, stderr)
	import System.Environment (getArgs)
	import qualified Data.ByteString as B
	import qualified Data.ByteString.Char8 as C

	main :: IO ()
	main = do