Ryan Parman skyzyx

I'm OK; The Bull Is Dead

By Gopal K. Kapur
Published at Computerworld • JUN 21, 2004 6:00 AM PST

Early in my career, when I worked as an engineer, my boss had a process by which the engineering team was expected to report project status. He insisted that we use the following steps, in the specified order:

Punch line: The facts; no adjectives, adverbs or modifiers. "Milestone 4 wasn't hit on time, and we didn't start Task 8 as planned." Or, "Received charter approval as planned."
Current status: How the punch-line statement affects the project. "Because of the missed milestone, the critical path has been delayed five days."

Dumb, small things that irritate me for completely irrational reasons: a living list

Inspired by Michael Lopp (author of Managing Humans and Being Geek), from the podcast episode “The One About Manager READMEs” from The Important Thing podcast.

Continually updated.

Writing

Double-spaces after periods. This is leftover from the typewriter days.

macOS is a Unix, and not built on Linux.

I think most of us realize that macOS isn't a Linux OS, but what that also means is that instead of shipping with the GNU flavor of command line tools, it ships with the FreeBSD flavor. As such, writing shell scripts which can work across both platforms can sometimes be challenging.

Homebrew

Homebrew can be used to install the GNU versions of tools onto your Mac, but they are all prefixed with "g" by default.

All commands have been installed with the prefix "g". If you need to use these commands with their normal names, you can add a "gnubin" directory to your PATH from your bashrc.

[20XX-XX-XX] Service Name downtime

This is a blameless Post-mortem.
We will not focus on the past events as they pertain to "could've", "should've", etc.
All follow up action items will be assigned to a team/individual before the end of the meeting.
If the item is not going to be top priority leaving the meeting, don't make it a follow up item.

| | |

Instructions

Expectations

Verbalize your thoughts as you solve the problem. How you arrived at the solution is just as important as the solution itself.
Ask questions if you're not sure about something, rather than guessing.
Read the instructions, which consist of this entire page.

	{
	"margo": {},

	// The maximum amount of memory(MiB) that MarGo is allowed to use
	"margo_oom": 1000,

	// you may set specific environment variables here
	// e.g "env": { "PATH": "$HOME/go/bin:$PATH" }
	// in values, $PATH and ${PATH} are replaced with
	// the corresponding environment(PATH) variable, if it exists.

	##
	# Requires:
	# * AWS Unified CLI Tools
	# * jq
	##

	cluster_name="name-of-ecs-cluster"

	aws ec2 describe-instance-status \
	--instance-ids $(

	wget http://repo1.maven.org/maven2/com/madgag/bfg/1.13.0/bfg-1.13.0.jar -O ~/bin/bfg.jar
	git clone [email protected]:{org}/{repo}.git
	cd {repo}
	java -jar ~/bin/bfg.jar --strip-blobs-bigger-than 100k --protect-blobs-from {branch}
	git reflog expire --expire=now --all && git gc --prune=now --aggressive
	git push --force

	...

	{{- partial "toc.html" . -}}

	...