2 ms·
Not blaming this commenter specifically, but this pervasive callous attitude of over-focusing on narrow metrics of importance seems to be why our general exper
by ssivark 7y ago
Not blaming this commenter specifically, but this pervasive callous attitude of over-focusing on narrow metrics of importance seems to be why our general experience with software is so... shitty.
The problem with such “partial” functionality is that it breaks composition. When you start building systems with a dozen modules, each with a couple of edge cases like this, the probability of something failing becomes high, and makes the final result/experience very crappy. Imagine if you had a sweater you couldn’t wear on Tuesdays!
For those who don’t get it, it’s not just about how often this “bug” affects the system (let alone the fact that it is quite severe). It indicates an utter lack of competence towards developing safety critical systems... like, how can one be writing navigation code and NOT know this?
That this could be considered a run-of-the-mill software bug means that we have set our standards too low.