jallspaw

Adrian -

I appreciate that you spent time in writing this post. I know I've been up until 2am writing similarly long ones as well. I will take responsibility for having what is likely an irrational response (I blame Twitter for that) to the term "NoOps", but I invite you to investigate why that might be. I'm certainly not the only one who feels this way, apparently, and thus far have decided this issue is easily the largest distraction in my field I've encountered in recent years. I have had the option to simply ignore my opposition to the term, and just let the chips fall where they may with how popular the term "NoOps" may or may not get. I have obviously not taken that option in the past, but I plan to in the future.

You're not an analyst saying "NoOps". Analysts are easy (for me) to ignore, because they're not practitioners. We have expectations of engineering maturity from practitioners in this field of web engineering, especially those we consider leaders. I don't have any expectations from analysts,

GregSutcliffe

class test {

  # Create the admin repo in the inital call, using defaults
  class { 'gitolite': }

  # Optionally override with your own config and keys
  #class { 'gitolite': }
  #  authfile => 'puppet:///modules/test/admin.conf',
  #  keydir   => 'puppet:///modules/test/admin-keys',
  #}  

GregSutcliffe

#!/bin/bash
#
# IRC notification post-receive hook.
# Based on https://wiki.icinga.org/display/community/GIT+Commit+Bot
# 
# Author:      Mikael Fridh <frimik@gmail.com>
# Modified by: Greg Sutcliffe <gsutcliffe@ibahn.com
#
# This script pulls out the commit information and sends it to 
# the RemoteCtl plugin in rbot via quassel.office:7268 using

bhenerey

In a perfect world, where things are done well, not just quickly, I would expect to find the following when joining the company:

Documentation

• Accurate / up-to-date systems architecture diagram

• Accurate / up-to-date network diagram

• Out-of-hours support plan

• Incident management plan

purcell

# Monkeypatch fix for https://github.com/rack/rack/issues/386 achieved by
# applying https://github.com/rack/rack/commit/2dfe94071497678c15cfcd8e63663d92f82958e5

raise "remove this fix" if Gem.loaded_specs["rack"].version > Gem::Version.new("1.4.1")

module Rack
  module Utils
    def parse_query(qs, d = nil)
      params = KeySpaceConstrainedParams.new

rkh

# encoding: binary

# Removes any bytes from a string that are not valid UTF-8
class Cleaner
  attr_reader :bytes, :buffer, :outstanding

  def self.clean(str)
    new.tap { |c| c << str }.to_s
  end

mikebaldry

class Array
  def expand_ranges
    self.collect { |wtf| wtf.is_a?(Range) ? wtf.to_a : wtf }.flatten
  end
end

[1..15, 19, 21..25].expand_ranges.each { |i| puts i }

ohadlevy

#!/usr/bin/env ruby

require 'rubygems'
require 'rest-client'
require 'json'
client = RestClient::Resource.new('http://0.0.0.0:3000',
                                  :user     => 'admin',
                                  :password => 'changeme',
                                  :headers  => { :accept => :json })

benders

! --------------------------------------------------------------------------------
! This example configuration shows what WE did to get Amazon VPC working with our
! ASAs.  We use version 8.3(1). This config has not been reviewed or otherwise
! blessed in any way by anyone at Amazon.  YMMV.
! 
! It differs from Amazon's supplied config by using two different sets of
! crypto maps and ACLs, so it brings both tunnels up simultaneously.
!
! For the purposes of the example, the physical datacenter network is 172.16.1.0/24
! and the VPC is 10.0.0.0/16.

dypsilon

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

---