coliver

== 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.

mtnygard

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

tmm1

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.

prwhite

# 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

bkeepers

#!/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

ubermajestix

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

Main{

  argument("youtube_url")

byllc

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

sentientmonkey

#!/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..."

aphyr

Some people think that configuration should not be "Turing complete"; others think the configuration language should be as expressive as possible--so much so that it amounts to a programming language itself.

I assert that configuration files which are not Turing complete (or, perhaps a more useful distinction, are not "sufficiently complex languages") are in practice extended to be that complex; and when that happens, the result is often more difficult to understand than if the language were more powerful to start with.

snipe

<!--
* * * * * * * * * * * * * * * * * * * * * * * * *  
*                                               *
* /     \             \            /    \       *
*|       |             \          |      |      *
*|       `.             |         |       :     *
*`        |             |        \|       |     *
* \       | /       /  \\\   ____ \\       :    *
*  \      \/   ___~~          ~____| \     |    *
*   \      \__~                    ~__\    |    *