Reminds me a bit of the good ol' pre-Vista days of "My Documents" et cetera in the Windows world. :) But hey, even MS took a decade between 95 and Vista to decide to drop the prefix!
Their choice of "My" caused a humorous reaction on quite a few people who felt the computer was much more a separate entity than a mechanical extension of themselves (to use the terminology of the OP)...
Remember the joke that Bill Gates reckons he has such complete control over every PC with Windows installed that he goes around naming each one "My Computer" so we won't forget it's his?
But versions of Windows before 95 didn‘t have the prefix. In Windows 3.1 it was just Program Manager, Write, Paintbrush, File Manager etc. So they took a step backwards in 95. It took them a decade to get back to where they were in the 80s.
This is a really dismissive comment that could be used to trivialize just about any article and debate here on HN. While it isn't a big issue, this topic is something designer's do think about and a discussion about its effects on user experience seems reasonable. Plus I doubt anyone's losing hours of productivity over this.
I disagree, I think if the OP was attempting to make a fair analysis, he should have acknowledged the third option. My immediate thought was the same expressed in this comment, as My & Your add wordiness. I suppose it depends on the overall tone & genre of the software you're (I'm?) designing, but it's an obvious alternative.
Dustin's post was not simply about whether to prepend labels with "my" or "your". That choice was an example of a more fundamental concern: whether to imagine the user as seeing an app as an extension of themselves or as seeing the app as a separate entity, and the implications of that in the interface.
It may have been helpful for the post to consider the effects of using no pronouns on a user's mental model, and a better response to the post would be to explore those effects, not to dismiss it outright as a false dilemma. A much better method of dismissing posts that have obvious answers is to not comment on them.
Calling comments dismissive is rather dismissive in itself. I don't see what is wrong with pointing out a better option (in the opinion of the commentator) in a succinct way.
That's the kind of dismissive attitude that kills web companies. If there's one thing we've learned from usability research, A/B testing and the like, it's that seemingly subtle changes in details can make a huge difference to overall effectiveness. And if there's a second thing we've learned, it's that what programmers or web developers assume is best is a lousy indicator of what is best when you actually measure results.
Presenting material in a way that resonates with the target audience of each particular product or service is important, and a little time spent getting it right will almost certainly generate more benefit than writing code for the same amount of time.
That's irrelevant. There are multiple reasonable possibilities here. Saying "Do X, now get on with coding" as if X is somehow obviously the right answer is a very dangerous attitude. The original article might not have mentioned those kinds of testing explicitly, but still, professionals decide among various choices being considered based on merit, not personal preference.
I find your comment odd (in that I am confused by it). The top comment (which you seem to take issue with) isn't any more useful to anyone than the OP itself. I took it as a bit tounge-in-cheek. You state that professionals make decisions based on merit rather than personal preference and yet the OP did the exact opposite. So neither the OP nor top-commenter are taking the 'professional' approach here.
FWIW I agree with pretty much everything you said in your previous comment (although perhaps not the first sentence).
EDIT: Or perhaps his last sentence irritated you? If he'd omitted "Now, get back to writing code!" would you still feel the same?
I think we just interpreted the original comment differently. I didn't sense any humour in the point being made, only in the flippant final line, and I strongly disagreed with the basic point regardless of anything related that the original article did or didn't mention. If I misunderstood then the poster has my apologies.
Where this simplicity breaks down is when you have two kinds of a thing. For example, a user may have documents shared by a group and then documents that are yours/mine.
Honestly, I still feel it's an overwrought discussion about something that ultimately doesn't effect the user enough to change their general perception of the product.
Microcopy generally takes the form of a speaking voice which addresses the User directly, so a phrase like "Are you sure you want to delete this Customer?" makes more sense than "Am I sure I want to delete this Customer?". And so forth.
Which Microsoft also fouled up. A user's desktop could contain elements which were present in the user's desktop folder, in a group folder, or in the global desktop folder for the system. From within the Explorer shell, it wasn't obviously clear where the element came from. Yet another reason I have a rabid dislike for GUI file manglers.