The common pattern underlying all of them is a spillover of evaluative judgments made on one axis (e.g., “helpful to people”, “efficient”) to all other axes
So it is basically a failure to decouple the values when they diverge?
IDK how broadly you tend and intend to use the term “value”, but for me, applying it here is quite a stretch.
If you’re measuring the performance of a program, and notice that it’s very fast/time-efficient, and consequently conclude that it must therefore also be space-efficient (use as little memory as possible), and elegantly written, then you’re definitely confusing various axes of evaluation — i.e., the thing I pointed at in the part of the post you’re replying — but it seems like a big stretch to call time-efficiency, space-efficieny, and source code elegance three distinct values that are being confused here.
So it is basically a failure to decouple the values when they diverge?
IDK how broadly you tend and intend to use the term “value”, but for me, applying it here is quite a stretch.
If you’re measuring the performance of a program, and notice that it’s very fast/time-efficient, and consequently conclude that it must therefore also be space-efficient (use as little memory as possible), and elegantly written, then you’re definitely confusing various axes of evaluation — i.e., the thing I pointed at in the part of the post you’re replying — but it seems like a big stretch to call time-efficiency, space-efficieny, and source code elegance three distinct values that are being confused here.
Oh, I didn’t mean value as “measure of worth” but value as in the math definition of “amount denoted by reference”.