https://danluu.com/metrics-analytics/
I'll add that I worked in systems at a large php shop which didn't have good metrics for utilization. After the adoption of HHVM their utilization dropped enough that they ended up buying extra hardware in the 6 figures. They knew that performance was a lot better but they didn't quantify it. So surprise! All it took to figure that out and start making better decisions was to collect SAR data and dump it to a central log. So, yeah. Boring is good or at least a good place to start.
Goodhart's law has been a problem with measures.
“When a measure becomes a target, it ceases to be a good measure.”
The problem is that a competitive measure tends to overshadow the utility of the measure (look at anything that starts with a TPC- or the first rotation of a Tesla roadster tire).
So the biggest impact of a measure is immediately after it is introduced, because the market hasn't engineering itself to overfit to that measure.
And that is what Dan's post clearly says, that immediately after he brings up something, there is an actual change in the industry practice that happens.
> it doesn't show off creativity.
But something like Jepsen is amazingly useful because it is a creative nothing-up-my-sleeves end-run around first-party testing - actual third party testing for the product is the red-team to a QE team doing the blue-team work. The problem is that a lot of people leave that to the same vendor who is selling the product with its promises from their sales team - it is hardly an open book into the bugs open list (I work in open-source, so I have to wash my dirty laundry in public).
As a side not to this, I had a meeting in the last 2 days where someone told me that the "QE team is doing a good job, because the test have been consistently green as the release approaches".
And I didn't know exactly how to respond to that.
Because, as it is, it just sounds like “advertisement doesn’t work on me, because I’m better than normal people”.
This.
If this is your modus operandi, then please think twice.
For me, as the person with the problem, this just sounds like "I don't want to be bothered with this right now".
Most maintainers don't see this as a possibility to improve their project, but as trouble for their brilliant idea. Grow up!
I am watching a coworker begin to discover this right now. He’s one of the last standing of a cohort of overconfident loudmouths. It’s been... interesting. No self-awareness so far yet though.
