Andrew Mercer
on this page

    Good technical work only counts if people can see it and trust it, and the working relationships around that work shape how much of it gets done. These guides cover the communication side of software and platform engineering.

    • Communicating Platform Updates — how to announce maintenance, report on incidents, and close the loop on changes, with audience and channel guidance, timing rules, a reusable update template, and a pre-send checklist.
    • Dealing with Micromanagement, Nitpicking & Chronic Negativity — why micromanagers behave the way they do, tactics for coping day to day, escalating ways to change the dynamic, and handling pedantic peers in code review.
    • Addressing Double Standards — how to tell a real double standard from legitimate differences in treatment, when it becomes targeting, and how to document and raise it.
    in this section
    * addressing double standards
    * bikeshedding (parkinson's law of triviality)
    * code review nitpicking
    * code review severity labels: nit, blocking, non-blocking
    * communicating platform updates: a guide for it/devops/sre roles
    * compassion fatigue & decision fatigue
    * dealing with micromanagement, nitpicking & chronic negativity
    * emotional bandwidth
    * level of give a fuck (logaf)
    * premeditated resentment and how it manifests in software development teams
    * pull requests & code review
    * six mainstream concepts related to logaf
    * spoon theory
    * strong opinions, weakly held
    * what people call it when speaking up at work backfires