I suppose this explains why developers don’t measure things. The things the typical developer needs to measure are tiny and immediate beyond trivial, typically

I suppose this explains why developers don’t measure things. The things the typical developer needs to measure are tiny and immediate beyond trivial, typically with tools already available. The problem with measuring things though is that you are forced to compare data and make original decisions that may likely destroy your personal opinions of a deeply held approach. Most developers bind their careers to a few technical conventions, which means a potentially catastrophic emotional/ethical impasse. The fairness described in the article is about validation of algorithms across human fairness in finance and insurance, which implies validation against demographic averages. That can mean challenging assumptions of social presumptions for the sake of defeating bias as a quality control measure of algorithmic durability. In either case the enemy is bias and the challenge is choosing between data objectivity versus current approaches. Even when the problem is made as simple as can be imagined people still find this harder than an outside observer would expect.