stilist

#!/usr/bin/env bash

set -euo pipefail

destination_branch_name="${1:-merge-pile}"
branch_list="${2:-branch-list.txt}"

if [[ ! -f "${branch_list}" ]] ; then
  echo "ERROR: Branch list file (${branch_list}) doesn't exist" >&2
  exit 1

stilist

#!/bin/bash

set -euo pipefail

log_directory="${1:-/var/log}"

year="20[[:digit:]]{2}"
day="[[:digit:]]{2}"
month_num="[[:digit:]]{1,2}"
month_alpha="[[:upper:]][[:lower:]]{2}"

stilist

See https://gist.github.com/stilist/dd88f71557c5231d374ce36645a065de for previous context.

stilist

This is a small revision to the move_cursor_to_start_of_ps1 function described in ‘When did I run that command?’. The original relies on a specific number of lines in PS1; this works with an arbitrary number of lines.

The original code works correctly for the PS1 provided in the article, but my PS1 has an additional line, and I wanted to avoid using a magic number in case I change my PS1 in the future.

stilist

// You can run this from your browser's JavaScript console.
console.log(JSON.stringify(Array.from(document.querySelectorAll('.retableRow')).map(node => {
  let rating
  const stars = node.querySelectorAll('.rating .personal')
  if (stars.length) {
    rating = stars.length
  } else {
    rating = node.querySelector('.rated-up') ? 'up' : 'down'
  }

stilist

// Copyright 2018 Jordan Cole
//
// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to
// deal in the Software without restriction, including without limitation the
// rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
// sell copies of the Software, and to permit persons to whom the Software is
// furnished to do so, subject to the following conditions:
//
// The above copyright notice and this permission notice shall be included in

stilist

require 'fileutils'
require 'json'

# LOG = ARGF.read.freeze
LOG = File.read('log.txt')

COMMIT_PATTERN = /
  \A
  r(?<revision>\d+)
    \s\|\s

stilist

MIT License

Copyright (c) 2017-present Jordan Cole

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

stilist

Copyright (c) 2017 Jordan Cole

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR O

stilist

Monitoring

Alerting

• base rate fallacy: given 1% false positive, 1% false negative, and 99.9% uptime: 9.1% chance positive predictive value (true positive)
• sensitivity (% true positives) vs specificity (% not false positive)
• ‘Alert liberally; page judiciously. Page on symptoms, rather than causes.’
• ‘An alert should communicate something specific about your systems in plain language: “Two Cassandra nodes are down” or “90% of all web requests are taking more than 0.5s to process and respond.”’
• ‘Not all alerts carry the same degree of urgency.’
• ‘Many alerts will not be associated with a service problem, so a human may never even need to be aware of them. […] should generate a low-urgency alert that is recorded in your monitoring system for future reference or investigation but does not interrupt anyone’s work.’