I prefer computers do what I tell them to rather than what it thinks I meant to tell it to. If I screw up, why isn’t it on me to fix it? And why aren’t you proofing data entry before accepting it?
How is it not data, usually key data, no less? It requires a unique path/filename combination, has to be human readable, is entered by a user. Not traditionally what one would think of as data entry, but is data that is entered and referenced. And unless you only use the recent view for finding files, knowing that the name is entered as intended seems rather important.
So? Numbers need to be human readable and entered by humans, too, and I’ve seen discussions about the proper pronunciation of 1.32. There are a number of ways that appear equally useful, but there is a convention that has been applied to remove ambiguity. And that convention is ignored in areas where other issues are more important. That convention is no more natural than writing itself, yet most people beyond a basic level of numeracy (and, perhaps, English fluency) know it. Moreover, filenames, just like numbers, need to be computer readable, as well, and conventions have been applied. Some of those conventions were constrained by the capabilities of computers of the time, just like with dates.
And people are very much case-aware. IF THEY WERENT, WHY ARE ALL CAPS COMMENTS INTERPRETED DIFFERENTLY?
I prefer computers do what I tell them to rather than what it thinks I meant to tell it to. If I screw up, why isn’t it on me to fix it? And why aren’t you proofing data entry before accepting it?
deleted by creator
How is it not data, usually key data, no less? It requires a unique path/filename combination, has to be human readable, is entered by a user. Not traditionally what one would think of as data entry, but is data that is entered and referenced. And unless you only use the recent view for finding files, knowing that the name is entered as intended seems rather important.
And perhaps I am also secretly a machine.
deleted by creator
So? Numbers need to be human readable and entered by humans, too, and I’ve seen discussions about the proper pronunciation of 1.32. There are a number of ways that appear equally useful, but there is a convention that has been applied to remove ambiguity. And that convention is ignored in areas where other issues are more important. That convention is no more natural than writing itself, yet most people beyond a basic level of numeracy (and, perhaps, English fluency) know it. Moreover, filenames, just like numbers, need to be computer readable, as well, and conventions have been applied. Some of those conventions were constrained by the capabilities of computers of the time, just like with dates.
And people are very much case-aware. IF THEY WERENT, WHY ARE ALL CAPS COMMENTS INTERPRETED DIFFERENTLY?