I use this page as a reminder of how I want to conduct myself.
Slogans repeated frequently. Some more than others.

The single most important one: Empathy in all things.

Hot roux + cold milk = no lumps.
          -- Chef John from FOODwishesDOTcom

Regardless of what we discover, we understand and truly believe that everyone
did the best job they could, given what they knew at the time, their skills
and abilities, the resources available, and the situation at hand.
            --Norm Kerth, Project Retrospectives: A Handbook for Team Review

Change the process, change the outcome.
  - Mick Gordon ('DOOM': Behind the Music, https://www.youtube.com/watch?v=U4FNBMZsqrY)

Overshoots, oscillations, and collapses are always caused by delays.
                         -- Donella H. Meadows, Thinking in Systems: A Primer

The 3 Ways of Devops:
- Systems Thinking (protip- read Thinking in Systems: A Primer)
- Remove Delays In Feedback Loops
- Experiment (take risks) and Learn From Failure (conduct root cause analysis)

Don't be the asshole.
          -- The Scrum Book?

- USE. A. TICKETING. SYSTEM.
  - Don't swear in your ticketing system.
- Nearly always have an odd number of persistence layer nodes per (AWS) region.
  - Primary/read-replica is a good example of when an even number is ok.
- Demand SLOs.
- Hold your team to SLAs.
- Eliminate toil (manual processes)
- SRE is just Google flavored DevOps.

- Steal Good Ideas from LEAN:
  - Keep Inventory At A Minimum
      Inventory is probably "number of tickets in the work queue".
  - Minimize the Work Queue
      Measure the amount of time it takes from a work being requested to
      work being finished.
  - Maximize Efficiency
      Keep improving your own tools. Attack the constraint, first optimize
      the tools/services/train-stops/whatever everyone uses all the time.

Recreational Sysadmining: Doing tech stuff at home that smells an awful lot
like work stuff. For examples: a Grafana dashboard with your refrigerator's
temperature, a spot-instance-autoscaling kubernetes cluster, any sort of "home
lab". Careful not to over-do it!

Intelligence and experience are multidimensional. Everyone has skill points in
different areas.

Data has mass. The more you have, the harder it is to move.

Have boundaries. Between Control Plane and Workloads, dev/staging/prod,
your time (like lunch and working hours), FedRAMP/NotFedRAMP, probably more.

If a company's leadership can't figure out pronouns, it may be a sign they are
not ready to figure out operational readiness.

You want more than two examples before commiting to a pattern.

Code Quality goes in one direction, OK to s--t. Our job is to slow that curve as much as possible.

There's nothing more permanent than a temporary hack.