Brian Shirai brixen

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

	### Keybase proof

	I hereby claim:

	* I am brixen on github.
	* I am brixen (https://keybase.io/brixen) on keybase.
	* I have a public key whose fingerprint is FA8D BC7C 3EE8 7517 8E3E D4D9 27DB C120 112E 82C2

	To claim this, I am signing this object:

	# To run this benchmark
	# $ git clone https://github.com/devs-ruby/devs .
	# $ gem build devs.gemspec && gem install devs-0.5.1.gem
	# $ gem install devs-models
	# $ git clone https://github.com/devs-ruby/devstone .
	# $ gem build devs.gemspec && gem install devstone-0.0.1.gem

	require 'devstone'

	opt_base = {

	(Chapters marked with * are already written. This gets reorganized constantly
	and 10 or so written chapters that I'm on the fence about aren't listed.)

	Programmer Epistemology
	* Dispersed Cost vs. Reduced Cost
	* Verificationist Fallacy
	* Mistake Metastasis
	The Overton Window
	Epicycles All The Way Down
	The Hyperspace Gates Were Just There

	failbowl:selecta(scoring_redesign) $ ruby ../readygo/readygo.rb --compare benchmark.rb
	.!.!.!.!.!.!.!.!..!.!.!.!.!.!.!.!.!.!...!.!.!.!.!.!.!.!.............................................................................................................

	filtering non-matching
	Baseline: \| X-----------\|
	Current: \| X--------- \|
	0 6.848 ms

	filtering matching exactly
	Baseline: \| X-------------------\|

	package main

	import (
	"github.com/streadway/amqp"
	"encoding/json"
	"log"
	"os"
	"fmt"
	"time"
	)

	This tool is used to compare microbenchmarks across two versions of code. It's
	paranoid about nulling out timing error, so the numbers should be meaningful.
	It runs the benchmarks many times, scaling the iterations up if the benchmark
	is extremely short, and it nulls out its own timing overhead while doing so. It
	reports results graphically with a text interface in the terminal.

	You first run it with --record, which generates a JSON dotfile with runtimes
	for each of your benchmarks. Then you change the code and run again with
	--compare, which re-runs and generates comparison plots between your recorded
	and current times. In the example output, I did a --record on the master

	#!/usr/bin/env bash

	siege -c 10 -b -t 30s http://localhost:9393

	source 'https://rubygems.org'

	gem 'benchmark-ips'
	gem 'json'
	gem 'multi_json'
	gem 'oj', platform: [:mri, :rbx]
	gem 'yajl-ruby', platform: [:mri, :rbx], require: 'yajl'
	gem 'jrjackson', platform: :jruby
	gem 'gson', platform: :jruby