~~~ Be Not Measurable ~~~
If developer productivity should be measured at all, maybe it should be with sociograms that show how much actual collaboration happens and how it becomes reflected in the organization of the technology (Conway's Law enters the chat).
Which you bet is invasive shit that can feel like Big Brother is watching, regardless of the data being collected. But tech management seems to want to do it anyway, without thinking about it from our perspective at the sharp-end.
These complicated ways they want to measure Work As Imagined and Work As Prescribed become huuuuge compliance pressure on us. They care very little about Work As Done because it can't be predicted. It's very unmeasurable work, especially in SRE.
This is the same neoliberal thinking that we can quantify everything, make all Work measurable, so that only Good Training - not Expertise - is needed to do the Work. Hire lower paid or even robotic agents. Profit.
For instance, attributing Root Cause is fundamentally misaligned with how we need to understand the way things Succeed.
If we look at history and point to the downhill slope of failure, we're looking past what Resilience has already made this "failure" not be more of a failure than it is. So is it a failure at all?
When we measure success, we tend to measure multiple things and consider all kinds of abductive reasoning to point at all the various paths for success to happen.
In tech, we do the opposite for incidents, especially when only failures count. So if you are in an org viewing incidents as causal pathways to automate away, then maybe AI can replace those humans and the org will continue to suffer exactly the same kinds of incidents.
Well, the silver lining I guess is that AI can't replace what can't be measured.
~~~ Be Not Measurable ~~~
:starrgirl.eth 
